[tech] Tech/Wheel Meeting 2022-03-26 14:00 - 24 hour reminder

[Andrew Adamson]

Apologies, I am unable to make this meeting due to other commitments.

Andrew Adamson
bob at ucc.asn.au

|"If you can't beat them, join them, and then beat them."                |
| ---Peter's Laws                                                        |

On Fri, 25 Mar 2022, root wrote:

> Tech/Wheel Meeting Agenda - Saturday 2022-03-26 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 recording minutes for
>     meeting n (beware mid-meeting glitches) and ensuring meeting n+1 reminders succeed:
>   - Copying the following checklist into a new issue under [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues]] (or clone #32) , and assigning it to yourself.
>     - This is to keep track of any async secretarial duties detailed ahead. See our new Action Items section below.
>   - [ ] ACTION: Save and commit the minutes of today's meeting, during the meeting; and at the end
>   - [ ] ACTION: Set and (later) verify reminders of next meeting:
>     - [ ] 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)
>     - [ ] Update the crontab: `motsugo# crontab -e`
>     - [ ] 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
>   - sprocket+winadmin should happen faster!
>     - [I2N] ?
>     - samuel_04 ?
>     - anyone from the 2022 committee keen?
> - 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 agenda that it's been completed, and and briefly discuss if need be
> - Try to keep meeting chaired and flowing quickly, then finish up and try to ACTION some items
>   - e.g. we're here to occasionally take stock and unblock things, not _make_ useful things wait until meeting n+1
>     - too many attendance-or-apologies-expected meetings are draining, c.f. UCCCleanup busybees
>   - e.g. briefly commiserate that our systems for keeping things up-to-date suck, but then get to it
> 
> ### Action items to discuss
> 
> ## Known Broken Stuff
> - `ucc-adduser-ad` can't be allowed to get too slow or flakey with optional parts, but... bulk actions should happen soon
>   - via: `/services/uccdnsci/webdeploy-reload` and similar?
>   - `mooneye:/etc/bind/domains/primary/zonemake.py`
>   - `mussel:systemctl restart apache2' on mussel`
>   - `mailfish:/home/other/mailman/adduser/$NEWUSER` subscribe-to-list (not ucc-announce): https://lists.ucc.gu.uwa.edu.au/mailman/listinfo/ucc
> - https://calendar.google.com/calendar/embed?src=rb44is9l4dftsnk6lmf1qske6g%40group.calendar.google.com&ctz=Australia%2FPerth
>   - repopulate? replace?
> - [NTU] discord #events -> #announcements tweaking has broken who can post to it from IRC
>   - https://discord.com/channels/264401248676085760/264401248676085760/956394160640884766
>   - can we check/fix bidirectional bridging of that channel?
>   - ensure dd discord-irc bot (via webhook) can post to #announcements
>   - what roles are missing the "Manage Event" permission? https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events#h_01FGJENQGRMPEPJCTCP2KGADQV
>   - discord-irc is freshly upgraded, thanks [TRS] @2022-03-23
>     - https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/16
> 
> ## Matters arising previously
> - Routine upgrades
>   - Trying to get to a baseline of Debian 11
>     - and even that needs a round of upgrade+reboot
>   - unpackaged/unmanaged stuff...
> 
> ## 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 add ./$(date +%Y-%m-%d).txt
> git commit -m "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/bob%40ucc.gu.uwa.edu.au
>