[GRASS-dev] Reviewing GSoC 2017 page

Blumentrath, Stefan Stefan.Blumentrath at nina.no
Wed Jan 25 15:35:41 PST 2017

Thanks, quite some interesting GSoC ideas.

I took the liberty to add one on “tools for generating unit tests from examples in module manuals”. Not sure if that is feasible or out of scope. Please feel free to remove it if you don`t find it suitable (I can`t mentor it anyway).

(which I also very much like to see become reality, esp. a function like “initGRASS()” from rgrass7) I have the question if that by chance is supposed to be related to last years GSoC on a WebGUI for GRASS (see: https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass).

In order to be really useful, WebGRASS would need a console, and here Jupyter was already mentioned as an option. In addition the WebUI struggled quite a bit with renderinig… So will this proposal be complementary?


From: grass-dev [mailto:grass-dev-bounces at lists.osgeo.org] On Behalf Of Vaclav Petras
Sent: torsdag 26. januar 2017 00.22
To: grass-dev at lists.osgeo.org
Subject: Re: [GRASS-dev] Reviewing GSoC 2017 page

Worked. Thanks for tuning the spam filter, Markus. I just put all the new things at the beginning.

On Wed, Jan 25, 2017 at 10:01 AM, Vaclav Petras <wenzeslaus at gmail.com<mailto:wenzeslaus at gmail.com>> wrote:
Can somebody reorder the ideas so that the fresh ideas are at the top? When I try it, I get "Too many links" or "Page not modified".

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170125/c7bb4594/attachment-0001.html>

More information about the grass-dev mailing list