[GRASS-dev] Should we use GitHub Discussions?

Veronica Andreo veroandreo at gmail.com
Thu Feb 11 12:34:21 PST 2021


Hello everybody,

I wonder if this discussion should also be moved to a RFC [1]. What do you
think?
If yes, is there anyone willing to draft it detailing background,
advantages,
disadvantages and alternatives?

It might be interesting to know how many OSGeo projects use it and how it
works for them. It was mentioned here that QGIS PSC is considering to close
it,
but what about others?

my 2 cents

Cheers,
Vero

[1] https://trac.osgeo.org/grass/wiki/RFC

El mié, 10 feb 2021 a las 15:28, Stefan Blumentrath (<
Stefan.Blumentrath at nina.no>) escribió:

> Hi,
>
>
>
> Personally, I tried being active on StackExchange. However, even though I
> do like to support colleagues using GRASS and the project in general, the
> GIS SE system somehow put me off. I just did not like the attitude there
> and would myself not even think about asking questions there...
>
>
>
> That said, GitHub discussions can be different. But I still would very
> much prefer the mentioned option to “modernize” the ML system.
>
>
>
> I also think that if people could register at OSGeo (and MLs) with other
> accounts (Github, Google, …) that could lower entrance barriers. But that
> is a different, and probably more complicated (?) issue…
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* grass-dev <grass-dev-bounces at lists.osgeo.org> *On Behalf Of *Vaclav
> Petras
> *Sent:* onsdag 10. februar 2021 04:10
> *To:* Markus Neteler <neteler at osgeo.org>
> *Cc:* GRASS developers list <grass-dev at lists.osgeo.org>
> *Subject:* Re: [GRASS-dev] Should we use GitHub Discussions?
>
>
>
>
>
>
>
> On Tue, Feb 9, 2021 at 3:59 PM Markus Neteler <neteler at osgeo.org> wrote:
>
> On Tue, Feb 9, 2021 at 9:50 PM Vaclav Petras <wenzeslaus at gmail.com> wrote:
> > On Tue, Feb 9, 2021 at 4:01 AM Markus Neteler <neteler at osgeo.org> wrote:
> >>
> > If we had a presence on StackExchange like QGIS has, we wouldn't be
> having a discussion about GitHub Discussions in the first place.
>
> Try this:
>
> https://gis.stackexchange.com/questions/tagged/grass
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgis.stackexchange.com%2Fquestions%2Ftagged%2Fgrass&data=04%7C01%7C%7Cd289d555eb8644f3d43b08d8cd716c87%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637485234341778088%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Dyz48Pe%2BEiOOvQUrep6ECt%2BSC3nqjdQMhE31keICWV8%3D&reserved=0>
> --> 2,027 questions
>
>
>
> I wish this would indicate a healthy community and I wish we would have
> one there. However, with a small sample from questions with recent
> activity, I see only a couple of users answering (2 or so; BTW thanks! you
> know who you are) and from the 2027 questions tagged grass, there are "475
> questions with no upvoted or accepted answers" [1]. This does not sound
> like what is in the original Nyall's email against QGIS using GitHub
> Discussions which says "there's LOTS of informed users answering all the
> QGIS questions on gis.stackexchange." [2]. Perhaps even more telling is
> that no one except myself [3] mentioned GIS StackExchange in this
> discussion up until now.
>
>
>
> [1] https://gis.stackexchange.com/questions/tagged/grass?tab=Unanswered
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgis.stackexchange.com%2Fquestions%2Ftagged%2Fgrass%3Ftab%3DUnanswered&data=04%7C01%7C%7Cd289d555eb8644f3d43b08d8cd716c87%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637485234341778088%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vXJOTBmVYkQUaQrCppWC%2BKOx2Zc0A%2FZBvpq%2FDHihlso%3D&reserved=0>
>
> [2] https://lists.osgeo.org/pipermail/qgis-psc/2021-February/009244.html
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fpipermail%2Fqgis-psc%2F2021-February%2F009244.html&data=04%7C01%7C%7Cd289d555eb8644f3d43b08d8cd716c87%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637485234341788080%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6uw%2ByA0iOlGsHjIS4OwE%2BJTuak6D1akR6lNoc1b8l5o%3D&reserved=0>
>
> [3] https://lists.osgeo.org/pipermail/grass-dev/2021-January/094867.html
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fpipermail%2Fgrass-dev%2F2021-January%2F094867.html&data=04%7C01%7C%7Cd289d555eb8644f3d43b08d8cd716c87%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637485234341788080%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bT8voloK2cCwwcXKGe78qt7awV8nLB4JeR0wjnK3HIg%3D&reserved=0>
>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210211/74577e64/attachment.html>


More information about the grass-dev mailing list