Changes between Version 4 and Version 5 of Subversion


Ignore:
Timestamp:
Nov 22, 2005, 9:28:47 PM (16 years ago)
Author:
Dominic Hargreaves
Comment:

Add references to commit policy and browse source

Legend:

Unmodified
Added
Removed
Modified
  • Subversion

    v4 v5  
    1 !OpenGuides source is now held in a subversion repository at https://urchin.earth.li/svn/openguides/. The repository can be browsed with a normal web browser, but to work properly with the code you will need a [http://subversion.tigris.org/project_packages.html Subversion client]. The rest of this document assumes you have found and installed a suitable subversion client.
     1OpenGuides source is now held in a subversion repository at https://urchin.earth.li/svn/openguides/. The repository can be browsed with a normal web browser, but to work properly with the code you will need a [http://subversion.tigris.org/project_packages.html Subversion client]. The rest of this document assumes you have found and installed a suitable subversion client.
    22
    3 
     3You can also browse the repository in a more detailed fashion by using the "Browse Source" function of Trac.
    44
    55== SSL ==
    6 
    7 
    86
    97The repository is SSL protected (primarily to protect authentication passwords) but the certificate is not signed by a well-known CA. You can find out more about the CA and get the root cert from http://www.earth.li/ca/. We recommend that you install this in your browser and subversion client. To install it into your client, download (and preferably verify...) the earth.li-CA.crt file from the site above, put it somewhere convenient and point at it in your ~/.subversion/servers file (if that directory doesn't exist, run "svn help" to create it):
     
    1311}}}
    1412
    15 
    16 
    1713== Commit access ==
    18 
    19 
    2014
    2115Checking code out from the repository is allowed by anyone, but to commit, you need to persuade Dom <dom@earth.li> (the current maintainer) that you should be given access, and supply him with a (preferably GPG signed and encrypted, or placed on a shell machine that he has access to) line for an Apache .htaccess file. You can do this with the htpasswd tool:
     
    2418htpasswd -n your-chosen-username
    2519}}}
     20
     21See CommitPolicy for more on committing code to the project
    2622
    2723== Using Subversion ==