I have a suggestion. These community projects tend to fail because of two things: lack of leadership and lack of people actually following through and doing things. To combat this, we could appoint one or two Marshals to each area of development- Programming, Assets, and Design- who would figure out what those departments need to do, and try to get people to do them. The position wouldn't be an "authority" or team leader, as this is a voluntary and democratic community project, but it would probably be helpful to have people acting as organizers.
If we do that, we should also probably have someone sign on as producer. This person must be in the project for the long haul, and would be responsible for 1) helping the Marshals communicate and coordinate, 2) figuring out what happens if one or all of the Marshals decide to step down or quit, and 3) speaking privately to anyone who is, as professional developers say, "being a dick." Just like the Marshals, the producer would not have authority or "final say" on any portion of the project, and is just meant to act as an organizer. It would not be "their" game- in fact, their most important responsibility would be ensuring that it was "our" game as a community, and that no one person is controlling the process by being the loudest.
Whether or not anyone else likes this idea, I could theoretically submit some code at this point in either of the platforms that are being discussed. Right now my programmer-hours are wrapped up in a personal project, but I may work on this every now and then as a break. If everyone agrees with my idea, I would be more than willing to act in some organizational capacity.
Author
Topic: DrPoo's programming Jam, 100*C, a community project, that actually works. (Read 42942 times)