[GRASS-dev] Should we use GitHub Discussions?

Luca Delucchi lucadeluge at gmail.com
Mon Jan 18 05:05:07 PST 2021

On Sun, 17 Jan 2021 at 15:27, Stefan Blumentrath
<Stefan.Blumentrath at nina.no> wrote:
> Dear all,
Dear al,,

> In general, I do agree with Moritz on this.
> In addition to the risk of more fragmented communication, I do appreciate the fact that ML-discussion is archived. Furthermore, GitHub discussion seems to be a feature that locks us more into GitHub and would it make more complicated if we should be forced to move to another platform (given the proprietary nature of GitHub).
> I do also see that some discussion has moved to github issues/PRs, but that is probably only natural, esp. when point of the discussion is specifics of an implementation / change.
> However, to address both valid issues (demand for web-based forum and a coherent communication), we could probably to three things:
> 1. Encourage all contributors to discuss/mention more significant changes on the ML.
> 2. Promote nabble [http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html] on our github repository
> 3. Check whether it would be feasible to sign up to nabble / ML with OAuth/github to make integration more seamless. I have no idea though if this would be feasible at all. Maybe OSGeo admins know?...

I also agree with Mortiz and Stefan

> Cheers
> Stefan


More information about the grass-dev mailing list