Open Source Project Management Guides?

Jeff Heinen asks: "I was wondering if there exists any documentation (books, websites, etc.) covering the practical matters of organizing and managing an open source project. I'm looking for details about things like communication, organizational structure, versioning and release management, etc. I've looked around and so far haven't found anything really useful. "

Software Release Practice HOWTO

[Anonymous Coward]

The only thing like this that I've seen is Eric Raymond's Sofware Release Practice HOWTO [unc.edu]. It doesn't address everything you asked about, but it does cover some common practices among open source software writers. It may help you follow the "standard practice" as far as announcements and releases are concerned. It's pitched to the Linux crowd (since it's for the LDP), but much of it should be applicable to any open source project.

Open Source Development -- only a matter of time

[tallpaul]

Someone mentioned bugzilla, and I think that CVS, rsync and other open source distributed development tools point to an inevitability -- a lot of open source is based on "scratching an itch", so it is only a matter of time before someone develops a complete package to do it (presumably with documentation).

I've given it some thought at such a system would be entirely web-based for information, and some command line driven for speed of development. It would ideally tie in the user end of things -- easy ways to download the latest alphas, and the developers side -- easy ways to upload the latest alphas, comments automatically generated into HTML documentation, org charts, automated software tests.. the whole 9 yards. :-)

project managment

[DataDevil]

bugzilla is an idea, www.mozilla.org, under projects, they also share other software/ideas for these kinds of projects.
I do hope more people post ideas, cause i'm also looking into this subject right now for my business...
If i find the time, i'll write some stuff about how it is done at themes.org, where i do community work.

General software development management

[sobiloff]

I haven't seen anything that uses the "open source" moniker, but I've run across a few books and articles that talk about "virtual teams" which may be of help. (Unfortunately, I haven't taken the time to read them so I don't have specific references handy.) VTs are usually geographically dispersed, so they face many of the same communications issues that open source projects face.

While the communications issue throws a few curves into the situation, open source projects really are about software development (SD). As such, there are quite a few good books out there that will help you learn to manage SD efforts. The best practical guide I've ever seen to SD project management is Steve McConnell's "Software Project Survival Guide." It doesn't claim to be the "one true way" to manage SD projects, but he relies on a lot of academic research as well as his own experience to come up with a comprehensive method that actively works to minimize risk and improve communications amongst all parties. I highly, highly recommend it.

As for managing people, while McConnell does provide quite a few good pointers, its written from the point of view of someone who already understands the technical person's mindset. If you have to work with Pointy-Haired Bosses, I'd recommend reading DeMarco & Lister's "Peopleware." It provides a lot of sound business arguments that PHBs will understand for why your project and its people need adequate resources, quiet offices, and different motivators/rewards.

Good luck!

bah.

[Zurk]

I've been collaborating from a guy from japan on my open source project..he hardly speaks english, i hardly speak japanese. how does it work ? simple. He mails me updates, i put them on my page. if i like his updates, it gets included in the main source. if i dont it stays on the page under his name. For bigger projects use CVS. open source is fairly open ended..no previous project management skills required. just be casual and it will work ok.

Re:bah.

[Zurk]

oh and release early, release often. Note that leading OS developers is like herding cats - push too far and they run away. keep it simple, minimal fuss and keep the comm lines open (mailing lists are nice as are searchable mail list archives)