+1, exactly Jörn. I'm not a huge fan of the bylaws. What I tend to do is to cruft up a resolution template, e.g,. here's a recent one for Airavata which passed muster:
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Airavata Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Airavata Project be and hereby is responsible for the creation and maintenance of software related to executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds; and be it further RESOLVED, that the office of "Vice President, Apache Airavata" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Airavata Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Airavata Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Airavata Project: Aleksander Slominski <[email protected]> Ate Douma <[email protected]> Chathura Herath <[email protected]> Chris Mattmann <[email protected]> Eran Chinthaka <[email protected]> Srinath Perera <[email protected]> Heshan Suriyaarachchi <[email protected]> Lahiru Gunathilake <[email protected]> Marlon Pierce <[email protected]> Patanachai Tangchaisin <[email protected]> Raminderjeet Singh <[email protected]> Saminda Wijeratne <[email protected]> Shahani Weerawarana <[email protected]> Suresh Marru <[email protected]> Thilina Gunarathne <[email protected]> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Suresh Marru be appointed to the office of Vice President, Apache Airavata, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Airavata PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Airavata Project; and be it further RESOLVED, that the Apache Airavata Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Airavata podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Airavata podling encumbered upon the Apache Incubator Project are hereafter discharged. Try revising this and getting to a resolution everyone is happy with. Then we can: 1. Community [VOTE] here on ctakes-dev@incubator 2. Incubator PMC [VOTE] on general@incubator 3. Add board resolution to board agenda - target March 2013 board meeting Cheers, Chris On 2/19/13 6:19 AM, "Jörn Kottmann" <[email protected]> wrote: >On 02/19/2013 02:11 PM, Chen, Pei wrote: >> What is the general procedure? >> Do we just copy and paste an example resolution and put it to vote at >>dev, then general, and if it passes. Present it to the board? > >The process is explained here: >http://incubator.apache.org/guides/graduation.html#process > >It might be easier to use the resolution template (committer access only): >https://svn.apache.org/repos/private/committers/board/templates/podling-tl >p-resolution.txt > >Jörn
