PROPOSAL:
�
The Tapestry community should immediately adopt the voting meritocracy guidelines of the Apache project, as detailed in
http://jakarta.apache.org/site/guidelines.html.
�
VOTES:
�
Howard Lewis Ship: +1
Mind Bridge:
Malcolm Edgar:
Richard Lewis-Shell: +1
I'm hoping Dion and Oliver (our new friends at Jakarta) will be able to help with the exact process.� To be honest, I haven't been able to determine (from the documentation) the exact granularity of an action item.� For instance, I doubt we'd need to vote on�whether to fix bugs in the bug list ... but what if the fix causes a non-backwards compatible change?
The guidelines do seem to specify reasonably well what changes would require a vote. Here's an excerpt from http://jakarta.apache.org/site/source.html:
"Doubtful changes, new features, and large scale overhauls need to be discussed before committing them into the repository. Any change that affects the semantics of an existing API function, the size of the program, configuration data formats, or other major areas must receive consensus approval before being committed."
I agree with Craig that these matters are not necessarily relevant/interesting to a 'users' list, and it would certainly be within the Jakarta spirit (http://jakarta.apache.org/site/communication.html) to create a 'dev' email list for these issues.
Richard
