ASF Project Roles
Wiki Markup
- users: someone that uses our software
Wiki Markup - *\[http://www.apache.org/dev/committers.html committers\]*: a committer is simply an individual who was given write access to the codebaseunmigrated-wiki-markup
- *\[http://www.apache.org/dev/pmc.html PMC members\]*: the project management committee is responsible for managing a project \\
SpamAssassin specifics
The SpamAssassin project management committee (pmc at spamassassin.apache.org), 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 project management committee member.
- proposing and cutting releases
- scheduling
:
- proposing and cutting releases
- scheduling
There's a private 'PMC list', called 'private at spamassassin.apache.org', but it's not to be used as a private mailing list of general discussions for PMC members only, as this is contrary to ASF policy. Instead, it's there to discuss sensitive stuff that needs to be moderately secret. Non-sensitive PMC discussions are held on the dev list. The ASF definition of what lives on the private list is: 'issues that cannot be discussed in public, such as discussion of pre-disclosure security problems, pre-agreement discussions with third parties that require confidentiality, discussion of nominees for project or Foundation membership, and personal conflicts among project personnel.'
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
should probably ensure they're subscribed to the 'committers' and 'community' ASF mailing lists.
We have adopted a policy whereby virtually all active committers are on the PMC. Here's how this works:
Any committer who (a) is not already on the PMC, (b) has been a committer for at least 6 months, and (c) has made a commit in the previous 3 months, may be offered an invitation to join the PMC. After a committer becomes eligible, a notice for discussion can be be sent to the private@ mailing list or a vote with the usual 24hrs lazy consensus. Assuming that vote passes, see the Apache new PMC member instructions before sending an invite to the potential PMC member. There is an Invite template below.
Any PMC member who has become inactive for a period of 6 months (ie. no commits or participation in the PMC/Development community) may be marked as an "emeritus" member of the PMC. At any time, an emeritus member can declare that they are active again, and the emeritus status will be revoked.
Any committers who have not been active or committed anything for a period of 6 months may be considered to have retired from active duty and moved to inactive status. We wish them well and hope to see them return someday.
Current roles
See the CREDITS pageWiki Markup
Changes to make during Advancement
(this part is still under construction)
When a contributor becomes a committer, they should check out the svn repository using the HTTPS url instead of the HTTP one, so that they have read/write access to the repo. To check out from scratch:
| No Format |
|---|
svn checkout https://svn.apache.org/repos/asf/spamassassin/trunk
|
or to switch an existing checkout to HTTPS:
| No Format |
|---|
cd /path/to/checkedout/tree
svn switch https://svn.apache.org/repos/asf/spamassassin/trunk
|
Changes to the SVN tree can now be checked in directly using svn commit.
The first time a file is checked in using svn commit, the committer will be prompted for their username and password. This will then be cached for all further commits.
If you want to do a test commit, something like adding a single newline to the end of an inoffensive file in a subdirectory, or removing it again, will do the trick.
They should also ensure that their checkout has the svn:eol-style property set to native throughout, as (apparently) this policy cannot be set server-wide. Do this by editing the file ~/.subversion/config and adding these lines to the end:
| No Format |
|---|
enable-auto-props = yes
*.pm = svn:eol-style=native
*.pl = svn:eol-style=native
*.PL = svn:eol-style=native
*.in = svn:eol-style=native
*.t = svn:eol-style=native
*.c = svn:eol-style=native
*.h = svn:eol-style=native
*.xml = svn:eol-style=native
*.html = svn:eol-style=native
*.css = svn:eol-style=native
*.bat = svn:eol-style=native
|
The PMC members should grant their Bugzilla account 'EditBugs' status. I'm not sure how this is done, but Theo knows 
Going from committer to PMC: Granted all permissions in Bugzilla. Given option for account on bugzilla server. Given option for spamassassin.org email forwarder (jm: does this still exist?). Apache email address added to pmc email list (jm: is it supposed to be the apache.org one? mine isn't).
...
Going from contributor to committer: See BecomingCommitter.
Going from committer to PMC: See BecomingPmc.
More Details
Be sure to read how-it-works.html – there's lots of useful stuff about ASF processes there.
Invitation Text
| No Format |
|---|
To: invitee-email-address
Cc: private
Subject: Invitation to serve on the Apache SpamAssassin PMC
Invitation to Apache SpamAssassin PMC
Dear <Invitee> --
The SpamAssassin PMC has voted to invite you to join as a PMC member!
The PMC is the entity that controls the project and speaks for the
project. If you accept, you'll have the right to vote for the
community-related decisions and the right to propose committer status for
active contributors. And, of course, you'll be expected to participate in
these community decisions too!
The latter needs to be a key factor in your decision to join. It
requires almost no effort to serve as a PMC member, but you *are* expected
to subscribe to, and keep up with the mailing list traffic on the dev and
private lists, provide votes where needed, contribute to the community
when it's required, and respect the Apache Way of doing things.
Some reading on the subject:
http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/dev/pmc.html
http://www.apache.org/foundation/faq.html
If you accept, please reply-all to that effect using the email address with
which you will be subscribed to the private@spamassassin.apache.org mailing list.
|