Replies: 1 comment 1 reply
-
|
Looks good to me! In @w3ctag (specifically in https://github.com/w3ctag/design-reviews/issues) we use milestones as well as labels - we may want to consider this here. We also automatically add an |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Indeed, once an issue is assigned and planned, instead of using a label for the planning target, we could use a milestone instead, that makes more sense. +1 for the automated |
Beta Was this translation helpful? Give feedback.
-
The group decided that it would be good to have labels in our issues to categorize, to plan, and to prepare the agenda. Here is a proposal:
ScorecardsFundamentals-courseSKF…immediate(something we need to do NOW, such as collaborating on an announcement with a deadline)backlog(needs to be discussed and assigned / planned)nice-to-have(we won’t discuss it in the short future, but we think we need to keep it :man-shrugging:) + specific labels for identified milestones such asOSSNA-2023or2022-Q4…<no-label>at creation. The group should regularly triage all the issues without a date label, then after a first triage it goes to one ofimmediate/backlog/nice-to-have. Theimmediates are treated, thebacklogones are discussed, and planned, and when they are planned they inherit a specific label such as Q4 or a specific event.next-meeting: to generate automatically the agenda / to make everyone interested in the issue aware that they might want to attend next meetingcat-orM-if we need for example a way to identify easily the uncategorized or the unplanned issues. We don't necessarily need to overthink it as labels can be changed later.The next step is to discuss this proposal in a group meeting.
Beta Was this translation helpful? Give feedback.
All reactions