[Python-checkins] devguide: Finish the SSH section.

Tue Jan 11 21:56:57 CET 2011

brett.cannon pushed f6e1e82d5968 to devguide:
http://hg.python.org/devguide/rev/f6e1e82d5968
changeset: 81:f6e1e82d5968
user: Brett Cannon <brett at python.org>
date: Tue Jan 11 12:27:53 2011 -0800
summary:
 Finish the SSH section.
files:
 coredev.rst
 faq.rst

diff --git a/coredev.rst b/coredev.rst
--- a/coredev.rst
+++ b/coredev.rst
@@ -48,7 +48,7 @@
 
 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
+form, please change it. This is so that it is easier to assign issues to the
 right person.
 
 
@@ -63,9 +63,20 @@
 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
+You can verify your commit access by looking at
+http://www.python.org/dev/committers which lists all core developers by
+username. You can also execute the follow command and look for the word
+"success" in the output::
 
-XXX Misc/Developers.rst
+ ssh pythondev at svn.python.org
+
+For Windows users using Pageant::
+
+ c:\path\to\putty\plink.exe pythondev at svn.python.org
+
+An entry in the ``Misc/Developers.txt`` file should also be entered for you.
+Typically the person who sponsored your application to become a core developer
+makes sure an entry is created for you.
 
 
 Sign a Contributor Agreement
diff --git a/faq.rst b/faq.rst
--- a/faq.rst
+++ b/faq.rst
@@ -47,50 +47,6 @@
 =========== ============================================================== ==========================================================================
 
 
-Who has commit privileges on the Subversion repository?
--------------------------------------------------------------------------------
-
-See http://www.python.org/dev/committers for a list of committers.
-
-
-How do I verify that my commit privileges are working?
--------------------------------------------------------------------------------
-
-UNIX
-'''''''''''''''''''
-
-If you are listed as a committer at http://www.python.org/dev/committers , then
-you should be able to execute::
-
- ssh pythondev at svn.python.org
-
-and have the following printed to your terminal::
-
- ( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries
- commit-revprops depth log-revprops partial-replay ) ) )
-
-If something else is printed, then there is a problem with your SSH 2 public
-key and you should contact pydotorg at python.org .
-
-Windows
-'''''''''''''''''''
-
-If you are using Pageant, you can verify that your SSH 2 key is set up properly
-by running::
-
- c:\path\to\putty\plink.exe pythondev at svn.python.org
-
-Using the proper path to your PuTTY installation, you should get a response
-from the server that says::
-
- ( success ( 1 2 ( ANONYMOUS EXTERNAL ) ( edit-pipeline ) ) )
-
-If there is a failure, run ``plink`` with ``-v`` to analyse the problem.
-
-If you are using a profile in PuTTY, the best way to test is to try to log in
-through Open.
-
-
 
 What tools do I need to merge between branches?
 -----------------------------------------------
--
Repository URL: http://hg.python.org/devguide
