[GRASS-dev] r.modis in GRASS 7 trunk

Markus Metz markus.metz.giswork at gmail.com
Wed Oct 31 01:15:52 PDT 2012


On Wed, Oct 31, 2012 at 5:58 AM, Yann Chemin <yann.chemin at gmail.com> wrote:
>
>
> On 31 October 2012 02:25, Helena Mitasova <hmitaso at ncsu.edu> wrote:
>>
>> 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.
>
>
> Same conclusion here for teaching...

+1
>
>>
>> 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.
>
>
> +1
+1
I think the toolbox concept on GUI level could help users a lot.
>
>>
>> Maybe PSC should have some mechanism to decide on which add-ons to move to
>> trunk based on a defined set of criteria.
>
>
> +1
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.

Markus M
>
> Yann
>
>>
>>
>> Helena
>>
>> On Oct 30, 2012, at 12:53 PM, Glynn Clements wrote:
>>
>> >
>> > Martin Landa wrote:
>> >
>> >>> as a regular user of MODIS, I would like to call other MODIS users to
>> >>> express interest to include r.modis into GRASS 7 SVN.
>> >>
>> >> we cannot extend number of modules in trunk forever. Probably some
>> >> modules should be reviewed and moved to addons.
>> >
>> > Why?
>> >
>> > Keeping modules in trunk ensures that any breakage resulting from
>> > changes to APIs or to the build system will be noticed. Also, the
>> > module will be included in the linkage database created by
>> > tools/sql.sh, and in any recursive grep of the source tree.
>> >
>> > Personally, I'd rather see most "normal" add-ons moved into trunk.
>> >
>> > OTOH, v.in.dwg should be moved to add-ons unless LibreDWG support is
>> > expected in the foreseeable future.
>> >
>> > --
>> > Glynn Clements <glynn at gclements.plus.com>
>> > _______________________________________________
>> > grass-dev mailing list
>> > grass-dev at lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
>
>
> --
> Yann Chemin
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev


More information about the grass-dev mailing list