You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Apache Geronimo Bylaws

Charter

This is the ASF Board resolution that created the Apache Geronimo project on 26 May 2004:

         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
         a certified implementation of the J2EE specification
         and related software and materials for distribution
         at no charge to the public.

         NOW, THEREFORE, BE IT RESOLVED, that a Project Management
         Committee (PMC), to be known as the "Apache Geronimo PMC", be
         and hereby is established pursuant to the Bylaws of the
         Foundation; and be it further

         RESOLVED, that the Apache Geronimo PMC be and hereby is
         responsible for the creation and maintenance of an open-source
         implementation of the J2EE specification as well as related
         software and other materials determined appropriate by
         the Apache Geronimo PMC licensed to the Foundation; and be
         it further

         RESOLVED, that the Apache Geronimo PMC is responsible for
         outreach and cooperation with other open-source projects whose
         purpose is deemed compatible with the work of the Apache
         Geronimo PMC; and be it further

         RESOLVED, that the office of "Vice President, Apache Geronimo"
         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 Geronimo PMC, and to have primary responsibility
         for management of the projects within the scope and
         responsibility of the Apache Geronimo PMC; 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 Geronimo PMC and also constitute the list of initial
         committers :

           Jan Bartel
           David Blevins
           Jeremy Boynes
           Alan Cabrera
           Hiram Chirino
           Gianny Damour
           Ceki Gülcü
           Jules Gosnell
           Jim Jagielski
           David Jencks
           Jacek Laskowski
           Geir Magnusson Jr.
           Richard Monson-Haefel
           Aaron Mulder
           Bruce Snyder
           Davanum Srinivas
           James Strachan
           Dain Sundstrom
           Greg Wilkins

         NOW, THEREFORE, BE IT FURTHER RESOLVED, that Geir Magnusson be
         and hereby is appointed to the office of Vice President, Apache
         Geronimo, 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 Geronimo 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 Geronimo Project.

By Unaninmous vote, the Apache Geronimo PMC was approved.

Project Structure

participants, contributors, committers, pmc

PMC Composition

all committers..?

PMC Responsibilities

approve releases vote on new committers oversee the project, subject to the chair

Folks,

Am trying to come up with bullet items (which can be expanded later) on what the board expects from a PMC and its members. Does anyone know if there is a document that already has this kind of list? Can folks please help refine/expand this list.

(May be each line item should start with "Thou Shalt" (smile)

#1: Timely and accurate reports based on the rotation schedule in the foundation svn module #2: Create and maintain a charter that governs the PMC/project(s) #3: Take decisions affecting progress and health of the projects(s), ensure smooth fun

  • No labels