Transfer of maintainer

[rsbivand]

@florisvdh @VLucet @hellik @veroandreo @petrasovaa @stevenpawley I feel that the demise of grass-dev as a digested mailing list makes this the right point in time to transfer maintenance: https://lists.osgeo.org/pipermail/grass-stats/2024-October/001883.html and https://lists.osgeo.org/pipermail/grass-dev/2024-October/096368.html. I'm grateful to Steven for responding - how should we proceed?

[florisvdh]

My work on the natural environment in Flanders right now makes it difficult to also adopt maintenance of rgrass, and this is probably not going to change the coming years (which is BTW also a happy and useful evolution since just one year). So I'm very happy with Steven's response. I will of course still follow the repo and will be happy to keep contributing at times.

[petrasovaa]

Would it make sense to transfer the repo under r-spatial? I see Steven has Rsagacmd under his account, but in terms of sustainability and visibility, r-spatial seems better, no?

[rsbivand]

Perhaps, let's take things a step at a time. qgisprocess and link2GI and others are there already, so it should be possible.

[stevenpawley]

That’s a great idea - I’ve been thinking of asking to move Rsagacmd there as well, for better visibility and involvement.

…

On Fri, Oct 4, 2024 at 2:30 PM Anna Petrasova ***@***.***> wrote: Would it make sense to transfer the repo under r-spatial <https://github.com/r-spatial>? I see Steven has Rsagacmd under his account, but in terms of sustainability and visibility, r-spatial seems better, no? — Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJKQLUBIAUHVL65ILI2IALZZ33GZAVCNFSM6AAAAABPLVGYPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUGUZDENBQHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>