Most out there enjoy hacking around on scripts, sometimes altering others' Open Source code to meet their needs. What happens, though, if you decide to make that step and jump out with your own Open Source project? How can you do it? What resources do you need? Well, this new article (via a link from PHPKitchen) can give you all of the answers and more.

The article includes topics such as: The Developer's Curse: Why OSS Projects Fail, Cut the crap: Homepage hints, She's gone from Suck to Blow: When to Go Live. It assumes that you, at the least, have a good understanding of some of the tools OS developers tend to use (like CVS, creating READMEs as needed, etc) as well as a good sense of how your project really fits into the world.

As the developer, you are blinded by how cool your project is. [...] Overcoming this bias is the single hardest thing to do when running an Open Source Project. I call this the "developer's curse", and is way most OSS projects fail to attract and keep developers or users.