Feature request: Display "Unmaintained" flag at the Project table level
Opened this issue · 2 comments
BadgeApp has been around long enough that some projects are dead repos at this point. When looking at the project table https://www.bestpractices.dev/en/projects there is no quick way to identify these. As such it is possible for a project to be listed as 99% met leading the viewer to to the wrong conclusion about the project. It would be good to see flag that indicates a project is no longer maintained if the criteria listed for "The project MUST be maintained." was previously true but no longer meets that criteria any longer:
When a project knows that it will no longer be maintained, it should set this criterion to "Unmet" and use the appropriate mechanism(s) to indicate to others that it is not being maintained. For example, use “DEPRECATED” as the first heading of its README, add “DEPRECATED” near the beginning of its home page, add “DEPRECATED” to the beginning of its code repository project description, add a no-maintenance-intended badge in its README and/or home page, mark it as deprecated in any package repositories (e.g., npm deprecate), and/or use the code repository's marking system to archive it (e.g., GitHub's "archive" setting, GitLab’s "archived" marking, Gerrit's "readonly" status, or SourceForge’s "abandoned" project status). Additional discussion can be found here.
Although being flagged as "unmaintained" my be found by drilling down into a specific project, having that clearly visible at the top level would be highly beneficial.
Thanks for the consideration.
-kenny
It's not clear to me that that this is a NEW flag - we already have a criterion for being maintained, namely "maintained".
I propose instead that if a project is known to be unmaintained (that is, "maintained" is "Not Met"), then we put a banner near the top of the badge entry, stating that "This project is no longer maintained (see [maintained])" or something like that.
Also: We do need a way to withdraw badges if no one's checked it in a long time. The "obvious" way to do it is to add a passing criteria like "badge answers have been validated within the last 3 years by a badge applicant". That means every 3 years someone the badge will drop unless someone does something.
"Flag" is probably the wrong term for me to have used for what I was thinking for the reason that you've stated.
What I was suggesting is that some manner of visual indication at this level that a project is no longer longer in compliance would be beneficial.
At the project page level I like your idea of a banner as you suggest and your suggestion of the passing criteria "recheck" every 3 years is a good one. :-)
-kenny