[Tapestry-developer] [VOTE] Adopt Apache Voting Rules

[Howard M. Lewis Ship]

DISCUSSION:   I think we should do a vote to check that the "grandfathered" committers are reachable (subscribed to and monitoring the list) and in the loop (ready to discuss and vote).  We can then vote on future items, such as addining additional committers, changing the license for the framework and (eventually) moving over to Apache and/or Jakarta.    There are also other decisions coming with the framework; for instance, my ideas for Tapestry Lite are controversial and could be discussed further.   See http://jakarta.apache.org/site/guidelines.html for details on what this entails.    What does this mean?   It means that for all significant decisions, an action item will be created and a vote called for.  The results of the vote determine whether the action item proceeds or is discarded.   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?   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:   ---- Howard Lewis Ship [EMAIL PROTECTED] http://tapestry.sf.net