[GRASS-SVN] r30175 - grass-web/trunk/devel

Fri Feb 15 17:25:44 EST 2008

Author: neteler
Date: 2008-02-15 17:25:44 -0500 (Fri, 15 Feb 2008)
New Revision: 30175

Modified:
   grass-web/trunk/devel/devel.inc
Log:
tons of links updated

Modified: grass-web/trunk/devel/devel.inc
===================================================================

--- grass-web/trunk/devel/devel.inc	2008-02-15 22:05:19 UTC (rev 30174)
+++ grass-web/trunk/devel/devel.inc	2008-02-15 22:25:44 UTC (rev 30175)
@@ -2,7 +2,7 @@
 
 
  <A HREF="#list">Mailing list</A> -
- <A HREF="#software">Download/CVS</A> -
+ <A HREF="#software">Download/SVN</A> -
  <A HREF="#help">Help wanted!</A> -
  <A HREF="#compile">Compiling GRASS</A> -
  <A HREF="#prog">Programmer's Manual</A> -
@@ -22,7 +22,7 @@
 <a href="../community/index.php">worldwide network of developers</a>
 continue to release new GRASS versions (see 
 <a href=grasshist.html>GRASS history</a>, see also 
-<a href="http://web.soccerlab.polymtl.ca/grass-evolution/cvs-stat/overall/index.html">CVS statistics for GRASS 6</a>).
+<a href="http://web.soccerlab.polymtl.ca/grass-evolution/cvs-stat/overall/index.html">SVN statistics for GRASS 6</a>).
 <p>
 The strength and success of GRASS relies on the user community. This in
 mind, the philosophy of the GRASS Development Team is to encourage users to
@@ -56,7 +56,7 @@
 Please join our mailing list, which will help and coordinate ongoing
 development in GRASS GIS development. Join the list if you are
 a programmer and/or want to follow the development discussion. If you have
-questions concerning compilation of the CVS-GRASS, please ask here.
+questions concerning compilation of the SVN-GRASS, please ask here.
 <p>
 <ul>
 <li><b>How do I subscribe to GRASS Developers Mailing List?</b><br>
@@ -79,12 +79,11 @@
 
 <a name=software></a>
 <h2> Download the latest GRASS software</h2>
-To follow GRASS development, get the latest code from CVS server:
+To follow GRASS development, get the latest code from SVN server:
 <ul>
-<li> <a href=../download/index.php>Download official GRASS releases</a>
-<li> <a href=cvs.php>CVS repository</a> (latest code)
-<li> New Developers: <a href=http://freegis.org//grass/howto_grass-sshcvs.en.html>How to get
-GRASS CVS write access with ssh</a>. To get a personal password, please
+<li> <a href="../download/index.php">Download official GRASS releases</a>
+<li> <a href="http://trac.osgeo.org/grass/wiki/DownloadSource">SVN repository</a> (latest code)
+<li> New Developers: <a href="http://grass.gdf-hannover.de/wiki/Requesting_SVN_write_access">How to get GRASS SVN write access</a>. To get a personal password, please
 contact the developers on the <a href="http://lists.osgeo.org/mailman/listinfo/grass-dev">GRASS developers mailing list</a>
 </ul>
 <p>
@@ -163,7 +162,7 @@
 trustable people who agree to the GRASS rules of code contributions (see below):
 
 <ul>
-<li> Legal aspects of code contributions (RFC2): these <a href="http://mpa.fbk.eu/markus/grass63progman/rfc/">rules</a> have to be accepted to gain CVS write access
+<li> Legal aspects of code contributions (RFC2): these <a href="http://mpa.fbk.eu/markus/grass63progman/rfc/">rules</a> have to be accepted to gain SVN write access
 <li> C language coding standards: Check your code against the rules defined in the
      'SUBMITTING' file (find it in the main directory of the GRASS source
      code and also <a href=../grass63/source/SUBMITTING>SUBMITTING</a>). This ensures
@@ -179,20 +178,19 @@
 <li> Python coding standards: Check your code against the rules defined in the
      'SUBMITTING_PYTHON' file (currently developed <A HREF="http://grass.gdf-hannover.de/wiki/GRASS_and_Python#SUBMITTING_PYTHON_proposal">here</a>).
 <li> Code submission: Please contact a member of the 
-     <A HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/AUTHORS">GRASS Development Team</a>
+     <A HREF="http://trac.osgeo.org/grass/browser/grass/trunk/AUTHORS">GRASS Development Team</a>
      or write to the development mailing list (see <A HREF="#list">above</a>).<br>
-     In general, please generate differences to the current CVS instead of sending
+     In general, please generate differences to the current SVN instead of sending
      full files:<br>
      <tt>cvs diff -u [file.c] > grassdiff</tt><br>
      You may send this file 'grassdiff' to a member of the
-     <A HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/AUTHORS">GRASS Development Team</a>.
+     <A HREF="http://trac.osgeo.org/grass/browser/grass/trunk/AUTHORS">GRASS Development Team</a>.
 <li> GRASS Add-on Wiki submission: <a href="http://grass.gdf-hannover.de/wiki/GRASS_AddOns">go here</a> (Add-on code
      is hosted on your server)
 <li> GRASS Add-on SVN repository: We maintain a SVN repository for group-wide code development. You can
-     ask the developers for write access, but you have to agree to the <a href="http://mpa.fbk.eu/markus/grass63progman/rfc/">Legal aspects of code contributions (RFC2)</a> and the code SUBMITTING standards (see in the <a href="https://grasssvn.fbk.eu/grasssvn/grassaddons/trunk/grassaddons/">SVN repository</a>).
+     ask the developers for write access, but you have to agree to the <a href="http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html">Legal aspects of code contributions (RFC2)</a> and the code SUBMITTING standards (see in the <a href="http://trac.osgeo.org/grass/browser/grass-addons">SVN repository</a>).
 <li> Already submitted code which is not (yet) integrated: <a href=../outgoing/>OUTGOING
      directory</a> - maybe you can work on this?
-<li> GRASS <a href="http://freegis.org//grass/howto_grass-sshcvs.en.html">CVS write access</a> for developers
 </ul>
 
 <A name="quality">

