[tech] Tech/Wheel Meeting 2022-08-29 18:30 - scheduled
wheel-reminder at ucc.asn.au
wheel-reminder at ucc.asn.au
Tue Jul 19 21:00:01 AWST 2022
Tech/Wheel Meeting Agenda - Monday 2022-08-29T18: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 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:
- Checklist follows:
- Clone and reopen a new issue from [[https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32]]
- 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"
- Reopen it and assign it to yourself
- Update the title for today
- [ ] 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
- [] 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
### 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: -->
More information about the tech
mailing list