<div dir="ltr"><div class="gmail_default" style="font-size:small"># TL;DR</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Our issue backlog is huge. We intend to resolve this. If you'd like to get involved, please let us know!</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># Background<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">As discussed in the Architecture Committee meeting earlier today, we're planning to attack the issue backlog as it hasn't been reviewed holistically for... maybe ever!</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I've added details on the issues to the Kata Rota wiki page [1], so if you are on the rota it would be great if you could start looking at issues too.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">We currently have 1,023 open issues [2], 922 of which don't have associated PRs (meaning they are _not_ "in progress") so we have a bit of work to do! ;-)</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># Work done so far</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">1) Ariel and I have had a brainstorming session to come up with a simple plan for attacking the backlog.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">2) We've created a new GitHub project Kanban board [3] with the intention of using this to manage the issue backlog.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">3) We've written a simple CLI tool using hub [6] that can add issues to github projects.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># The plan</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><div class="gmail_default">1) Make use of one of the GitHub actions [4][5] that can be used to auto-add newly opened issues from *all* the Kata repos into the new project.</div><div class="gmail_default"><br></div><div class="gmail_default"></div></div><div class="gmail_default" style="font-size:small">2) Run the hub script as a "one off" to add the existing open issues in all the repos into the new project.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">3) Hold a regular (probably weekly) meeting to review the backlog on the Kanban board [3].</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">3.1) Consider re-enabling the stalebot [3.1] trigger [3.2] that used to auto-close issues that hadn't seen activity for a long time [3.3].</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">4) Start making better use of labels to allow us to categorise and data-mine the backlogs.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">For example, more intelligent handling of bug and feature issues for example, ensuring they are applied and also back-ported and forward-ported as appropriate. We actually have a YAML database that documents all our GitHub labels [7] along with some simple tooling to keep the list of labels across the repos in sync.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">4.1) We probably need to review the (rather large) list of labels and refine it slightly.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Once we have a more refined set of labels, we should consider trying to make better use of them (for issues and PRs) particularly at the issue triage stage to categorise the issues.<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">5) Report back to the Architecture Committee on progress and findings.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">6) Consider creating a Kanban board for the PR backlog to make that easier to manage too.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">7) Share what we've learnt with the community</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Explain the new Kanban process and best practises for labelling issues.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># Feedback</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">The task of actually reducing the issue backlog could take some time and we may need to modify our approach as we learn more.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">As always, if anyone has thoughts on the above, please let us know. We'll assume "silence means compliance"! :-)<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># Willing helpers (that means you!)</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">If you'd like to get involved in any of the above (particularly the actual reviewing of issues), again, please let us know ;-)</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Cheers,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">James</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">[1] - <a href="https://github.com/kata-containers/community/wiki/Review-Team-Rota">https://github.com/kata-containers/community/wiki/Review-Team-Rota</a></div><div class="gmail_default" style="font-size:small"><div class="gmail_default">[2] - <a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+">https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers</a>+<span style="color:rgb(136,136,136);font-family:monospace,monospace"></span></div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font color="#888888"><span style="font-family:monospace,monospace"><span class="gmail_default"></span></span></font>[3] - <a href="https://github.com/orgs/kata-containers/projects/23">https://github.com/orgs/kata-containers/projects/23</a></div><div dir="ltr">[3.1] - <a href="https://github.com/apps/stale">https://github.com/apps/stale</a></div><div dir="ltr">[3.2] - <a href="https://github.com/kata-containers/.github/blob/master/.github/stale.yml">https://github.com/kata-containers/.github/blob/master/.github/stale.yml</a></div><div>[3.3] - Maybe; I'd like to think that we won't need to use such a feature if we can reduce the backlog down to a more manageable size.</div><div class="gmail_default"></div></div></div></div></div></div></div></div></div></div><div class="gmail_default" style="font-size:small">[4] - <a href="https://github.com/marketplace/actions/assign-to-one-project">https://github.com/marketplace/actions/assign-to-one-project</a></div><div class="gmail_default" style="font-size:small">[5] - <a href="https://github.com/marketplace/actions/github-project-automation">https://github.com/marketplace/actions/github-project-automation</a></div><div class="gmail_default" style="font-size:small"></div><div class="gmail_default" style="font-size:small">[6] - <a href="https://github.com/github/hub">https://github.com/github/hub</a></div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default">[7] - <a href="https://github.com/kata-containers/tests/blob/master/cmd/github-labels/labels.yaml.in">https://github.com/kata-containers/tests/blob/master/cmd/github-labels/labels.yaml.in</a></div><div class="gmail_default"></div><div dir="ltr"><span style="font-family:monospace,monospace;color:rgb(136,136,136)"></span></div><div dir="ltr"><font color="#888888"><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace">---</span></span></font></div><div dir="ltr"><a href="https://katacontainers.io/" style="color:rgb(17,85,204);font-family:monospace,monospace" target="_blank">https://katacontainers.io/</a><span style="color:rgb(136,136,136);font-family:monospace,monospace"> | <a href="https://github.com/clearcontainers" target="_blank">https://github.com/kata-containers</a></span><font color="#888888"><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace"><br></span></span></font></div><div dir="ltr"><font color="#888888"><font face="monospace, monospace">Open Source Technology Center</font><br><font face="monospace, monospace">Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.</font></font><br></div></div></div></div></div></div></div></div></div></div></div></div>