[tech] Tech/Wheel Meeting 2024-03-05 18:30 - 24 hour reminder

[Conor Bennett]

Hi all,

I am also going to be unavailable tomorrow.

Kind regards,
Conor Bennett

On Mon, 4 Mar 2024, 8:59 pm James Arcus, <jimbo at ucc.asn.au> wrote:

> Hi all,
>
> I will either only be able to attend online, or not at all, as I will
> have to work late tomorrow.
>
> In any case, I will update the agenda ahead of time with relevant
> things...
>
> Cheers,
>
> James [MPT]
>
> On 2024-03-04 18:30, tech-reminder at ucc.asn.au wrote:
> > Tech/Wheel Meeting Agenda - Tuesday 2024-03-05T18:30
> > ====================================================
> > - VENUE: UCC Clubroom
> >   - and online at https://meetings.ucc.asn.au/b/tech
> >
> > *Meeting opened HH:MM*
> >
> > ## Attendance
> > - Present
> > - Apologies
> > - Absent
> >
> > ## Next meeting
> > - Schedule next meeting
> >   - *day 2024-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:
> >   - Checklist follows:
> >     - Clone a new issue from
> > [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32]]
> >       - Right now, before the meeting is underway and everyone is
> > waiting; then reopen it and assign it to yourself
> >       - This issue is to keep track of any async secretarial duties
> > detailed ahead
> >       - Type `/clone` into the "Write a comment" box as a "quick
> > action"
> >       - Update the title to match today's date
> >   - [ ] ACTION: Save and commit the minutes of today's meeting, during
> > the meeting (yes, really); 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
> > previous or 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
> > - [ ] Quick check of ChangeLog
> > - [ ] Lessons learnt
> >
> > ## Current Action Items
> > - ACTION: [MPT] to ask Unigames if they would like to keep
> > `unigames.(guild|gu).uwa.edu.au`
> > - ACTION: [TPG] work out how to add "realms"/"universes" to
> > `zonemake.py`
> > - ACTION: [333] [GPO] Proxmox upgrading preparation
> > - ACTION: [GPO] [I2N] Pester UWAIT about firewalled IPs
> > - ACTION: [MTL]: Get docker container ansible SOE finished, and then
> > start UCC mastodon instance
> > - ACTION: [MTL] [MPT] [GPO] [NTU]: Update ucc-mailman to mailman3
> > - ACTION: [MTL] [MPT] [GPO]: Seperate mussel's functions into seperate
> > functions, separate VMs
> > - ACTION: [333] to properly investigate Proxmox Backup, even if that's
> > just trying it at home and reporting back.
> > - ACTION: [GPO] [NTU] [DBA] to rotate uccpass passwords
> > - ACTION: [GPO] [333] [I2N] look into PAM 2FA systems for SSH
> > - ACTION: [GPO] [CJN] to fix OpenVPN and look at other VPN setups
> > - ACTION: [333] to look into Magikarp Ceph OSD.3: underlying Samsung
> > 860 Pro SSD is dead
> > - ACTION: ALL to add changes or work you have done to
> > https://wiki.ucc.asn.au/Changelog
> >
> > ### Boilerplate/Review
> > - Review GitLab bug list:
> > [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/]]
> > - Briefly discuss anything iff needed, but don't spend too long
> > rehashing previous meetings ;)
> > - Then:
> >   - New actions/ACTION items: put them in the minutes once, but add to
> > bug list to minimise repeat discussion
> >   - Ongoing actions: don't keep them in the agenda, summarise updates
> > - iff needed
> >   - Completed actions: mention in the agenda that it's been completed,
> > summarise - iff needed
> >
> > ### 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 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.gu.uwa.edu.au/pipermail/tech
> >
> > Unsubscribe here:
> > https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/jimbo%40ucc.asn.au
> _______________________________________________
> List Archives: http://lists.ucc.gu.uwa.edu.au/pipermail/tech
>
> Unsubscribe here:
> https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/cjnb%40ucc.asn.au
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucc.gu.uwa.edu.au/pipermail/tech/attachments/20240304/c93a3bf6/attachment-0001.htm>