Triage Team: Goals and Processes #18878
Replies: 3 comments 8 replies
-
|
I propose we should use a proliferation of small GitHub Projects, to track a set of short-term goals based around suitably-sized buckets for the date that each issue in the backlog was last updated. I've compiled a table of the counts of still-open issues at time of writing, bucketed by creation year and last-updated year:
'Last Updated' feels like the more important signal here, with issues updated recently being much more likely to still merit technical review than issues that are years stale (i.e. different sorts of effort required). Note that several of these years would need to be broken down further --- I'd offer 1-month buckets for 2026, 2025, and 2024; and quarterly buckets for 2023 and 2022. Point is, to use these features to:
And as far as a model workflow framed to be as actionable as possible: Initial Setup
Ongoing ProcessA member of @micropython/triage-team volunteers to take responsibility for the triage of the Issues or Pull Requests that they choose to, and executes that responsibility by following the steps of either the Basic Triage or Technical Triage process where they remain a useful communication tool to save time and effort, and by applying common sense to deviate from them where appropriate. Basic Triage
Technical Triage
|
Beta Was this translation helpful? Give feedback.
-
|
Lets put the 🐘 on the barbie :-) I think it is best to separate triaging from fixing , or adding features or chiseling bytes from firmware sizes.
Fixing vs adding features / functionality. I feel this is a tougher nut to crack - what is important to me may not be relevant to the community, or it may be orthogonal to Damien's goals.
So
|
Beta Was this translation helpful? Give feedback.
-
|
I have been pondering and reading about what works / does not work in other OSS projects Then I found and I watched a non-technical talk form a very technical guy, Brett Cannon, on OSS Participation. That has me thinking about what I could or cannot do, and what would actually that actually help most, and enjoy it.
"Always remember, your focus determines your reality." So shared focus, over than volume. |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As of writing, there are 1392 open issues and 495 open PRs on micropython/micropython --- including some that were opened all the way back in 2014, twelve years ago!
With the creation of the new @micropython/triage-team, I'd like to propose we break this backlog into a series of more achievable short term triage goals, and to as part of that, adopt and document some specific model workflow for triaging them.
I don't think it would be useful or appropriate to go full middle-manglement with an ISO9000-style process document, or to really even do something that's that close. Many of us, I'm sure, are already far too traumatized for that, by the sort of managers who see such standards as threats to their ego or as conveniently thick to roll up and bludgeon underlings with. Applied conscientiously with the correct motivations at the forefront, though, and abstracted out from more corrupt motives, the underlying ideas do offer something of value even to a community like ours.
In general, as a group of trusted senior members of our volunteer community:
MicroPython should only adopt official goals and recommendations for Triage Team that stand firmly atop the underlying norms we mean them to explain and encourage, and the principled reasons we'd have to encourage them. But for all of the above reasons, we should adopt a set of short-term goals and an accompanying "model workflow" that's as specific and actionable as possible within that.
I have my own specific proposal for how to break the backlog into smaller goals, and model workflow I've framed in a way I think would be appropriate, submitted below. I encourage everyone who cares to to offer their own competing ideas as top-level comments beside it, and any concerns or offered tweaks in replies to them. If you disagree with the concept itself, please make that known with your 👎s and your own top-level comment. (And, if you're motivated to satire, we all need an ego haircut occasionally: call this foolish ten ways and link whichever dilbert strip you need.)
@jonnor @dhylands @mattytrentini @agatti @Josverl @andrewleech @dpgeorge @peterhinch @robert-hh
Beta Was this translation helpful? Give feedback.
All reactions