This is an old revision of the document!
Committee Meeting Minutes: 14 September 2026
Attendees
- Maggie (Zoom)
- Wade
- Simon
- Jade
- Sarah
Agenda
- Memberships process:
- How to add ppl to Matrix: Jade needs to write this down
- Everything Open Talks
- AI Policy
- LoRes UX: Design Directions and student involvement
- Partnership opportunities
- Taiga board review: AGM, bank account
- Solarpunk meetups
Meeting Notes
Everything Open Talks
- Jade will propose a tutorial: install LoRes stack on your laptop
- Sarah will propose a talk on how we do
Memberships process
- How to add ppl to Matrix: Jade needs to write this down
- Jade to add Rob to bank account, and send statements
Meetups
- Oct Maker Community
- Nov Melbourne Connect
LoRes Update and Partnerships
- Coburg Studios may be a space to explore: now fully battery powered (though not offgrid)
- 8 ppl have successfully set up their nodes; Kiwix app install is now a separate subsequent step. Some folks need to update. Maintenance section in the doc now started. Some QoL improvements are needed e.g. to see what version. Nodes are on
- Now we have one other contributor! Greg: a meaty PR.
- Priority: starting to unlock other contributors to the project.
- Multi-node Wikipedia is just a Proof of Concept
- People are knocking on our door asking for the services we are offering. Neighbourhood centres. Food Sovereignty Alliance. Feral Computing.
- DashChat is being realigned to be local first. But note it's not open / foundation held but the technical approach is interesting.
Design Directions
- Co-design opportunities around the LoRes Tech;
- Students and design professional to build a brief;
- Incorporate input from First Nations people;
- New design approaches needed to communicate the status of the node and network;
- A key idea: computing is now embedded in place. Re-geographising computers.
- Peopling computing:
- To what extent should we make the tech-based interactions human? Should people see the name and face of the person who's providing tech or will that lead to finger pointing?
- We can't fully throw a question like this over to designers: There are security implications which impact on risk, accessibility, compliance. Frameworks that we can work through e.g. Cade offers the ANXIETY framework.
- Security model?
- Auditable and transparency rather than control
- Wade: “embarrassingly transparent”