Erik Moeller wrote at last:
Just the basics:
- Name of the project
- Types of content that are to be covered
- Key policies
- Timetable for setting things up
- Potential changes that need to be made to the software
- Templates
- Internationalization
- Participants
Formalize these things, then have a vote on whether the project should in fact be started. Is that too much to ask?
Why hold a vote? If some people want to do it and others don't, then some people will do it while others won't. To be sure, there must be coders in the group that wants to do it, or it still won't get done! -- but if a group of coders wants us to vote to decide what they will do and what they won't, then they can do so.
Otherwise, I agree, with the understanding that some things may be incomplete before starting. Templates are the best example of this.
-- Toby