Harihareswara has run or helped run several distributed sprints/hack days/hack weeks. Here are some tips that help. The approach is less "top-down schedule" and more "here's how to adapt to and support the emergent ways people will act".
A free 38-page sampler ebook on assessing an existing project, starting to think about budgets and money, and teaching and including unskilled volunteers. Includes the introduction and table of contents for the full (forthcoming) book.
How to attract corporate sponsors: Inventory your potential donors and fundable tasks or chores, prepare your requests and update your website and documentation to ensure your open source project looks credible, make the request, and follow up on responses.
Supporting users can frustrate maintainers. What are its causes, and how could we build the "infrastructure of equanimity" in open source? Some answers, and ideas for potential cross-project tools & practices.