Quote:
Personally, I'd like to see a third person take over and merge the best concepts of the various World Eaters lists to get a "core" list; using the ideas and experiences without the animosity and hard feelings.
Respectfully, I think this sets a dangerous precedent and might discourage development from developers. Why would anyone want to develop a new list if the prospect of having their work taken away from them hangs on the horizon.
I think the community is self-purifying and that list development responds well to market forces.
Think about the process as it stands now.
Someone gets an idea, they cobble together some notes, maybe they get the list to the first step, play a couple of games whatever. The next step is what really determines how far the list will go. The list gets shared, people look at it, interest is generated (hopefully).
The key though is the interaction between the developer and the community. There is a lot of wisdom inherent in the community and that should always be tapped in order to improve the product, because as we have all seen if we've been around long enough, none of us are that good.
That being said, the "vision" still has to come from the individual, JMO. Taking the vision away from the author, to be developed by some unknown committee or representatives strikes me as intellectual socialism.
Please do not go down this road. It is one thing to pick up an abandoned list. It is quite another to attempt to take something away from it's owner.
Quote:
The NetEA project is supposed to be about working together, in open fashion, to build lists as teams of players.  Yes there are "champions", and even rivalries, and egos do get in the way, but the spirit of the project is supposed to be a sense of community and co-operation, not a "*my* list is the bestest!" competition.
There are examples of both and I think both methods work. Both methods fail as well. I don't think the community has the wisdom to know in each case, which way the dice will roll. When there are like minded spirits, the team approach can really shine. However, you cannot force or legislate teamwork.
It either takes place naturally or it fails miserably.
I think the most equitable solution at this point is to let the two developers go their own ways. Let them work on which type of list they want to work on and let the players decide.
