3 ms·
Maybe another status "stale" would be the solution here. That way, maintainers would be able to focus on "active" issues while the people who reported the issue
by codethief 6y ago
Maybe another status "stale" would be the solution here. That way, maintainers would be able to focus on "active" issues while the people who reported the issue could still add information to the issue later on to move it from "stale" back to "open" / "active".
- diggan 6y agoI'd reverse it and say you should have a status for when something is done discussed about, and implementation path is clear "Ready for development" or something like that. Then people who are looking for things to develop, they filter by that. Anything that is not "Ready for development" either needs triaging, or another type of closure.