Figure out how this space could work!
My thinking here is that we have about half a dozen people consistently and actively engaged in product maintenance and another dozen or so irregularly engaged at a fairly productive level. We also have some specific offers of assistance that we have not taken up.
I feel that the people who are doing this work are collaborating very well but not necessarily prioritising and co-ordinating well. For example the top 3 goals in my opinion are
- To get critical issues down to x
- To get pull requests down to y
- To figure out a constructive, blame-free way of diagnosing and learning from regressions (and to draw a line in the sand when the process kicks in and only worry about fixing regressions prior to that point). Note that this goes beyond tech & involves ensuring we are triaging incoming issues. Also we should know that we are always fixing regressions for the next possible release. I feel this happens pretty well once they are identified.
I deliberately left the numbers blank because I feel those should be set collaboratively, but I would like to see a team goal of let's get critical issues down to x by this date.