<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Apologies.</p>
<p>I've just found out about a family dinner for tonight, so won't
be able to attend<br>
</p>
<p>I was going to raise the topic of the webcam archives after
discussions the last few Mondays. Apparently the webcams
(particularly the archives?) are a put-off for some people joining
the club - only have this third hand, so don't have any more
details than that.<br>
</p>
<ul>
<li>Should we keep them forever? Or start decimating after a few
years?</li>
<ul>
<li>The webcam archive is approximately half of the total disk
usage of `/space`<br>
</li>
</ul>
<li>Should they be restricted to just inside the club network?</li>
<ul>
<li>So randoms on the internet can't trawl them for ML training,
or other nefarious purposes</li>
<li>Very easy to control, as it's just an IP level filter on the
archive page.<br>
</li>
</ul>
<li>Should they be restricted to just committee/wheel (just for
security purposes).</li>
<ul>
<li>This is iffy... there are arguments that the more private
the archives are, they creepier they become.</li>
</ul>
</ul>
<p><br>
</p>
<pre class="moz-signature" cols="72">John Hodge [TPG]
UCC Wheel Member</pre>
<div class="moz-cite-prefix">On 10/4/23 18:30,
<a class="moz-txt-link-abbreviated" href="mailto:tech-reminder@ucc.asn.au">tech-reminder@ucc.asn.au</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20230410103000.6B9BA20019@motsugo.ucc.gu.uwa.edu.au">
<pre class="moz-quote-pre" wrap="">Tech/Wheel Meeting Agenda - Tuesday 2023-04-11T18:30
====================================================
- VENUE: UCC Clubroom
- and online at <a class="moz-txt-link-freetext" href="https://meetings.ucc.asn.au/b/tech">https://meetings.ucc.asn.au/b/tech</a>
*Meeting opened HH:MM*
## Attendance
- Present
- Apologies
- Absent
## Next meeting
- Schedule next meeting
- *day 2023-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 [[<a class="moz-txt-link-freetext" href="https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32">https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/32</a>]]
- Preferably immediately; 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; 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: [333] Research Proxmox Backup Appliance - should fit in well with our existing PVE environment.
- ACTION: [MPT] and [BRD] draft an email about IPs.
- ACTION: [MPT] organise meeting about Guild Subdomains and drag [GPO] and others along for the future
- ACTION: [I2N] will add libcrack/haveibeenpwned API to `ucc-adduser`
- ACTION: [MPT] and [BRD] to email UWA IT about unfirewalling firewalled IPs, as they're not blocking anything useful, it's just inconvenient at this point.
- ACTION: After O-Day (April), do network shenanigans. (next wheel meeting)
- ACTION: [333] and [GPO] to read up on Ceph shenanigans and PVE in-place upgrade documentation.
### Boilerplate
- Now maintained in GitLab at [[<a class="moz-txt-link-freetext" href="https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/">https://gitlab.ucc.asn.au/UCC/tech-todo-list/-/issues/</a>]]
- 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
- Debian upgrade kills mailman
- Mailman is dead, long live mailman3
- We should look into upgrading to mailman3, and look at porting our homebrew patches for mailmail3.
- We shouldn't be using things that use python2 now that it is no longer supported either.
## Matters arising previously
## Extra items (rename/refile as appropriate)
*Meeting closed HH:MM*
----
```
# <a class="moz-txt-link-freetext" href="https://demo.hedgedoc.org/Hlsapf47RsqpgIjqLVfMUw">https://demo.hedgedoc.org/Hlsapf47RsqpgIjqLVfMUw</a>
cd /home/wheel/docs/meetings
HEDGEDOC_SERVER=<a class="moz-txt-link-freetext" href="https://demo.hedgedoc.org">https://demo.hedgedoc.org</a> /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: <a class="moz-txt-link-freetext" href="http://lists.ucc.asn.au/pipermail/tech">http://lists.ucc.asn.au/pipermail/tech</a>
Unsubscribe here: <a class="moz-txt-link-freetext" href="https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/tpg%40ucc.gu.uwa.edu.au">https://lists.ucc.gu.uwa.edu.au/mailman/options/tech/tpg%40ucc.gu.uwa.edu.au</a>
</pre>
</blockquote>
</body>
</html>