[GRASSweb-list] markus: web/devel devel.inc,1.43,1.44

[grass at intevation.de]

Author: markus

Update of /grassrepository/web/devel
In directory doto:/tmp/cvs-serv2695

Modified Files:
	devel.inc 
Log Message:
SVN info added

Index: devel.inc
===================================================================
RCS file: /grassrepository/web/devel/devel.inc,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- devel.inc	23 Mar 2007 15:56:59 -0000	1.43
+++ devel.inc	14 May 2007 18:18:08 -0000	1.44
@@ -157,8 +157,10 @@
 the GRASS community. There are several ways to probably get your code into
 the standard GRASS release. Another option is to host the software on your own
 web page - in this case we can add a link to our "GRASS Add-ons" section. We
-strongly recommend you follow the coding style described in SUBMITTING file
-(which you find in the GRASS source code).
+strongly recommend you follow the coding style described in SUBMITTING files
+(which you find in the GRASS source code). Optionally, for group based development
+we can offer access to the GRASS AddOns-SVN repository which we grant to
+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://freegis.org/cgi-bin/viewcvs.cgi/grass6/rfc/RFC2_PSC.dox?rev=HEAD&content-type=text/vnd.viewcvs-markup">rules</a> have to be accepted to gain CVS write access
@@ -174,6 +176,8 @@
 <li> Tcl/Tk script coding standards: Check your code against the rules defined in the
      'SUBMITTING_TCLTK' file (find it in the main directory of the GRASS source
      code and also <a href=../grass63/source/SUBMITTING_TCLTK>SUBMITTING_TCLTK</a>).
+<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>
      or write to the development mailing list (see <A HREF="#list">above</a>).<br>
@@ -182,8 +186,10 @@
      <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>.
-<li> GRASS Add-on submission: <a href="http://grass.gdf-hannover.de/wiki/GRASS_AddOns">go here</a> (Add-on code
+<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://freegis.org/cgi-bin/viewcvs.cgi/grass6/rfc/RFC2_PSC.dox?rev=HEAD&content-type=text/vnd.viewcvs-markup">Legal aspects of code contributions (RFC2)</a> and the code SUBMITTING standards (see in the <a href="https://grasssvn.itc.it/grasssvn/grassaddons/trunk/grassaddons/">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