<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi All,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">This effort stalled rather due to holidays, etc but here is the latest update:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">- The labels.yaml PR has now landed [1].</div><div class="gmail_default" style="font-size:small">- I've now applied the new set of labels to all the repositories. For example, see [2].<br></div><div class="gmail_default" style="font-size:small">- We now have a new ".github" *repository* for storing GitHub template files that are common to all repositories in the Kata Containers GitHub organisation [3].<br></div><div class="gmail_default" style="font-size:small">- We now have a set of issue templates that are being used across all repos [4]. Check out [5] for example!<br></div><div class="gmail_default" style="font-size:small">- Stalebot is being discussed on a separate thread [6].<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Next steps:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">- Create some documentation to explain the labels and how to use them.</div><div class="gmail_default" style="font-size:small">- We need to review open PRs and issues and potentially add some of the new labels to all to help us get a better view on the backlogs.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">For further information, see [7].<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">If anyone has experience of any bots that we could use to apply labels to issues/PRs, please get in contact! ;)</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/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" style="font-size:small">[2] - <a href="https://github.com/kata-containers/runtime/issues/labels">https://github.com/kata-containers/runtime/issues/labels</a></div><div class="gmail_default" style="font-size:small">[3] - <a href="https://github.com/kata-containers/.github">https://github.com/kata-containers/.github</a></div><div class="gmail_default" style="font-size:small">[4] - <a href="https://github.com/kata-containers/.github/tree/master/.github/ISSUE_TEMPLATE">https://github.com/kata-containers/.github/tree/master/.github/ISSUE_TEMPLATE</a></div><div class="gmail_default" style="font-size:small">[5] - <a href="https://github.com/kata-containers/runtime/issues/new/choose" class="cf_div_theme_dark">https://github.com/kata-containers/runtime/issues/new/choose</a></div><div class="gmail_default" style="font-size:small">[6] - <a href="http://lists.katacontainers.io/pipermail/kata-dev/2019-June/000870.html">http://lists.katacontainers.io/pipermail/kata-dev/2019-June/000870.html</a></div><div class="gmail_default" style="font-size:small">[7] - <a href="https://github.com/kata-containers/kata-containers/issues/39">https://github.com/kata-containers/kata-containers/issues/39</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 17 avr. 2019 à 09:45, Hunt, James O <<a href="mailto:james.o.hunt@intel.com">james.o.hunt@intel.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Hi All,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">To follow up on the discussion in the Architecture Committee meeting yesterday, we're trying to make better use of GitHub labels.</div><div class="gmail_default" style="font-size:small"><br></div><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">Take a look at <a href="https://github.com/kata-containers/tests/pull/1466" target="_blank">https://github.com/kata-containers/tests/pull/1466</a>.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">(The reason the PR is in the "tests" repo by the way is that this repo is always cloned when running CI tests for any _other_ repo. That allows us to add additional CI tests on the labels database and labels on issues/PRs. See below for further info if you're interested).</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">__________</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"># The problem</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;white-space:pre-wrap">The Kata GitHub-hosted repositories currently have a variety of labels that can be added to GitHub issues and PRs. However, the current labels suffer from a number of problems:</span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial"><br></span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial">- Some labels refer to the same concept.</span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial">- Only a few of the labels have descriptions.</span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial">- The meaning of some of the labels is unclear.</span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial">- The overall set of labels is not adequate to make intelligent queries on the pool of open issues.</span></div><div class="gmail_default" style="font-size:small"><span style="background-color:transparent;font-size:11pt;white-space:pre-wrap;color:rgb(0,0,0);font-family:Arial">- Labels are not applied consistently to issues.</span></div><div class="gmail_default"><span id="gmail-m_-4599441754850985737m_-825425798463943566gmail-docs-internal-guid-ffc85e4b-7fff-551e-796f-2a6a7be8bbc7"><div class="gmail_default"><span><br></span></div># Plan</span></div><div class="gmail_default"><br><span><p dir="ltr" style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Establish a small set of labels that are succinct, intuitive, documented and which allow us to capture the many dimensions of an issue/PR.</span></p><p dir="ltr" style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><br></span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"># Approach</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><br></span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Create a YAML database of labels that will be used consistently across all Kata repos.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Allow individual repos to supplement the base list of labels by providing their own YAML snippet.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Add tooling to check and view the YAML database files.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Get agreement on the labels to use.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Apply the labels defined in the YAML labels database to all Kata repos.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Add CI checks to validate the labels database.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Review the backlog of issues + PRs across all repos and manually apply labels.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- Start to improve our process by:</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;white-space:pre-wrap">  - Creating GitHub issue templates to auto-label issues.</span><br></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">  - Make the bug triage slightly more formal by having the team review each new issue and apply a few labels (things like priority).</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">  - Consider using Planning Poker to "size" issues and break them down into manageable chunks.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">  - Auto-add labels to PRs showing their relative sizes (by SLOC).</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">  - Start using GitHub projects to manage upcoming releases.</span></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt">  - ...</p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt">The basic mantra is "automate and organise" - we don't want to impose heavy process, but we do want to make better use of our resources. By applying a few well-chosen labels (automatically where possible), we can start to get a clearer picture of the backlog, which will hopefully allow us to clear it down more quickly.</p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt">Labels will allow us to categorise issues and PRs quickly rather than having to trawl through screens of log output, etc. Also, labels will allow teams to focus on particular groups of issues and PRs rather than having to fall back on the dreaded "github ping" to get attention on particular areas.</p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt">Please comment on <a href="https://github.com/kata-containers/tests/pull/1466" target="_blank">https://github.com/kata-containers/tests/pull/1466</a> so we can start moving this forward.</p><p style="font-size:small;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p></span></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><span style="font-family:monospace,monospace;color:rgb(136,136,136)">---</span><br></div><div dir="ltr" class="gmail-m_-4599441754850985737m_-825425798463943566gmail_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"><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>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="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 dir="ltr"><font color="#888888"><span style="font-family:monospace,monospace"><span style="font-family:monospace,monospace">James<br>---</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>