Skip to content

"Dead" project criteria #43

@philvarner

Description

@philvarner

What are the criteria for a project going into the "Dead" category? There are only 4 in it, but there are many others that haven't had commits or releases for years.

I'd propose a couple of heuristics:

  1. Has not updated CI build use the latest version of python within 6 months (e.g., 3.13 released Oct 2024, so any that don't use it by now)
  2. No releases in a year
  3. No human commits in a year (e.g., auto-approved bot dependency updates don't count)

I would also propose that the name "dead" be replace with "unmaintained", since it more accurately describes the status of the project. A "dead" project could still be used in many active codebases, and can become maintained again with single release or commit.

Also, I volunteering to go through and make these changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions