>>! In T78617#849924, @jayvdb wrote:
> But we also need better tools/strategies to better plan low/lowest priority bugs - these are the bugs which take 'forever' to be fixed, and cause disenfranchisement when the various 'stakeholders'' have different expectations about the priority that should be given to the problem. I don't see how Priority Low/Lowest/Needs volunteer/None/whatever is part of the solution to the 'long tail' problem.
Very true. While we continue developing tools and processes helping the mainly professional developers deal better with the higher priority tasks, the long tail of lower priority tasks that are not even considered in anybody's backlogs keeps growing.
We need to be better at
* providing mechanisms for external contributors to identify low priority tasks that should be promoted in project backlogs
* promoting easy tasks suitable for new / casual / junior contributors
* connecting popular priorities with maintainers' plans
* reviewing contributions fast (see T78768)
* closing marginal tasks that clearly have little to no chance to be addressed ever
What else? And which specific actions can we take here and now to start solving the problem?
**See Also (though not "low priority" per se):**