Jason Batten wrote:
What if an idea man posts an idea. A developer comes along and works on the idea but adds his own ideas. The idea man gets up set because his idea is ruined, now he wants the developer to drop the project or change it back. The developer says no.
I don't think the idea man will come back if he's told his idea is now the developers. I don't think the developer would come back if the idea man gets his way either.
I do not see how this is any different to any development community. I've been involved in projects on SF where someone had an original idea, other developers come in and add features, remove features, change features etc. Often with a group consensus, but sometimes not. I've also built commercial websites where the clients are unclear about their requirements, and I've ended up delivering something that I would not have chosen to. Thats the nature of the beast.
The difference here is that the idea originator may not have a specific set of features. They may just have a general idea for a program without giving any details. As bpat1434 stated, its more an exercise in brainstorming ideas than a guided development lifecycle.
I picture the system incorporating a branching structure. If an idea becomes too large or deviates too far from the original intent, it will branch off and become a new idea. The integrity of the original is maintained, and there's another project to be picked up down the track.
Jason Batten wrote:
What are you going to get from the project? Experience and perhaps some good ideas? Warm fuzzy feeling inside?
Well. Experience and ideas are always good. Something unique to add to my portfolio. I believe that this project will fill a need. If its not your need then thats fine, but from the early indications I've gleaned from my research and discussion with other developers, I think that there is definitely a need.
I dont care if the site doesn't make me money. I have a fulltime job, as well as doing my own commercial projects in my freetime.