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

Claim abandoned name: slack-cleaner (PEP 541) #11

Closed
7 tasks done
sgratzl opened this issue Mar 27, 2019 · 7 comments
Closed
7 tasks done

Claim abandoned name: slack-cleaner (PEP 541) #11

sgratzl opened this issue Mar 27, 2019 · 7 comments
Assignees
Labels
PEP 541 Package name support requests

Comments

@sgratzl
Copy link

sgratzl commented Mar 27, 2019

I'd like to apply to take ownership of the project name "slack-cleaner" https://pypi.org/project/slack-cleaner/

Reachability

I tried to reach the original author via email (kfei@kfei.net) twice or by filing a issue on the repos github repository (kfei/slack-cleaner#51). However, no response to either of it.

Abandoned projects

A project is considered abandoned when ALL of the following are met:

  • owner not reachable (see Reachability above);
  • no releases within the past twelve months; and
  • no activity from the owner on the project's home page (or no home page listed).

All other projects are considered active.

Continued maintenance of an abandoned project

If a candidate appears willing to continue maintenance on an abandoned project, ownership of the name is transferred when ALL of the following are met:

  • the project has been determined abandoned by the rules described above;
  • the candidate is able to demonstrate their own failed attempts to contact the existing owner;

-> see github issue among others

  • the candidate is able to demonstrate improvements made on the candidate's own fork of the project;

-> my fork: https://github.com/sgratzl/slack-cleaner contains all open Pull Requests added some new features

  • the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; and

a lot of people (as indicated by the stars of the original and the fork project) use the project and encounter the same errors again when installing from pypi since they are stuck to the old version. Thus, being able to update the package with the forked version would simplify things a lot and avoid that the same error is reported multiple times since already fixed in the improved version.

cheers

sam

@di di transferred this issue from pypi/warehouse Oct 25, 2019
@di di added the PEP 541 Package name support requests label Oct 25, 2019
@yeraydiazdiaz yeraydiazdiaz self-assigned this Nov 9, 2019
@yeraydiazdiaz
Copy link

Hello @sgratzl thanks for the detailed report. I have emailed @kfei myself as a moderator. Hopefully we will hear back soon and move your request forward.

@yeraydiazdiaz
Copy link

Hi @sgratzl, I have had no response from the current owner of the project so it is now considered abandoned and will ask an admin to transfer the project to you.

@sgratzl
Copy link
Author

sgratzl commented Jan 5, 2020

thx!

@ewdurbin
Copy link
Member

ewdurbin commented Jan 7, 2020

@sgratzl what PyPI username should the project be transferred to?

@sgratzl
Copy link
Author

sgratzl commented Jan 7, 2020

@sgratzl what PyPI username should the project be transferred to?

it is the same: sgratzl

https://pypi.org/user/sgratzl/

@ewdurbin
Copy link
Member

ewdurbin commented Jan 7, 2020

Transfer complete.

@ewdurbin ewdurbin closed this as completed Jan 7, 2020
@sgratzl
Copy link
Author

sgratzl commented Jan 7, 2020

thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PEP 541 Package name support requests
Projects
None yet
Development

No branches or pull requests

4 participants