On 1 November 2012 12:29, Markus Neteler <[email protected]> wrote: > On Wed, Oct 31, 2012 at 10:33 PM, Glynn Clements > <[email protected]> wrote: > > > > Moritz Lennert wrote: > > > >> > I suggest that modules should not simply be moved from addons to > >> > trunk, but that a developer has a close look at a module including > >> > testing before moving it to trunk. > >> > >> +1, but I see Martin's point about lack of dev power. So the trade-off > >> has to be between quality of code and value added of having a > >> functionality in trunk even if the code is not perfect. > > > > Relegating something to add-ons is a reliable way to reduce the amount > > of developer oversight it gets. E.g. currently you can't just "make" > > the add-ons/grass7 directory (it lacks a Makefile), > > Now there is. >
Thanks ! > > > so most developers > > won't even try to compile it. If the modules were in trunk, developers > > may notice errors or warnings as part of the normal build process. > > Agreed. > > I also think that we need the toolbox concept rather at GUI level than > at directory level. > +1 there was an earlier discussion about using modules keywords to make module groups... > > Markus > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Yann Chemin
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
