Open Stack

Hi All,

This effort stalled rather due to holidays, etc but here is the latest
update:

- The labels.yaml PR has now landed [1].
- I've now applied the new set of labels to all the repositories. For
example, see [2].
- 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].
- We now have a set of issue templates that are being used across all repos
[4]. Check out [5] for example!
- Stalebot is being discussed on a separate thread [6].

Next steps:

- Create some documentation to explain the labels and how to use them.
- 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.

For further information, see [7].

If anyone has experience of any bots that we could use to apply labels to
issues/PRs, please get in contact! ;)

Cheers,

James

[1] -
https://github.com/kata-containers/tests/blob/master/cmd/github-labels/labels.yaml.in
[2] - https://github.com/kata-containers/runtime/issues/labels
[3] - https://github.com/kata-containers/.github
[4] -
https://github.com/kata-containers/.github/tree/master/.github/ISSUE_TEMPLATE
[5] - https://github.com/kata-containers/runtime/issues/new/choose
[6] -
http://lists.katacontainers.io/pipermail/kata-dev/2019-June/000870.html
[7] - https://github.com/kata-containers/kata-containers/issues/39

Le mer. 17 avr. 2019 à 09:45, Hunt, James O <james.o.hunt at intel.com> a
écrit :

> Hi All,
>
> To follow up on the discussion in the Architecture Committee meeting
> yesterday, we're trying to make better use of GitHub labels.
>
> # TL;DR
>
> Take a look at https://github.com/kata-containers/tests/pull/1466.
>
> (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).
>
> __________
>
> # The problem
>
> 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:
>
> - Some labels refer to the same concept.
> - Only a few of the labels have descriptions.
> - The meaning of some of the labels is unclear.
> - The overall set of labels is not adequate to make intelligent queries on
> the pool of open issues.
> - Labels are not applied consistently to issues.
>
> # Plan
>
> Establish a small set of labels that are succinct, intuitive, documented
> and which allow us to capture the many dimensions of an issue/PR.
>
>
> # Approach
>
>
> - Create a YAML database of labels that will be used consistently across
> all Kata repos.
>
> - Allow individual repos to supplement the base list of labels by
> providing their own YAML snippet.
>
> - Add tooling to check and view the YAML database files.
>
> - Get agreement on the labels to use.
>
> - Apply the labels defined in the YAML labels database to all Kata repos.
>
> - Add CI checks to validate the labels database.
>
> - Review the backlog of issues + PRs across all repos and manually apply
> labels.
>
> - Start to improve our process by:
>
> - Creating GitHub issue templates to auto-label issues.
>
> - Make the bug triage slightly more formal by having the team review each
> new issue and apply a few labels (things like priority).
>
> - Consider using Planning Poker to "size" issues and break them down into
> manageable chunks.
>
> - Auto-add labels to PRs showing their relative sizes (by SLOC).
>
> - Start using GitHub projects to manage upcoming releases.
>
>   - ...
>
>
> 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.
>
>
> 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.
>
>
> Please comment on https://github.com/kata-containers/tests/pull/1466 so
> we can start moving this forward.
>
>
> Cheers,
>
> James
> ---
> https://katacontainers.io/ | https://github.com/kata-containers
> <https://github.com/clearcontainers>
> Open Source Technology Center
> Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
> 1RJ.
>


-- 
James
---
https://katacontainers.io/ | https://github.com/kata-containers
<https://github.com/clearcontainers>
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
1RJ.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katacontainers.io/pipermail/kata-dev/attachments/20190604/130cee85/attachment.html>