You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by co...@spamassassin.apache.org on 2004/09/27 04:23:30 UTC

[SpamAssassin Wiki] New: ProjectRoles

   Date: 2004-09-26T19:23:30
   Editor: DanielQuinlan <qu...@pathname.com>
   Wiki: SpamAssassin Wiki
   Page: ProjectRoles
   URL: http://wiki.apache.org/spamassassin/ProjectRoles

   new page

New Page:

#pragma section-numbers off

= ASF Project Roles =

SpamAssassin, as an Apache top-level project, follows the Apache development model which [http://www.apache.org/foundation/how-it-works.html#roles defines the various roles] in the project:

 * '''users''': someone that uses our software
 * '''[http://www.apache.org/dev/contributors.html contributors]''': anyone can provide feedback, submit bug reports, or submit patches
 * '''[http://www.apache.org/dev/committers.html committers]''': a committer is simply an individual who was given write access to the codebase
 * '''[http://www.apache.org/dev/pmc.html PMC members]''': the PMC is responsible for managing a project

= SpamAssassin specifics =

The SpamAssassin PMC, like most other PMCs, is responsible for:

 * adding new committers (and potentially removing)
 * creating and destroying subprojects
 * setting project direction
 * handling public relations
 * setting policy and procedures

In addition, there are some actions that are purely development-related,
so they do not fall under the PMC mantle.  Of course, people who happen to be on the
PMC tend to do these, but committers could as well.  Then again, a
committer who was this active and responsible for the project would
frequently end up being a PMC member.

 * proposing and cutting releases
 * scheduling

= Advancement =

Developers and contributors who contribute too much good code and not enough bad code usually become committers.

Committers with a long history of significant involvement in the advancement of the project and project development (ideally in more than one way), a strong ability to work with others in the ASF way, and who are not jerkwads are generally nominated to be on the PMC.  After the PMC has voted to add a new PMC member, the ASF board has to approve new PMC members.

There are no hard criteria for either of these roles: not lines of code nor number of patches.  If you're interested, you can always send a message to the PMC to ask where you are on the radar.

= Current roles =

See the [http://cvs.apache.org/viewcvs.cgi/spamassassin/trunk/CREDITS?root=Apache-SVN&view=markup CREDITS page].