Static Analysis Async MoSCoW 15.3
As inspired by #356612 (closed) this is an attempt at a minimal asynchronous process for backlog refinement. This first time we will be focusing on typemaintenance since they require narrower breadth than typefeature
In reality, typebug would likely be easier given the stricter definition of the problem domain, but perhaps we can do that next time
The goal is to determine what should be closed out of backlog. This is not an attempt to weight issues which comes later after we determine whether they are even worth doing.
Rules
MoSCoW rating: (Must, Should, Could, Wont, ?, or Elsewhere).
Extra ratings:
- ? - I don't understand what this is or have an opinion (more explicit than an empty cell)
- Elsewhere - means to send elsewhere in the event we determine this to belong to another team.
- Participation is optional: as long as one person has started we can use an aggregate
- Each team member adds MoSCoW Rating
- [optionally] each team member opens new discoto thread if any issue requires discussion
- Open for 1 week
- After 1 week, @theoretick will compile ratings into overall column. He may take liberties with discrepancies but advertise back here in case others wish to contest
- @amarpatel as DRI for typemaintenance will determine whether to accept overall rating or override (in the future this will be more cross-functional depending on workflow types)
The cutoff for whether to close out "Should"s vs "Could"s vs "Wont"s is TBD.
Review
Currently populated with Development department members, but if others wish to participate, please feel free to add column!
This list is generated via created_at ASC list of SAST type::maintenance
Auto-Summary 🤖
Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:. For example, the following are all valid points:
#### POINT: This is a point* point: This is a point+ Point: This is a point- pOINT: This is a pointpoint: This is a **point**Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:. For example, the following are all valid topics:
# Topic: Inline discussion topic 1## TOPIC: **{+A Green, bolded topic+}**### tOpIc: Another topicQuick Actions
Action Description /discuss sub-topic TITLECreate an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINKLink an issuable as a child of this discussion
Last updated by this job
- TOPIC "Increase test coverage **" #368540 (comment 1034622607)
- TOPIC Add MobSF downstream QA test for custom ruleset... (#330673 - closed) #368540 (comment 1034624061)
- TOPIC Standardize analyzer images with overridable GO... (#277401 (closed)) #368540 (comment 1034917502)
- TOPIC Consider refactoring secure analyzer ruleset package on top of report package #297249 (closed) #368540 (comment 1035834184)
- TOPIC What do yall think of Async MoSCoW? #368540 (comment 1035836815)
- TOPIC CodeQuality data is exposed in MergeRequestWidget (#229383 (closed)) #368540 (comment 1037949525)
- TOPIC SAST & Secret Detection testing & Azure compatibility (#235623 (closed)) #368540 (comment 1037964046)
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascending
See the settings schema for details.