What is the best way to set up a project's mail lists and what is their ideal structure.
One idea:
- every project should have a projectname-dev list and projectname-user list. This gives users a retreat from high bandwidth conversations and starts a band of self-supporting users who help each other out. Developers are expected to monitor it.
- All CVS commit messages should go to projectname-dev as opposed to going to a seperate list. This allows for greater oversite and helps keep discussion focused on the actual work of the project. It also helps to keep conversations about a specific commit in the same place.
Another idea:
- Developers interact with their intended audience on a single dev@ list. During the launch of a project, it is very important to interact with the users. Even as the project matures, it is important not to tune them out; the worst of all possible worlds is a user community totally disjoint from the developers.
- Commit messages go to cvs@ where the developers can sign up to receive them. (actually, with SVN coming on the scene, it might be good to start using checkins@ or commits@)