PEP 541: Add section on how to request a name transfer #1059
Conversation
|
Changes look good to me. Thanks @takluyver. |
|
I agree it would be good to be more explicit, but I'm not sure what the preferred process actually is - I've asked @ewdurbin and @dstufft to take a look, as I believe Ernest usually handles the mechanics of actually transferring projects, and Donald is still the lead dev for Warehouse, and I'm not sure he really wants the Warehouse issue tracker to also be serving as the pypi.org user ticketing system. |
|
This is accurate to the current state of things. There hasn't been further work to organize a better system/process, so I'd agree that being explicit is probably better than leaving it undefined in the PEP. |
|
We've decided to move these issues to the pypa/pypi-support repo. |
Co-Authored-By: Dustin Ingram <di@users.noreply.github.com>
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
PEP 541 details the rules for transferring ownership of abandoned PyPI projects whose owners cannot be reached. Understandably, this is a common starting point for people who want to claim such projects.
This PR adds explicit information on how to go about getting an abandoned name. In particular, it points people to the Warehouse issues as the place to request a transfer - this seems to be the de-facto standard approach. It also tries to emphasise that this should be a last resort, to hopefully prevent a flood of requests.
I'm happy to change this if a Github issue is not the preferred way to request an ownership transfer. Arguably sending an email doesn't tie it to having a Github account, but on the other hand, a Github issue feels more publicly visible, and is convenient for @ mentioning project owners who are on Github as an additional attempt to contact them. But there should be some pointer for people, whatever the best option is.