The Open Source Prime Directive

May 19, 2003 9:35 AM

Do not, do not, do not start a public Open Source project unless you already have:

  1. Working code that does a useful and/or interesting subset of the project's goal
  2. An automated build
  3. Sufficient instructions to get the program running

This rant was brought to you by one too many Google searches that ended up on a Sourceforge or Savannah project that was started in 2001, updated for a month and then abandoned.

This rant was brought to you by one too many really interesting-looking projects that thought it was a good idea to have a design phase that was open to public comment, and as a result never produced anything.

Getting people to contribute to Open Source is hard. If you do not have sufficient motivation1 to take the first, important steps yourself, nobody else is going to. At most, you'll attract a bunch of other people who, like you, want to talk about the project instead of coding it.

A bit harsh, perhaps, but true.

1 Edit: This originally read ‘skill’, but was changed after publication to better reflect what I meant to say in the first place.

2 TrackBacks

Listed below are links to blogs that reference this entry: The Open Source Prime Directive.

TrackBack URL for this entry: http://fishbowl.pastiche.org/mt-tb.cgi/242

Among other things, I've been looking at Open Source repositories to publish working code to and start inviting collaboration on. Read More

Really, there is. Mostly it's pretty bad stuff, but now and then you find a thread that leads somewhere good. Great. So if I start using this application, I’m going to become reliant on some paranoid flake who cripples his program on totally specious... Read More

2 Comments

Guilty: http://sourceforge.net/projects/jackal/ . I like to think I learned the lesson, though.

I agree, this should be part of creating a project on sf or fm or similar

Previously: Passing by on the web

Next: Mortal Hacking