To me the question isn't wether it is a good idea or not. The real question seems to be wether someone will actually sit down and do it. look at sourceforge, code.google.com and all the other hosters that let you create projects with a few mouseclicks (been there done that unfortunately myself).
It is just too easy to think "Hey I need a tool, let's go to sf.net creat a project make up a 3 liner as specification and wait for some community to build up".
Sourceforge alone counts too many projects that haven't even started - I'm not putting critics on anyone who has done a tool the third time, there may have been arguable reasons but at least he/she has done _something_. Better someone sits down writes the software he/she needs until at least a level of usability is reached so that you acutally have a lib/executable whatever that does what the initial idea was. It doesn't have to be bug free or extraordinarily reliable or the cleanest code ever. But damnit something has to be there to build upon. And mot important the initial author has to care about the project at least long enough until some critical mass has been reached that then will evolve by itself (URL:http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar).
This is what has to be done. Just writing a (stupid) blog post with 100-200 lines of code and think someone will sit down for you and do the work? Ah yessss you can then go and sue him/her that the idea was actually yours just to get the credits (prior art)....
If you want to fork it, sit down and start working (damnit just start working don't talk about it until you're too old to hit the keys....)
Slashdot Mirror
To me the question isn't wether it is a good idea or not. The real question seems to be wether someone will actually sit down and do it. look at sourceforge, code.google.com and all the other hosters that let you create projects with a few mouseclicks (been there done that unfortunately myself).
It is just too easy to think "Hey I need a tool, let's go to sf.net creat a project make up a 3 liner as specification and wait for some community to build up".
Sourceforge alone counts too many projects that haven't even started - I'm not putting critics on anyone who has done a tool the third time, there may have been arguable reasons but at least he/she has done _something_. Better someone sits down writes the software he/she needs until at least a level of usability is reached so that you acutally have a lib/executable whatever that does what the initial idea was. It doesn't have to be bug free or extraordinarily reliable or the cleanest code ever. But damnit something has to be there to build upon. And mot important the initial author has to care about the project at least long enough until some critical mass has been reached that then will evolve by itself (URL:http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar).
This is what has to be done. Just writing a (stupid) blog post with 100-200 lines of code and think someone will sit down for you and do the work? Ah yessss you can then go and sue him/her that the idea was actually yours just to get the credits (prior art)....
If you want to fork it, sit down and start working (damnit just start working don't talk about it until you're too old to hit the keys....)