[GRASS-PSC] GRASS add-on sharing and write access

Markus Neteler neteler at osgeo.org
Thu Dec 14 11:47:00 PST 2017


Dear Nagy,

On Thu, Dec 14, 2017 at 12:24 PM, Nagy Edmond <nagy.edmond.eno at gmail.com> wrote:
> Dear GRASS-PSC,
>
> Recently, I've been working with least-cost paths in GRASS, and to save up
> time, I decided to automate the process by writing an add-on that generates
> a vector output resembling a network from a set of input vector points. It
> is mostly based on r.cost/r.walk and r.drain.
>
> I would be happy to share it with the community, and include it into the
> official repository. To build some trust, I considered uploading the py
> script on GitHub for you to look at the code, but I wasn't sure if that
> would be acceptable. I can still do it if there is no problem.

Feel free to post the link to the repo here.

> I have also read the RFC2 and accept the legal consequences. Unfortunately I
> don't have a mentor, but I would appreciate if someone kindly suggested
> someone.

We'll collectively assist you :)

> My "osgeo_id" is "eno91".

Welcome!

I have now activated the access and added your record to
"grass-addons/contributors.csv" in r71939.

Here some hints: Please, prior to submission, check your code and
manual contributions against the rules defined in the document
Submitting (and its subsections):

https://trac.osgeo.org/grass/wiki/Submitting
--> Submitting rules

This ensures a smooth integration into the standard GRASS code base
and avoids portability problems.

The "What's next" we addressed here:
https://trac.osgeo.org/grass/wiki/HowToContribute#Thenwhat

Happy coding,
Markus

--
Markus Neteler
GRASS GIS PSC Chair
http://grass.osgeo.org


More information about the grass-psc mailing list