3️⃣ Revise "urgent maintenance" into something more positive and actionable #67
Description
One thing that seems to be missing is a way for community members to add context to some of these metrics. I am the former maintainer of four of the five packages highlighted as "Urgent maintenance required" and I will admit that it stung a bit to see that, especially given that two of them (sandpaper and varnish) are under active maintenance by a core team that has been ravaged by funding challenges from the rise of AI in 2022 (leading funders pull investments in education and open source) to the recent fascist policies of the US government leading to opportunities being taken away.
When I saw this callout, I struggled with this: it wasn't clear what the remedy would be for these. I feel like the blanket "urgent maintenance required" callout strips the context of why the package is labelled like this away. I would like to see some way for the community to be able to add this context to say something like:
- "Yes! We are under-resourced! Here is how to help!" or
- "This project is stable! It may be old, but it's been working for year!" or
- "This is not a package and these metrics make no sense!" or
- offering a path for people to find new maintainers for these projects that have been abandoned out of necessity.