forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: [DRAFT] Forrest Project Guidelines
Date Wed, 09 Jun 2004 07:17:05 GMT

I've made fundamental changes in the committers-PMC section, trying to 
be more near the legal ASF foundation bylaws.

David Crossley wrote:
> Here is the current content. Please everyone send feedback
> to this list. Current committers can tweak the xdoc at
> guidelines.xml but please discuss major changes.
> This initial document is intended as a discussion starter.
> Developers
> ----------
> These people are contributers who make more substantial
> contributions. They get more involved in discussion,
> especially discussion about design issues, help with
> solving major issues, provide patches with new and
> improved functionality. They would participate on both
> the "dev" and "user" mailing lists.

Some developers can be given partial or time limited commit access, to 
be able to give a more substantial contribution to the project without 
necessarily becoming stably part of it.

All commit accesses to developers must be given with the direct 
supervision of at least one PMC mmember, and must be voted favorably by 
the PMC.

Being a developer, with or without commit access, is a necessary step 
for becoming a project committer.

> Committers
> ----------
> When developers remain with the project and demonstrate
> commitment to the project in various ways, then they
> will be noticed and invited to become committers. After
> a successful vote, they are provided with a user account
> and commit access to the source repository, which enables
> them to be far more productive. This is meritocracy - they
> are given more responsibility and can do more work. 
> The responsibilities of committers include:
> * Ensuring that they do not add code that has copyright
>   and license issues.
> * Keeping oversight of the commit log messages.
> * Resolving license disputes regarding products of the
>   project, including other supporting software that is
>   re-distributed.
> * Deciding what is distributed as products of the project.
>   In particular all releases must be approved by the 
> * Maintaining the project's shared resources, including
     the codebase repository, mailing lists, websites.
> * Speaking on behalf of the project.
> * Maintaining these and other guidelines of the project.
> All Apache committers are required to have a signed
> Contributor License Agreement (CLA) recorded on file with
> the Apache Software Foundation. The Committer FAQ provides
> more details about the requirements for committers. 

 From a project management perspective, and as ASF bylaws, the 
committers on a project form the PMC (Project Management Comittee), that
> is responsible to the Board and the ASF for the
> management and oversight of the Apache Forrest codebase
> and community. 
> The PMC does have a private mailing list on which it can
> discuss certain issues. However this list is rarely used
> and every effort is made to conduct all discussion on the
> public mailing lists. 
> The chair person of the PMC is appointed by the ASF board.
> The chair is an office holder of the Apache Software
> Foundation (Vice President, Apache Forrest) and has
> primary responsibility to the board for the management of
> the project, within the scope of the Forrest PMC. The chair
> provides quarterly reports to the board about developments
> within the Forrest project. The PMC may consider the
> position of PMC chair annually, and may recommend a new
> chair to the board. Ultimately, however, it is the board's
> responsibility who it chooses to appoint as the PMC chair. 

<link to the asf bylaws/>

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

View raw message