Excellent. Is it technically feasible to involve the whole user community in this? Or would it be easier to restrict to devs with SVN write access?
Ben On 01/19/2011 12:42 PM, Markus Metz wrote: > On Wed, Jan 19, 2011 at 9:14 AM, Anne Ghisla <[email protected]> wrote: >> On Wed, 2011-01-19 at 08:51 +0100, Markus Neteler wrote: >>> On Wed, Jan 19, 2011 at 12:37 AM, Dylan Beaudette >>> <[email protected]> wrote: >>>> On Tuesday, January 18, 2011, Benjamin Ducke wrote: >>>>> That's reassuring, thanks Markus. >>>>> Incidentally, since HTML housekeeping is such a boring >>>>> chore but so crucial: Do you guys think it would make >>>>> sense to have a "man page improvement day", similar to >>>>> a code sprint, but with the whole community dedicating >>>>> perhaps a day to finding problems in man pages and fixing >>>>> them? >>>>> >>>>> I am not just talking about correcting errors, but also >>>>> rephrasing things that are hard to understand or elaborating >>>>> on aspects that aren't explained verbosely enough. >>>>> >>>>> Ben >>>> >>>> Excellent idea! I would participate. >>> >>> Me, too. >>> >>> Also the sphinx'ization (http://trac.osgeo.org/grass/ticket/151) comes to >>> mind. >> >> Me too! >> > Me too. It seems I started something here by forgetting to remove a > paragraph. I always wanted to update the lidar tools man pages but > never got around to do it... > > Markus M > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > > ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
