[tech] New ACTION item tracking process for tech/wheel (Tech Todo List)

[Dylan Hicks]

Hi All,

As discussed in today's wheel meeting, we're now hoping to track our action items in GitLab instead of the growing backlog of "Matters arising previously" in the meeting minutes.

Action items are now recorded as Issues in a new GitLab repository named "Tech Todo List" at the below URL, and these can be directly assigned to people (who will then get an email notification accordingly), can be triaged with various tags like "nice-to-have" or "majorly-borked", and should generally be easier to manage in this manner.
https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues

Access to this repository is controlled via membership in the GitLab `wheel` group, which unfortunately isn't synced with the AD/LDAP group of the same name (but can - and does - still have AD users as group members).
As such, if you're missing from this GitLab group and you're a wheel member, let us know, and we can add you in.

Going forward, here is the new process we're intending to follow:
- Capture any new action items in the wheel meeting minutes
- Create a corresponding issue in the above GitLab repo, with as much detail as is reasonable, so that people know what it's about
    - Give it a tag and assign it to someone, if you can
    - This makes it easier to prioritise issues where stuff is "majorly-borked" over the sea of "nice-to-have" issues that we don't always get the time/motivation to action, but ideally should still keep on our todo list
- Do not include the action item in agenda.next, unless:
    - It's a new action item that will be raised in the meeting to which that agenda corresponds, ie. as above; or
    - Further discussion specifically needs to take place around that action item during the next meeting; or
    - The action item has been completed and should be reported as such in the next meeting

This will hopefully streamline our meeting minutes, and make it easier to track and manage action items we've assigned ourselves, rather than running `grep -C 'ACTION: [???]' /home/wheel/docs/meetings/*.txt` to get a list of actions we've each committed to doing, and these taking up space in every meeting's minutes until they're completed.

If anyone has any feedback, queries, suggestions, objections, or anything else pertaining to this new process, please don't hesitate to reply(-all)!

--
Thanks, and kind regards,
Dylan Hicks [333]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucc.gu.uwa.edu.au/pipermail/tech/attachments/20211114/bd57fc3c/attachment.htm>