Big effort!! Also thanks for doing the same to the repo2docker issues!!
What is your feeling for the trade off between spending time triaging issues and dealing with them then and there?
In my mind triaging is for when there are several people on the project and one person can triage things and that saves time for the rest of the team as they look at their speciality. For small teams where it is more “everyone can/has to tackle everything” it seems not so useful to spend my time triaging because I could just reply then and there (it is highly unlikely that someone else will look). I’ve been wondering however if it is because we don’t triage things that we don’t increase the size of the team of people who items could be redirected to.
One thing I’ve pondered while reflecting on how many notifications we all get and people declaring “bankruptcy on GitHub notifications”: should we strive to only trigger a notification if the person who receives it has a clear next step when they read it? If we could get really good at that then every time there is a notification and you decide to act on it there is a clear thing for you to do. Often it feels like we generate a notification and the people who react to it are greeted with a “yeah well, what am I meant to do here” state. Pondering how/if we can use labels to help with that. Maybe we should collect a list of the next steps that are frequently used and then have a system for “the next step here is step #1234 from our list of next steps”
Stream of thoughts over