On Mon, Apr 20, 2015 at 10:02 AM, Markus Neteler <[email protected]> wrote: > > On Fri, Apr 17, 2015 at 9:02 PM, Helmut Kudrnovsky <[email protected]> wrote: > > hi, > > > > looking at http://grass.osgeo.org/grass70/manuals/addons/ there seems to be > > some mess up in short descriptions: > > The incomplete manual pages of r.green*.html are breaking the script > which creates the overview. > I spent already lot of time to work around that but have no more time for that. > > Markus > > PS: Also addon pages must follow > https://trac.osgeo.org/grass/wiki/Submitting/Docs
Perhaps there could be script and page which would show the guilty modules. There are already pages about build of the module. Perhaps there is a way to extent it or clone it to check for (some) submitting rules. There is a script to do static source code analysis for Python code: https://svn.osgeo.org/grass/sandbox/wenzeslaus/grass_py_static_check.py http://grass.osgeo.org/grass71/manuals/libpython/gunittest_testing.html#analyzing-quality-of-source-code > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
