13 | | For inspiration, we have a wish-list of [report:1 projects and feature requests]. Just pick a task from the list. It may be a good idea to send a small posting to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list] to announce your activities (maybe someone will join you!). Please read [wiki:HowToProgram how to write source code]. We appreciate if you can fix [http://trac.osgeo.org/grass/query?status=%21closed&type=defect&order=id&desc=1 bugs] etc. Using the Ticket system is the best way to submit code contributions if you don't have write access to SVN. See for example #33. |
| 14 | For inspiration, we have a wish-list of [report:1 projects and feature requests]. Just pick a task from the list. It may be a good idea to send a small posting to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developers mailing list] to announce your activities (maybe someone will join you!). Please read [wiki:HowToProgram how to write source code]. We appreciate if you can fix [http://trac.osgeo.org/grass/query?status=%21closed&type=defect&order=id&desc=1 bugs] etc. |
| 15 | |
| 16 | The Trac ticket system is the best way to submit your code contributions if you don't have write access to SVN, and (even for those with write access) the preferred way to submit more radical changes for general review. See for example trac ticket #33. |
| 17 | * Submit your code and documentation patches [http://trac.osgeo.org/grass/newticket here]. |
| 18 | * [http://grass.osgeo.org/wiki/Patches How to create a patch] - they should be generated versus the latest development SVN (trunk). |
24 | | * In general, the [http://grass.gdf-hannover.de/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]). |
25 | | * The requester has to '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2). |
26 | | * The request has to be sent to the GRASS-PSC [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list], stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below). |
| 29 | |
| 30 | The typical process for new developers to gain full write access to the Main GRASS SVN repository is that for some mentorship period they send patches to the grass-dev mailing list (or the trac system) for existing old timer developers to review and commit. Full SVN access generally happens when the mentor has seen enough patches that they trust the person's code (committing it unchanged) and eventually get bored reviewing & rubber stamping all their patches. It is assumed during this period that a track record of trust will be established via participation on the grass-dev mailing list. At some point the mentor nominates the new developer on the PSC mailing list for full write access, and a vote happens. |
| 31 | |
| 32 | * In general, the [http://grass.osgeo.org/wiki/PSC GRASS Project Steering Committee] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]). |
| 33 | * The new developer must '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2). |
| 34 | * An email must be sent to the [http://lists.osgeo.org/mailman/listinfo/grass-psc GRASS-PSC mailing list] by the new developer stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the PSC mailing list. After a period of evaluation, SVN write access may be granted and is set up in the OSGeo authentication system (see below). |