Component/s: Process Doc
In 1.1.1 Mailing Lists, lines 202-214 of the http://java.net/projects/jsr348/downloads/download/Working%20documents/JCP%20NEXT%202.8-10AUG2011-Clean.pdf version of the process doc, there is a discussion about why a private mailing list is needed for minor admin issues. This seems overstated and based on the following comment from the closed
I don't understand why we cannot simply have one moderated list.
EG members would have automatic read/write access to the list
non-EG members would have read access to the list and all write access would be moderated (allowed upon approval)
Since all debates are tracked via the issue tracker, observers have the alternative option of commenting on the issue report.
I suggest this setup because it's used almost universally for open source projects and has proven to work (and scale). Plus, anyone familiar with open discussions will understand this model.
Sending discussions from one list to another, in my opinion, is just making matters more complex than necessary.
is seen as suspicious. I would suggest a much simplified section that would allow for a purely administrative list if that is how the EG decides it needs to conduct business, but does not advocate it.
"All substantive business must be carried out on a public mailing list designated by the Spec Lead. The
purpose of this list is to keep observers aware of important issues. The preferred way to conduct the mailing
list is a moderated list.
If the Expert Group uses a mailing list writable only by Expert Group members, then the EG must also
provide a publicly readable and writable email list or a forum to enable feedback and comments from