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

transfer / release / claim invalid project forge (pep-541) #4001

Closed
dfee opened this issue May 16, 2018 · 7 comments
Closed

transfer / release / claim invalid project forge (pep-541) #4001

dfee opened this issue May 16, 2018 · 7 comments
Assignees

Comments

@dfee
Copy link

dfee commented May 16, 2018

According to PEP-0541, projects that conform to the following behavior are subject to removal project is name squatting (package has no functionality or is empty);.

forge is an example of a project like this:

  • v0.0 was initially published on Mar 19, 2010 with no code and project description: "not released yet"
  • it's 2018 (8 years later on Friday) and there has been no update.

I've attempted to get a hold of Mark Ramm (by email, linkedin, and twitter) to transfer ownership, and haven't heard back from him.

I've also sought resolution on the pypa-dev mailing list, and was directed here.

Unlike other PEP-541 requests, this seems pretty clear cut. Let me know how to proceed.

@dfee
Copy link
Author

dfee commented May 20, 2018

@brainwane where does the current process stand? I've looked through the tickets and can't figure out if the PEP 541 workflow is inactive, if I need to provide more information, etc.

Do you / pypa have any clarity on when these sorts of issues will be resolved? Is it in my best interest to publish my software under a different name, or to wait? Again, if the answer is "wait", then how long?

Thanks

@di
Copy link
Member

di commented May 22, 2018

@dfee Right now we are working on adding the necessary admin features to be able to take action on PEP 541 requests, to do so in a fair way to all users, and to be able to organize them in a way that is not incredibly time-consuming for the volunteers who will be responding to them (e.g.: #3231, #4011, #4022).

Since this is an entirely volunteer-driven project, it's not really possible to provide a timeline. I can say that these issues are my current highest priority, when I am able to find the time to work on them.

What you've done so far is exactly the right thing to do, and I'll be happy to address your request once said features are in place.

@dfee
Copy link
Author

dfee commented May 22, 2018

@di great response. Thanks for adding that context.

@yeraydiazdiaz yeraydiazdiaz self-assigned this Apr 6, 2019
@yeraydiazdiaz
Copy link
Contributor

Hello @dfee, sorry for the delay on processing this request.

I've tried contacting Mark by email and hopefully he will come back to us soon regarding your claim.

As you mention the project has a single empty release which falls under the name squatting bullet point of invalid projects category in PEP 541. If it's ok with you we'll give Mark some time respond to my email and otherwise take action.

@yeraydiazdiaz
Copy link
Contributor

Hello @dfee, Mark has not responded in a timely fashion to my attempt to contact him so we'll proceed to transfer ownership of the package to you.

Can you confirm your PyPI username for me, please?

@dfee
Copy link
Author

dfee commented Apr 23, 2019

Sure: dfee.

@di
Copy link
Member

di commented Aug 7, 2019

Done. Please note that you won't be able to make a release with version 0, 0.0, 0.0.0, etc. as this was previously used.

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

4 participants