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: ***@***.***>

[rsbivand]

@stevenpawley Thanks so much for converting to roxygen in #97 ! I've checked locally with R 4.4.1 and today's R-devel on GRASS 8.4.0 (and GDAL 3.10.0rc3), all OK. I regenerated the online docs with pkgdown too (ef72593). I bumped the version number and updated DESCRIPTION.

[rsbivand]

@stevenpawley Should we aim to transfer maintainer and submit when CRAN comes back in early January? We'd also need to transfer ownership of this repo, and regenerate docs at your github account. A next step once that is done would be to ask r-spatial.

Alternatively, we could ask them first, including Rsagacmd at the same time.

There is was a NO_REMAP problem in C++ code in terra, which would need resolving first - the current github HEAD on master is clean (checked), so I expect an early submission.

[stevenpawley]

Hi Roger,

Early January works for me, although I like the idea of moving to r-spatial (and Rsagacmd as well) - maybe this can all be done in one step, before submitting to CRAN?

I wonder - would it make sense for rgrass to reside in the OSGEO GitHub organization directly? Other than GRASS itself, there is a growing number of GRASS-related repos in there, including tutorials, workshop-related repos, etc.

Also, very soon, I'll try and finish a pull request that I've been working on to get rgrass running with a basic test suite in GitHub Actions, testing against some LTS ubuntu versions and the GRASS releasebranch Docker image.

[rsbivand]

Hi Steven,

A test suite with GitHub Actions would be very valuable. I see that qgisprocess uses the Geocompuation with R docker image as a low-effort entry point, but in GHA uses QGIS more directly: https://github.com/r-spatial/qgisprocess/blob/49ffca7362597582ae1d2e890c3cc46342d7874a/.github/workflows/R-CMD-check.yaml#L58-L102 and other variants. I guess your approach would resemble that.

I also like the idea of using the OSGEO GitHub organization, @florisvdh @veroandreo what do you think? We are an OSGeo community project https://www.osgeo.org/projects/r-spatial/, so there is also a proper link.