[Checkins] SVN: developer_docs/trunk/ - add svn:ignores

Chris Withers chris at simplistix.co.uk
Fri Apr 3 11:11:52 EDT 2009 

Log message for revision 98843:
  - add svn:ignores
  - remove outdated references to account.php
  - slightly more logical ordering and structuring
  - general tidyup.

Changed:
  _U  developer_docs/trunk/
  U   developer_docs/trunk/source/becoming-a-contributor.rst
  U   developer_docs/trunk/source/index.rst
  U   developer_docs/trunk/source/subversion-writable-checkouts.rst

-=-

Property changes on: developer_docs/trunk
___________________________________________________________________
Added: svn:ignore
   + .installed.cfg
bin
build
eggs
develop-eggs
parts


Modified: developer_docs/trunk/source/becoming-a-contributor.rst
===================================================================
--- developer_docs/trunk/source/becoming-a-contributor.rst	2009-04-03 14:37:33 UTC (rev 98842)
+++ developer_docs/trunk/source/becoming-a-contributor.rst	2009-04-03 15:11:52 UTC (rev 98843)
@@ -6,28 +6,40 @@
 
 2. Print, fill out and sign the `Zope Committer Agreement <http://foundation.zope.org/agreements>`_
 
-3. Submit the agreement in one of 3 ways as a scanned copy or through fax
-   or through postal mail to the `Zope Foundation <http://foundation.zope.org/about>`_
+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 nag jim at zope.com, or J1m on the freenode #zope3 IRC channel.  A
    reasonable time depends on the way the agreement was sent, as described above.
 
-4. Upload your SSH public key at: https://cvs.zope.org/upload-key.html
+5. Deposit your SSH public key(s) as described in the section below.
 
-   When you go to that page, you'll get a basic auth login prompt.  Use your
-   www.zope.org login and password.
+6. Do a :doc:`writeable checkout <subversion-writable-checkouts>`.
 
-   If you have trouble, **do not ask Jim Fulton for help.**  Ask for help on
-   the IRC channels. People there may ask me to look at ssh logs on the server or
-   at the uploaded keys, as I am able to access those.
+Depositing your SSH public key(s)
+---------------------------------
 
-   One thing to keep in mind is that the user id you use to access the
-   subversion and CVS repositories is your zope.org user id.  This means that you
-   might have to specify a id explicitly. I know of two ways to do this:
+Your SSH public key(s) must be uploaded using the application at: 
+https://cvs.zope.org/upload-key.html
 
-   - Include it in the subversion url: svn+ssh://your_zope_org_id@svn.zope.org/repos/main/some_path
+When you go to that url, you'll get a basic auth login prompt.  Use your
+www.zope.org login and password.
 
-   - Specify the user if to use for svn.zope.org (or cvs.zope.org) in your SSH configuration.
-     See the SSH documentation for details.
+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	2009-04-03 14:37:33 UTC (rev 98842)
+++ developer_docs/trunk/source/index.rst	2009-04-03 15:11:52 UTC (rev 98843)
@@ -5,6 +5,15 @@
 Welcome to Zope Developer Information's documentation!
 ======================================================
 
+Becoming a Zope contributor
+---------------------------
+
+.. toctree::
+   :maxdepth: 2
+
+   becoming-a-contributor
+
+
 Zope Subversion Repository
 --------------------------
 
@@ -15,15 +24,6 @@
    subversion-writable-checkouts
    subversion-ui
 
-Becoming a Zope contributor
----------------------------
-
-.. toctree::
-   :maxdepth: 2
-
-   becoming-a-contributor
-
-
 Zope CVS Repository (obsolete)
 ------------------------------
 

Modified: developer_docs/trunk/source/subversion-writable-checkouts.rst
===================================================================
--- developer_docs/trunk/source/subversion-writable-checkouts.rst	2009-04-03 14:37:33 UTC (rev 98842)
+++ developer_docs/trunk/source/subversion-writable-checkouts.rst	2009-04-03 15:11:52 UTC (rev 98843)
@@ -4,44 +4,17 @@
 Below are instructions for hooking up with our Public Subversion repository
 with checkin ability.  
 
-Overview
-########
+Before you start
+================
 
-Public Subversion checkin access uses the Subversion SSH tunneling mode.
-You get registered for checkin access by the "cvs master",
-mailto:cvs-admin at zope.org, which provokes an email message with
-instructions for depositing your SSH public key(s) via the web.
-Once that's done, you're set to do the checkouts, all detailed
-below.
+Make sure you have :doc:`registered as a contributor <becoming-a-contributor>`.
 
 
-Depositing your SSH public keys
-###############################
 
-When you're registered for public access, you'll get an email directing you
-to
-
-    - https://cvs.zope.org/account.php
-
-
-where you can deposit your SSH public keys.  Your key deposit is protected
-by your zope.org account name and password.  (Until we finish institution of
-the new Zope.org site, the synchronization of the key-deposit view of the
-account DB is poor, so you may need "cvs master", mailto:cvs-admin at zope.org
-intervention to get this right...)
-
-You can use RSA or DSA, ssh v1 or v2 keys, or any combination.
-
-You can revisit the key deposit page any time to put in new keys - but you
-will have to resubmit any keys of the same type as new ones your submitting,
-since the process replaces the entire corresponding authorized keys file
-(authorized_keys or authorized_keys2).
-
-
 Doing checkouts (Linux, MacOS-X, Un*X)
-######################################
+======================================
 
-Any time ssh makes an RSA-key connection for subversion it will require
+Any time ssh makes a key connection for subversion it will require
 your key passphrase.  You can use ssh-agent to stash that key once for your
 shell, and not have to specify it again while you're issuing commands from the
 same shell.  It's worthwhile getting acquainted with ssh-agent - check the man
@@ -52,8 +25,7 @@
 
     % svn co svn+ssh://username@svn.zope.org/repos/main/Zope/trunk Zope
 
-You, of course, should substitute the zope.org account name by which you
-are registered.
+You should substitute the zope.org account name by which you are registered.
 
 Subversion commands using SSH this way will require you to provide the
 passphrase for the key being invoked - you will be prompted for it
@@ -62,16 +34,19 @@
 
 
 Doing checkouts (Windows)
-#########################
+=========================
 
 Some of the command line access methods that work on non-Windows systems
-don't work on Windows.  The TortoiseSVN project also offers a very nice
-integration of svn commands into the Windows Explorer GUI.
+don't work on Windows.  The 
+`TortoiseSVN <http://tortoisesvn.tigris.org/>`_
+project also offers a very nice integration of svn commands into the
+Windows Explorer GUI.
 
 The easiest way to set up both (command line and TortoiseSVN) for svn+ssh
-access is to first download the popular PuTTY set of connection tools for
-Windows.  Then, as a one-time setup cost, run 'putty.exe' to create a new PuTTY
-session for Zope svn+ssh access:
+access is to first download the popular 
+`PuTTY <http://www.chiark.greenend.org.uk/~sgtatham/putty/>`_ set of 
+connection tools for Windows. Then, as a one-time setup cost, run
+'putty.exe' to create a new PuTTY session for Zope svn+ssh access:
 
 - Under Session, use Host Name 'svn.zope.org', and select the SSH
   protocol.
@@ -82,12 +57,6 @@
 - Under Connection -> SSH -> Auth, enter the path to your private
   key file (whether generated by 'puttygen.exe', or otherwise).
 
-  (Note that private keys generated with !OpenSSH will not work with
-  !TortoisePlink.exe - you'll have to convert your private key to PuTTY's format
-  using 'puttygen.exe' or, conversely, generate a key with 'puttygen.exe'
-  saving it in the !OpenSSH format and update your public key(s) at 
-  https://cvs.zope.org/account.php .)
-
 - Back under Session, save the session under some unique name.  For
   example, 'svnzope'.  Do note that 'svn.zope.org' can be used as
   the name!  The examples here do not, just to make the distinction
@@ -130,6 +99,3 @@
   Then, again, use the name of your saved PuTTY session instead of 'svn.zope.org'
   in svn command lines that need to reference the repository explicitly.
 
-  For the rest, follow the instructions in the non-Windows section above,
-  but use your PuTTY session name as the hostname.
-

More information about the Checkins mailing list