Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve custodial issues for this repo and others #231

Open
jaraco opened this issue Jan 10, 2022 · 0 comments
Open

Solve custodial issues for this repo and others #231

jaraco opened this issue Jan 10, 2022 · 0 comments

Comments

@jaraco
Copy link
Contributor

jaraco commented Jan 10, 2022

Since I no longer have access to yougov/velociraptor and yougov/vr.*, I'm no longer able to administer settings such as to add a secret to CI to enable releases of tagged commits. Yet I'm still the sole owner of at least some of the vr.* projects in PyPI. As a result, after making maintenance changes to the project (such as in yougov/vr.launch#6 (comment)), there's no one with sufficient access to both configure the project in Github and in PyPI.

I'd like to continue to share in the maintenance of velociraptor, but I don't feel terribly strongly about it.

So I propose the following options in my order of preference:

  1. Create a new org (vr and velociraptor are taken, so it'd need to be something else, like vr-paas). I would share admin access on that org. All velociraptor projects would be transferred to that org. I would grant co-ownership of the PyPI packages.
  2. Transfer the VR projects to my personal account (jaraco). I would grant collaborator access to the repos and maintainer access to PyPI.
  3. I'll transfer PyPI access to someone at YouGov and relinquish maintainership of the projects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant