Hi Tim, (sorry if this gets double-posted - my mailbox was full the first time I sent it)
Here's a link to creating patches for submission to svn: http://grass.osgeo.org/wiki/Patches You can send documentation patches to myself, or, if you would like to contribute on a more permanent basis, ask the Grass PSC for svn repository write privileges (we can always use more volunteers). The wiki seems to be the place for more in-depth explanations, examples, and how-tos, and the manuals tend to be a bit more succinct, but there's no hard and fast rules. If something is unclear in the manuals, then the text should definitely go there. Cheers, -- Eric Patton -----Original Message----- From: grass-dev-boun...@lists.osgeo.org on behalf of Tim Michelsen Sent: Thu 12/10/2009 8:13 PM To: grass-dev@lists.osgeo.org Subject: [GRASS-dev] contributing documentation Hello, what's the best way to provide patches to GRASS documentation like small and more verbose explanations? Where do you draw the limit between simple FAQ items for the wiki and how would an item qualify for the manual pages? Regards, Timmie _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
