[tech] Tech/Wheel Meeting 2022-01-08 14:00 - 24 hour reminder

[Lyndon White (Frames)]

My apologies.
Due to covid restrictions I am unable to attend the wheel meeting.

[*OX]

On Fri, 7 Jan 2022, 6:01 am root, <root at ucc.gu.uwa.edu.au> wrote:

> Tech/Wheel Meeting Agenda - Saturday 2022-01-08 14:00
> ===================================================
> - VENUE: UCC Clubroom
>   - and online at https://meetings.ucc.asn.au/b/tech
>
> *Meeting opened 14:mm*
>
> ## Attendance
> - Present
> - Apologies
> - Absent
>
>
> ## Next meeting
> - Schedule next meeting
>   - *day 2022-MM-ddTHH:mm
> - ACTION: [???] shall be this meeting's secretary! This entails:
>   - Copying the following checklist into a new issue under [[
> https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues]], and assigning it
> to yourself.
>     - This is to keep track of any async secretarial duties detailed
> ahead. See our new Action Items section below.
>   - [ ] Set and verify reminders of next meeting: `motsugo# crontab -e`
>   - [ ] Promptly update agenda.next with the TIME/DATE/VENUE
>   - [ ] Perform initial curation of agenda.next, and move any longstanding
> action items out of it and into GitLab (see Action Items section below).
>   - [ ] Check at T-7days that the notice really went out, fix for T-4days
> if needed
> - [ ] Everyone, before next meeting: Curate agenda.next, and move any
> items you think should be tracked as GitLab issues into GitLab issues, as
> above.
>
>
> ## Optional items - choose at the start of the meeting
> - Ethical guidelines
> - Monitoring
> - Backups
> - Password rotations
> - New members
> - Quick check of ChangeLog
> - Lessons learnt
>
>
> ## Current Action Items
> ### Boilerplate
> - Now maintained in GitLab at [[
> https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/]]
> - Briefly discuss anything in here that's worth discussing, but don't
> spend too long rehashing unresolved issues that have already been discussed
> ;)
> - Going forward:
>   - New actions: when new ACTION items arise, put them in the minutes
> once, but add to GitLab
>   - Ongoing actions: don't keep them in the agenda, unless they definitely
> need to be discussed in the next meeting
>   - Completed actions: mention in the agend that it's been completed, and
> and briefly discuss if need be
>
> ### Action items to discuss
>
>
> ## Known Broken Stuff
>
>
> ## Matters arising previously
>
> ## Extra items (rename/refile as appropriate)
>
> *Meeting closed HH:mm*
>
> ----
>
> ```
> # https://demo.hedgedoc.org/Hlsapf47RsqpgIjqLVfMUw
> cd /home/wheel/docs/meetings
> HEDGEDOC_SERVER=https://demo.hedgedoc.org /home/wheel/bin/hedgedoc export
> --md Hlsapf47RsqpgIjqLVfMUw ./$(date +%Y-%m-%d).txt
> git commit -am "Tech meeting minutes $(date +%Y-%m-%d)"
> ```
>
> <!-- vim: tabstop=2 softtabstop=2 shiftwidth=2 expandtab
> -->
> <!-- Local Variables: -->
> <!-- tab-width: 2 -->
> <!-- End: -->
> _______________________________________________
> List Archives: http://lists.ucc.asn.au/pipermail/tech
>
> Unsubscribe here:
> https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/oxinabox%40ucc.asn.au
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucc.gu.uwa.edu.au/pipermail/tech/attachments/20220108/b5f9d34f/attachment.htm>