Access to oysteR

[csgillespie]

My access has been removed from oysteR

You’ve been removed from the "oysteR" team on the "Sonatype Open Source Community" organization.

If this is intentional, then can we update the DESCRIPTION, and transfer ownership on CRAN.

Note: CRAN is different to pypi. It expects packages to be constantly updated and work with all dependencies.

Thanks

[csgillespie]

Bump @davidkarlsen / @jdillon / @ajbrown / @mpuglin

[bhamail]

Hey Colin! So sorry for the silence. It's only due to not having a clear answer on this end. Rather than continue the silence, let me share a little of what's been happening in the background: Due to a security review, a bunch of access was removed across a bunch of community projects, so removal of your access was NOT directly intentional. We would very much like for you to be able to continue maintaining things here and on CRAN etc. The sticky part is keeping things happy regarding security/secrets/etc and how to do that with the minimum access required for non-Sonatype folks (of which I am now one btw).

Towards that end, do you know off hand what the minimum access you need to get back to speed on this repo? (Short of repo admin?) Feel free to ping me out of band if you prefer. At the very least, know that your comments are not falling on deaf ears.
Thanks! -Dan

[csgillespie]

Thanks @bhamail - no worries, completely understand.

I don't really use GitHub - more a GitLab guy, so what I want to do is:

• Open/Close issues
• Create labels/etc
• Open/close MRs
• Merge/Approve/Commet MRs
• Update GitHub Actions - create/delete/Add some CI variables

I think that's it? I'm not really that opinated about the internal GitHub repo set-up

[csgillespie]

Just bumping this. The current version has a small bug, and I can't push a fix.

'