Hi, 2012/10/30 Helena Mitasova <[email protected]>: > I agree with Glynn and Ben, > when working with students on 50+ different projects it is really great to > have everything > in one package and not to worry about which additional tool to install and > whether it will work with the latest release. > We used to have the code split into core, alpha and several other groups and > it was pain to maintain, > I think it works much better now and the toolbox concept should be > implemented at the GUI level.
sure on the other hand all GRASS modules included in trunk (or main branch) should be solid, well tested and actively *maintained*. Note that the GRASS development team is relatively small. > Maybe PSC should have some mechanism to decide on which add-ons to move to > trunk based on a defined set of criteria. We definitely need to define some criteria. Probably we should also review which addons modules should go to trunk (well written, maintained), and which should go from trunk to addons (not maintained, rarely used, seriously broken). >From my POV, r.modis or r.streams.* modules are examples of the modules which should go to trunk. Martin -- Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
