[Python-checkins] devguide: Start the core dev intro doc.

[brett.cannon]

brett.cannon pushed c5b66e8ff490 to devguide:

http://hg.python.org/devguide/rev/c5b66e8ff490
changeset:   78:c5b66e8ff490
user:        Brett Cannon <brett at python.org>
date:        Tue Jan 11 11:15:49 2011 -0800
summary:
  Start the core dev intro doc.

files:
  coredev.rst
  faq.rst

diff --git a/coredev.rst b/coredev.rst
new file mode 100644
--- /dev/null
+++ b/coredev.rst
@@ -0,0 +1,100 @@
+.. _coredev:
+
+How to Become a Core Developer
+==============================
+
+What it Takes
+-------------
+
+When you have consistently contributed patches which have met quality standards
+to be committed without requiring extensive rewrites, you may qualify for
+commit privileges and become a core developer of Python. You must also work
+well with other core developers (and people in general) as you become an
+ambassador for the Python project.
+
+Typically a core developer will offer you the chance to gain commit privilege.
+The person making the offer will become your mentor and watch your commits for
+a while to make sure you understand the development process. If other core
+developers agree that you should gain commit privileges you are then extended
+an official offer.
+
+You may request commit privileges yourself, but do not be surprised if your
+request is turned down. Do not take this personally! It simply means that other
+core developers think you need more time contributing patches before you are
+able to commit them without supervision.
+
+XXX list of people
+
+
+Gaining Commit Privileges
+-------------------------
+
+When you have been extended an official offer to become a Python core
+developer, there are several things you must do.
+
+Mailing Lists
+'''''''''''''
+
+You are expected to subscribe to python-committers, python-dev,
+python-checkins, and one of new-bugs-announce or python-bugs-list. See
+:ref:`communication` for links to these mailing lists.
+
+
+Issue Tracker
+'''''''''''''
+
+If you did not gain the Developer role in the `issue tracker`_ before gaining
+commit privileges, please say so. This will allow issues to be assigned to you.
+
+It is expected that on the issue tracker you have a username in the form of
+"first_name.last_name". If your initial issue tracker username is not of this
+form you can change it. This is so that it is easier to assign issues to the
+right person.
+
+
+SSH
+'''
+
+You need to generate an SSH 2 RSA key to be able to commit code. You may have
+multiple keys if you wish (e.g., for work and home). Send your key as an
+attachment in an email to python-committers (do not paste it in the email as
+SSH keys have specific formatting requirements).
+
+Your SSH key will be set to a username in the form of "first_name.last_name".
+This should match your username on the issue tracker.
+
+XXX verifying
+
+XXX Misc/Developers.rst
+
+
+Sign a Contributor Agreement
+''''''''''''''''''''''''''''
+
+Submitting a `contributor form for Python`_ licenses any code you contribute to
+the Python Software Foundation. While you retain the copyright, giving the PSF
+the ability to license your code means it can be put under the PSF license so
+it can be legally distributed with Python.
+
+This is a very important step! Hopefully you have already submitted a
+contributor agreement if you have been submitting patches. But if you have not
+done this yet, it is best to do this ASAP, probably before you even do your
+first commit so as to not forget.
+
+
+.. _contributor form for Python: http://www.python.org/psf/contrib/
+
+
+
+Read-write Checkout
+'''''''''''''''''''
+
+XXX
+
+
+
+
+Responsibilities
+----------------
+
+XXX
diff --git a/faq.rst b/faq.rst
--- a/faq.rst
+++ b/faq.rst
@@ -9,21 +9,6 @@
 .. contents:: :depth: 3
 .. sectnum::
 
-General Information
-=====================================================================
-
-
-How can I become a developer?
----------------------------------------------------------------------------
-
-Contribute on a regular basis through patches and ask for commit
-privileges once you have demonstrated a track record of being good
-at fixing things.
-
-(Raymond Hettinger commented on the
-`School of Hard Knocks <http://mail.python.org/pipermail/python-dev/2002-September/028725.html>`_ required.)
-
-
 
 Version Control
 ==================================
@@ -34,49 +19,6 @@
 
 .. _download Subversion: http://subversion.apache.org/packages.html
 
-UNIX
-'''''''''''''''''''
-
-If you have checkin rights, you need OpenSSH_.  This is needed to verify
-your identity when performing commits.
-
-.. _OpenSSH: http://www.openssh.org/
-
-Windows
-'''''''''''''''''''
-
-If you have checkin rights, you will also need an SSH client.
-`Download PuTTY and friends`_ (PuTTYgen, Pageant, and Plink) for this.  All
-other questions in this FAQ will assume you are using these tools.
-
-Once you have both Subversion and PuTTY installed you must tell Subversion
-where to find an SSH client.  Do this by editing
-``%APPDATA%\Subversion\config`` to have the following
-section::
-
-  [tunnels]
-  ssh="c:/path/to/putty/plink.exe" -T
-
-Change the path to be the proper one for your system.  The ``-T``
-option prevents a pseudo-terminal from being created.
-
-You can use Pageant to prevent from having to type in your password for your
-SSH 2 key constantly.  If you prefer not to have another program running,
-you need to create a profile in PuTTY.
-
-Go to Session:Saved Sessions and create a new profile named
-``svn.python.org``.  In Session:Host Name, enter ``svn.python.org``.  In
-SSH/Auth:Private key file select your private key.  In Connection:Auto-login
-username enter ``pythondev``.
-
-With this set up, paths are slightly different than most other settings in that
-the username is not required.  Do take notice of this when choosing to check
-out a project!
-
-.. _download TortoiseSVN: http://tortoisesvn.net/downloads
-.. _PuTTY: http://www.chiark.greenend.org.uk/~sgtatham/putty/
-.. _download PuTTY and friends: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
-
 
 How do I get a checkout of the repository (read-only or read-write)?
 -------------------------------------------------------------------------------

--
Repository URL: http://hg.python.org/devguide