History for CVSKeyDepositAdminNotes

??changed:
-
To establish CVS checkin accounts (see DoingWritableCheckouts and WriteAccessHintAndTips):

    - Admins need an htpasswd account - on cvs.zope.org, in
      /home/httpd/passwords/htpasswd

      (To generate the crypted password, for example::

        python -c "import crypt;print crypt.crypt('somepw','py')"

      yields "pyeEYoZPWOzl.", ie a crypted form of 'somepw' using salt 'py'.)

    - visit https://cvs.zope.org/admin, using the htpasswd account.

    - Follow "Creates a new user" link, fill out the form - username
      is the critical setting - must be the user's account name on
      zope.org.

      Yields "The user soandso was added."

    - Within a minute or two the user will get an email KeyDepositInvitation 
      message, with instructions for depositing their key.

    - From https://cvs.zope.org/admin, visit the View/Grant 
      commit access screen: https://cvs.zope.org/admin/grant1.php

      (The table you get has a column which indicates whether the
      user's ssh key has been deposited.  Doesn't mean it's _valid_,
      but...)

      Click the "Change" link for the user's entry, and grant them commit
      access to the selected repository

    - The user can deposit their key(s) any time following receipt of
      the key deposit instructions email - another every-minute cron
      job will put the key in the right form and place.

    - Have them test by ssh'ing to cvs.zope.org - they should get not be 
      able to log in, but should get an envvar dump with some CVS 
      complaints.

      When the user depoits the key, they'll wind up at
      KeyDepositCheckoutInstructions.

Vie-o-lah.