[Checkins] SVN: developer_docs/trunk/source/ Use "committer" rather than "contributor" for developers with SVN commit access.
Tres Seaver
tseaver at palladion.com
Wed Apr 21 17:33:47 EDT 2010
Log message for revision 111232:
Use "committer" rather than "contributor" for developers with SVN commit access.
Changed:
A developer_docs/trunk/source/becoming-a-committer.rst
D developer_docs/trunk/source/becoming-a-contributor.rst
U developer_docs/trunk/source/index.rst
U developer_docs/trunk/source/new-members-procedure.rst
U developer_docs/trunk/source/subversion-writable-checkouts.rst
-=-
Copied: developer_docs/trunk/source/becoming-a-committer.rst (from rev 108395, developer_docs/trunk/source/becoming-a-contributor.rst)
===================================================================
--- developer_docs/trunk/source/becoming-a-committer.rst (rev 0)
+++ developer_docs/trunk/source/becoming-a-committer.rst 2010-04-21 21:33:46 UTC (rev 111232)
@@ -0,0 +1,64 @@
+Becoming a Committer
+====================
+
+Applying for Committer Status
+-----------------------------
+
+1. Mail webmaster at zope.org for a new user account at www.zope.org.
+ Pick a user id that is a valid Unix user id. Include this id when
+ you fill out the committer agreement form.
+
+2. Print, fill out and sign the
+ `Zope Committer Agreement <http://foundation.zope.org/agreements>`_
+
+3. Submit the agreement to the Zope Foundation. This can be done by
+ either email, fax or post (in order from fastest to slowest).
+
+ The contact details can be found on the
+ `Zope Foundation website <http://foundation.zope.org/about>`_.
+
+4. Wait for an acknowledgement. If you don't get this in a reasonable amount
+ of time, then ask back on the Zope Foundation list
+ (foundation-info at zope.org) or try to contact a member of the repository
+ committee (Andreas Jung and Christian Theune).
+
+5. Deposit your SSH public key(s) as described in :ref:`deposit-ssh-pubkey`
+
+6. Get a :doc:`writeable checkout <subversion-writable-checkouts>`.
+
+.. _deposit-ssh-pubkey:
+
+Depositing your SSH public key(s)
+---------------------------------
+
+Your SSH public key(s) must be uploaded using the application at:
+https://cvs.zope.org/upload-key.html
+
+When you go to that url, you'll get a basic auth login prompt. Use your
+www.zope.org login and password.
+
+Your keys can use RSA or DSA, ssh v1 or v2. If the file being uploaded
+contains more than one public key, it should be formatted as if it
+were an authorized_keys file.
+
+You can revisit the key deposit page any time to put in new keys.
+Make sure you submit all keys that you wish to have work in any file
+that you upload as your previous upload will be overwritten.
+
+Subscribe to the Mailing Lists
+------------------------------
+
+Active Zope 2 committers should subscribe to the `zope-dev mailinglist
+https://mail.zope.org/mailman/listinfo/zope-dev`_.
+
+They should also either subscribe to the `zope2-tracker notifications
+mailinglist <http://mail.zope.org/mailman/listinfo/zope2-tracker>`_.
+(this list receives notifications from Launchpad for each updated bugtracker
+issue in the ``zope2`` project), or ask to be added to the ``zope2-dev``
+team on Launchpad.
+
+Grok committers should be subscribed to the `grok-dev mailinglist
+<https://mail.zope.org/mailman/listinfo/grok-dev>`_.
+
+Bluebream committers should be subscribed to the `bluebream mailinglist
+<https://mail.zope.org/mailman/listinfo/bluebream>`_.
Deleted: developer_docs/trunk/source/becoming-a-contributor.rst
===================================================================
--- developer_docs/trunk/source/becoming-a-contributor.rst 2010-04-21 21:26:54 UTC (rev 111231)
+++ developer_docs/trunk/source/becoming-a-contributor.rst 2010-04-21 21:33:46 UTC (rev 111232)
@@ -1,48 +0,0 @@
-Becoming a contributor
-----------------------
-
-1. Mail webmaster at zope.org for a new user account at www.zope.org.
- Pick a user id that is a valid Unix user id. Include this id when
- you fill out the contributor form.
-
-2. Print, fill out and sign the `Zope Committer Agreement <http://foundation.zope.org/agreements>`_
-
-3. Submit the agreement to the Zope Foundation. This can be done by
- either email, fax or post (in order from fastest to slowest).
-
- The contact details can be found on the `Zope Foundation website <http://foundation.zope.org/about>`_.
-
-4. Wait for an acknowledgement. If you don't get this in a reasonable amount of
- time, then ask back on the Zope Foundation list (foundation-info at zope.org) or
- try to contact a member of the repository committee (Andreas Jung and Christian
- Theune).
-
-5. Deposit your SSH public key(s) as described in the section below.
-
-6. Do a :doc:`writeable checkout <subversion-writable-checkouts>`.
-
-Depositing your SSH public key(s)
----------------------------------
-
-Your SSH public key(s) must be uploaded using the application at:
-https://cvs.zope.org/upload-key.html
-
-When you go to that url, you'll get a basic auth login prompt. Use your
-www.zope.org login and password.
-
-Your keys can use RSA or DSA, ssh v1 or v2. If the file being uploaded
-contains more than one public key, it should be formatted as if it
-were an authorized_keys file.
-
-You can revisit the key deposit page any time to put in new keys.
-Make sure you submit all keys that you wish to have work in any file
-that you upload as your previous upload will be overwritten.
-
-
-
-
-
-
-
-
-
Modified: developer_docs/trunk/source/index.rst
===================================================================
--- developer_docs/trunk/source/index.rst 2010-04-21 21:26:54 UTC (rev 111231)
+++ developer_docs/trunk/source/index.rst 2010-04-21 21:33:46 UTC (rev 111232)
@@ -5,13 +5,13 @@
Welcome to Zope Developer Information's documentation!
======================================================
-Becoming a Zope contributor
----------------------------
+Becoming a Zope Committer
+-------------------------
.. toctree::
:maxdepth: 2
- becoming-a-contributor
+ becoming-a-committer
Resources
----------
Modified: developer_docs/trunk/source/new-members-procedure.rst
===================================================================
--- developer_docs/trunk/source/new-members-procedure.rst 2010-04-21 21:26:54 UTC (rev 111231)
+++ developer_docs/trunk/source/new-members-procedure.rst 2010-04-21 21:33:46 UTC (rev 111232)
@@ -10,7 +10,8 @@
- Check readability of the scanned application form
- If applicant and reference committer are (well)-known, proceed
with procedure. Otherwise ask the reference committer about
- the applicant. Note that the reference committer must be an active committer.
+ the applicant. Note that the reference committer must be an
+ active committer.
2) Create SVN account for new committer::
@@ -38,13 +39,8 @@
One last step, though: you need to deposit your SSH public key(s) as
described:
- http://docs.zope.org/developer/becoming-a-contributor.html
+ http://docs.zope.org/developer/becoming-a-committer.html
Best regards,
<<<SENDER>>>
-
-
-
-
-
Modified: developer_docs/trunk/source/subversion-writable-checkouts.rst
===================================================================
--- developer_docs/trunk/source/subversion-writable-checkouts.rst 2010-04-21 21:26:54 UTC (rev 111231)
+++ developer_docs/trunk/source/subversion-writable-checkouts.rst 2010-04-21 21:33:46 UTC (rev 111232)
@@ -7,7 +7,7 @@
Before you start
================
-Make sure you have :doc:`registered as a contributor <becoming-a-contributor>`.
+Make sure you have :doc:`registered as a committer <becoming-a-committer>`.
More information about the checkins
mailing list