<div dir='auto'><div>Hi All,</div><div dir="auto"><br></div><div dir="auto">My apologies, but I will not be attending tonight's tech meeting, as I've still got a cough that I don't think people will appreciate being in the vicinity of.</div><div dir="auto"><br></div><div dir="auto">Kind regards,</div><div dir="auto">Dylan Hicks [333]<br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On 6 Oct 2024 18:30, tech-reminder@ucc.asn.au wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Tech/Wheel Meeting Agenda - Monday 2024-10-07T18:30
<br>
===================================================
<br>
- VENUE: UCC Clubroom
<br>
- and online at https://meetings.ucc.asn.au/b/tech
<br>
<br>
*Meeting opened HH:MM*
<br>
<br>
## Attendance
<br>
- Present
<br>
- Apologies
<br>
- [NTU]
<br>
- Absent
<br>
<br>
## Next meeting
<br>
- Schedule next meeting
<br>
- *day 2024-mm-ddTHH:MM
<br>
- 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:
<br>
- Checklist follows:
<br>
- Clone a new issue from [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32]]
<br>
- Right now, before the meeting is underway and everyone is waiting; then reopen it and assign it to yourself
<br>
- This issue is to keep track of any async secretarial duties detailed ahead
<br>
- Type `/clone` into the "Write a comment" box as a "quick action"
<br>
- Update the title to match today's date
<br>
- [ ] ACTION: Save and commit the minutes of today's meeting, during the meeting (yes, really); and at the end
<br>
- [ ] ACTION: Set and (later) verify reminders of next meeting:
<br>
- [ ] Promptly update `agenda.next` with the TIME/DATE/VENUE
<br>
- [ ] 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)
<br>
- [ ] Update the crontab: `motsugo# crontab -e`
<br>
- [ ] Check at T-7days that the notice really went out, fix for T-4days if needed
<br>
- [ ] Everyone, before next meeting: Curate `agenda.next`, and move any items you think should be tracked as GitLab issues into GitLab issues, as above
<br>
<br>
<br>
## Optional items - choose at the start of the meeting
<br>
- [ ] Ethical guidelines
<br>
- [ ] Monitoring
<br>
- [X] Backups
<br>
- Proxmox/PBA demo
<br>
- [ ] Password rotations
<br>
- [ ] New members
<br>
- [ ] Quick check of ChangeLog
<br>
- [ ] Lessons learnt
<br>
<br>
## Current Action Items
<br>
- ACTION: [TPG] work out how to add "realms"/"universes" to `zonemake.py`
<br>
- ACTION: [GPO] [I2N] Pester UWAIT about firewalled IPs
<br>
- ACTION: [MTL] [TPG]: Get docker container ansible SOE finished, and then start UCC mastodon instance
<br>
- ACTION: [MTL] [MPT] [GPO] [NTU]: Update ucc-mailman to mailman3
<br>
- ACTION: [MTL] [MPT] [GPO]: Seperate mussel's functions into seperate functions, separate VMs
<br>
- ACTION: [GPO] [NTU] [DBA] to rotate uccpass passwords
<br>
- ACTION: [GPO] [CJN] to fix OpenVPN and look at other VPN setups
<br>
- ACTION: [333] to fix the speed of uccroot `push.sh`
<br>
- migrate to `ansible` ?
<br>
- ACTION: ALL to add changes or work you have done to https://wiki.ucc.asn.au/Changelog
<br>
- ACTION: [333] (to draft and send) [BRD] (to proofread) to send an email to @wheel for reminding proper good'ol days documentation & communication
<br>
- ACTION: [333] to update welcome-to-wheel document.
<br>
- ACTION: Brainstorm improvements to wheel onboarding process.
<br>
- ACTION: Brainstorm wheel offboarding process, and checking if people still want/need their wheel access.
<br>
- ACTION: [ROY] [GPO] [NTU] to write a documentation/record for Proxmox 6->8 upgrade
<br>
- already documented on upstream's wiki? or email update to tech@?
<br>
<br>
### Boilerplate/Review
<br>
- Review GitLab bug list: [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/]]
<br>
- Briefly discuss anything iff needed, but don't spend too long rehashing previous meetings ;)
<br>
- Then:
<br>
- New actions/ACTION items: put them in the minutes once, but add to bug list to minimise repeat discussion
<br>
- Ongoing actions: don't keep them in the agenda, summarise updates - iff needed
<br>
- Completed actions: mention in the agenda that it's been completed, summarise - iff needed
<br>
<br>
### Action items to discuss
<br>
<br>
## Known Broken Stuff
<br>
<br>
## Matters arising previously
<br>
<br>
## Extra items (rename/refile as appropriate)
<br>
<br>
*Meeting closed HH:MM*
<br>
<br>
----
<br>
<br>
```
<br>
# https://hedgedoc.ucc.asn.au/t6u3DLnHTNyrnxR-AuYLGg
<br>
cd /home/wheel/docs/meetings
<br>
wget -O ./$(date +%Y-%m-%d).txt https://hedgedoc.ucc.asn.au/t6u3DLnHTNyrnxR-AuYLGg/download
<br>
# HEDGEDOC_SERVER=https://demo.hedgedoc.org /home/wheel/bin/hedgedoc export --md W***DemoDocID*** ./$(date +%Y-%m-%d).txt
<br>
git add ./$(date +%Y-%m-%d).txt
<br>
git commit -m "Tech meeting minutes $(date +%Y-%m-%d)"
<br>
```
<br>
<br>
<!-- vim: tabstop=2 softtabstop=2 shiftwidth=2 expandtab
<br>
-->
<br>
<!-- Local Variables: -->
<br>
<!-- tab-width: 2 -->
<br>
<!-- End: -->
<br>
_______________________________________________
<br>
List Archives: http://lists.ucc.gu.uwa.edu.au/pipermail/tech
<br>
<br>
Unsubscribe here: https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/dylanh333%40ucc.asn.au
<br>
</p>
</blockquote></div><br></div></div></div>