That book is the long version. The short version, which will do for projects just starting out, is: make some useful code, stick it on GitHub, make sure it's got readable documentation, and by default be nice to everybody who helps out.
The prevalence of this sort of lightweight open source project structure in the node.js community is probably the single largest factor in its success. It also works well elsewhere, but the node.js folks are the most dramatic example I've seen.
I did. I also sit next to the guy who wrote it (but I read it years before I met him).
If you take nothing else from it, the bikeshed concept is useful in pretty much any discussion.
This is an interesting book with a lot of good information on organizing volunteers to accomplish productive ends.
Producing Open Source Software