Skip to content
This repository was archived by the owner on May 30, 2020. It is now read-only.
This repository was archived by the owner on May 30, 2020. It is now read-only.

claim abandoned package linkchecker #725

@anarcat

Description

@anarcat

Hi!

The linkchecker package has been abandoned by its author (@wummel) for years. The last release on PyPI dates from 2014 and the last commit dates from June 2016, over a year ago.

Because of this, the community has stepped up to create a friendly fork to bring the project back to life. The "linkcheck" organization was created on Github for that purpose (because the "linkchecker" namespace was already taken by an unrelated user) and eventually the linkchecker organization was reclaimed as well (see linkchecker/linkchecker-old.github.io#2). New releases are being made in a new community-maintained project.

A full history of the discussions and various attempts at contacting the maintainer are well documented in wummel/linkchecker#686.

We would like to get back access to the PyPI "linkchecker" namespace/repository. I first posted this on the Sourceforge tracker as this was the only documented process i could find then. But since, I was told that some requests are made here as well, so I'm trying my luck here as well.

I believe linkchecker falls within the scope of abandoned projects as defined by PEP-0541:

  • 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).

We wish to continue maintenance of the project, again as per PEP-0541 the following applies:

  • the project has been determined abandoned by the rules described above;
  • the candidate is able to demonstrate own failed attempts to contact the existing owner; (tried to reach by private email, issue queue, multiple parties, documented in in new organisation to welcome maintainers wummel/linkchecker#686)
  • the candidate is able to demonstrate improvements made on the candidate's own fork of the project; (we made one release since the fork and are consistently reviewing and merging pull requests)
  • the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; and (see below)
  • the maintainers of the Package Index don't have any additional reservations.

Regarding the second to last criteria, we could use the linkcheck namespace (and indeed we have done that for the GitHub orga for a while) but that would mean renaming the whole package, something we'd like to avoid, as this is a friendly fork. Furthermore, "linkcheck" conflicts with other similar tools that already exist. Finally, we'd like to keep an upgrade path for all the users who have linkchecker installed.

My username on PyPI is anarcat and the other members of the organization are documented here:

https://github.com/orgs/linkchecker/people

Thank you for your consideration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PEP 541Issues blocked on the implementation of PEP 541

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions