[GRASS-PSC] Contributing a Python add-on

[Luí­s Moreira de Sousa]

Thank you Markus.

I am going now through the checklist. The pep8config.txt file is supposed to be in /tools but it is not there. Where can I find it?

Thanks.

--
Luís Moreira de Sousa
Im Grund 6
CH-8600 Dübendorf
Switzerland

Phone: +41 (0)79 812 62 65
Email: luis.de.sousa at protonmail.ch
URL: https://sites.google.com/site/luismoreiradesousa

-------- Original Message --------
Subject: Re: [GRASS-PSC] Contributing a Python add-on
Local Time: May 23, 2017 5:48 PM
UTC Time: May 23, 2017 3:48 PM
From: neteler at osgeo.org
To: Luí­s Moreira de Sousa <luis.de.sousa at protonmail.ch>
GRASS-PSC <grass-psc at lists.osgeo.org>

Dear Luí­s,

On Thu, May 18, 2017 at 3:32 PM, Luí­s Moreira de Sousa
<luis.de.sousa at protonmail.ch> wrote:
> Dear all,
>
> I would like to contribute a Python add-on to GRASS named r.mblend [0]. I
> have read and accept the Legal Aspects of Code Contributions [1]. My OSGeo
> epithet is Lads [2].
>
> Thank you and regards.
>
> [0] https://github.com/ldesousa/r.mblend
> [1] https://trac.osgeo.org/grass/wiki/RFC/2_LegalAspectsOfCodeContributions
> [2] https://wiki.osgeo.org/wiki/User:Lads

... sorry for the delay.

I have created your account and added your record in
"grass-addons/contributors.csv" in r71117.

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20170524/101cf87b/attachment.html>