transfer / release / claim invalid project `forge` (pep-541)
See original GitHub issueAccording 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.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
User support ticket system #3231 - pypi/warehouse - GitHub
transfer / release / claim invalid project forge (pep-541) #4001 ... Does flagging a project refer to flagging name-squats?
Read more >Transfer of Claim Other Than For Security | United States Courts
Transfer of Claim Other Than For Security. Download Form (pdf, 267.91 KB). Form Number: B 2100A. Category: Bankruptcy Forms. Effective onDecember 1, 2015....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.Sure:
dfee
.