[GRASS-dev] Contributing to addons on GitHub

[Markus Neteler]

Hi,

Sorry for the late reply.

On Tue, Dec 31, 2019 at 12:03 AM Brendan <brendan.harmon at gmail.com> wrote:
>
> Thanks. Got it.
>
> Documentation with old instructions includes:
>
> How to Contribute
> https://trac.osgeo.org/grass/wiki/HowToContribute#SettingupthenewSVNwriteaccessafteracceptance

... yes, that needs to be done.

> Submitting
> https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons
> https://trac.osgeo.org/grass/wiki/Submitting#SubmittingcodetoSVN

... updated to "Submitting code to GitHub".

> How to SVN
> https://trac.osgeo.org/grass/wiki/HowToSVN

... marked as "historic" with link to new page.

> The GitHub GRASS Addons repo contains SVN_HOWTO.txt

... deleted.

> rather than a git HOWTO like https://trac.osgeo.org/grass/wiki/HowToGit
> I think a link in the README to https://trac.osgeo.org/grass/wiki/HowToGit would help.

... yes, deduplication is the best.

> Submitting Python Code
> https://trac.osgeo.org/grass/wiki/Submitting/Python
> mentions svn diff which could be updated to git diff

...done.

> I believe there was a discussion on the grass-dev list about using Python Black for style.
> Was there a decision? That could be added to this wiki page.

AFAIK no decision. It might be good to come back to this discussion.

Thanks for the links!

Markus