Everything Open 2026 – Day 3 – Morning

Open source can have friends everywhere by Emma Davidson

  • Large Business Benifit a lot from unpaid open source volenteers
  • But when they burn out unmaintained open source becomes a risk
  • 0.3% of the AUKUS Budget ($1b) would cover 15,000 Open Source software Internships
  • Lots of other stuff in talk but I didn’t really get good notes

Books-As-Code by Alec Clews

  • https://books-as-code.gitlab.io/
  • Main Book “Staying Safe Online” is targetted at Seniors so will be printed and sold in bookshops
  • Start writing your book. Don’t delay
  • Planning and High Level Design
    • Who are your readers?
    • What will you book teach them?
    • How are they going to buy your book?
  • The reader
    • Experience and background
    • Problems
    • How do they consume knowledge ( offline for older people, online for technical readers)
    • Where do they find your book
  • Plan the book content
    • List is ever evolving
    • Just a list of all the comment and topics
    • Ask AI to create a high level outline to get yourself starts rather than a blank page
    • Can use a mind-map to do outline
    • Elevator Pitch. Needed for traditional publisher. Useful for others
  • How Wlll you Write?
    • Capture notes and research
    • Formats to create
      • epub3 for ebooks
      • Prepress PDF for print
      • Display PDF for screen
      • HTML Online
    • Need a toolchain to create
  • Docs as Code
    • Lightweight Text Format – eg Markdown
    • Developer Style workflow
    • Automation
    • Simple Publication tools and platforms
    • This is not new. “The Unix Programming Environment” was done this way in 1984
  • What does Alex use
    • Asciidoctor – supports all the formats. Markdown is not enough
    • M4 pre-processor
    • sed, pandoc, ripgrep, sheel scripts
    • Gnu Make plus scripts
    • Graphics editors. Freeplane, GIMP
  • Writing Style
    • Follow best practices
    • Simple English. Use US English
    • Make content accessible. Alt text, good colours
  • Web vs Books
    • Web is non-linear. Books are not
    • Structure Book for easy-of-use and discovery
  • Create the Best Possible Book
    • You can’t see you own mistakes
  • QA Tools
    • Vale or TextLink style guide
    • Link Checks – lychee
    • epubcheck
    • Unit tests for code examples
    • Ai can review and suggest improvements in text. Gemini Write Extension
  • Human QA Resources
    • Beta Readers. Not all will do a good job. Social networks, local writers group
    • Find professional copy editor service. Will cost $$$
    • Get human editors to raise tickets
    • Update linter to spot previous problems
  • Publishing
    • Check the IP is all good
    • Copyright and License
    • ISBN
    • Legal Deposit
  • Traditional vs Self-publishing
    • Check exact what trad will do. Varies
    • Trans looks good on resume but might sell more
    • They will take more money, will own some rights
    • Never pay a trandional publish. Asking for money indicates a scam
  • Self Publishing
    • Responsibility for everything
    • You need all the skills
    • Keep more of the income
  • Typesetting
    • Consistent style
    • KDP is cheap for preview copies
  • Sales Tools
    • Need Book Description and Back Jacket Blurb. Hook Sentence, clear value proposition
    • Book Cover
      • Self-designed for free book
      • DesignDusk Premade for $200 odd
      • Bespoke is $700+. Consider ROI
    • Keywords and Categories. SEO
  • Kindle Direct Publish – KDP
    • Amazon’s Print on Demand
    • No Distribution to bookstores and libraries
    • Supports ebooks
    • No standard colour printing in Au Market
  • Print and Distribution
    • Looks at other books and genre and size sell for to decide price.
    • Looks at overheads and costs
    • See try.books.by and bookvault.app
    • Ingramspark as POD allows Retails Bookstores
  • Online Marketing and Newsletters
    • Better to create a Book Specific profile on Social media
    • Maybe create a seperate persona
    • Worth the work if you plan multiple books

So You’ve Decided to Build It Yourself by Leesa Ward

  • Definition for “from scratch”
    • WordPress Plugins
    • Anything from a small script to a full plugin or library
  • The Seven Sins
  • Envy
    • Want a feature yourself
    • Or you “assume” your clients really want a feature
    • Focus and what is important. Talk to the client. What is essential.
    • Build things as requested. Don’t spend time making something have options unless client asks for them. At least don’t too early
  • Lust
    • Allow buffer time to explore ideas
    • Or maybe create time outside the project
  • Greed
    • Maybe there are better uses for your time
    • Try create something bit-by-bit rather than a long term project that doesn’t deliver till the end
    • Develop common patterns and conventions
  • Gluttony
    • Sometimes you have to say no
    • Make sure reusable. Automate things. Create change logs and release numbers
  • Sloth
    • Just build the MVP
    • Shipping something that is messy but “just works”
    • Create automation and doc manual steps so you can sorta work with it next time you see it.
    • At least have a decent README file
    • Future is going to forget why you have done something this weird way and if you document it you’ll learn it again the hard way
  • Wrath
    • Frustrated Developers. Was harder than we expected. Other delays. AI gets stuck
    • Add buffer time. Get better at predicting timeline. Communicate well with clients. Don’t rely too much on AI
  • Pride
    • Assuming your way is the best way. Doesn’t document.
    • It’s not about the code it is about solving problems
    • Accept that sometimes things are the way it is. Work with what the company uses and knows
    • Don’t get stuck with sunk-cost if you have gone the wrong way
  • Takeaways
    • Be Proactive in communication
    • Document everything
    • First milestone should be an extensible MVP. Start small but build to grow and build to last
    • Treat all {non personal) projects as those other devs will be using and working on them
  • github.com/doubleedesign
Share

Everything Open 2026 – Day 2 – Afternoon

My degoogled life by Joshua Hesketh

  • Part personal journey, part reflection, part advice
  • Why?
    • Applies to any SaaS software where you are giving up data
    • If you are not paying for it you are the product
    • Different threat levels for different people
    • Privacy vs Secrecy
    • Situations can change. You share information now with a good company but their policy could change, they could have leaks or the law could change
  • Almost impossible to completely cut yourself off from Google
  • Tradeoffs
    • Self hosted software is often worse than the SaaS equivs
    • A lot more effort
    • SaaS services have full time staff looking after it, patching it etc
    • SaaS services are bigger targets than the personal setup
  • GraphereOS replacing Android
    • Ironically available mostly for Pixels
    • Many Apps worked via the website, just bookmark
    • Installed some Apps from Apps Store.
  • Youtube
    • Subscribe to channels via RSS
    • Watch in incognito and regularly close and reopen window
    • Few recommendations “Fantastic if you want to avoid doomscrooling”
  • Email Hosting
    • Have important stuff going to a SaaS provider email
    • Switched everything to a provider (fastmail)
Share

Everything Open 2026 – Day 2 – Morning

Peak Text: AI and the Golden Age of Libraries and Archives by Keir Winesmith

  • Finished “EGOT of GLAMs” with latest job
  • Mapping Brisbane
    • 1957 Tram network: based on older tracks, evolved into suburbs. River is fixed
    • Averaged with AI = River + Tramlines
  • Maps of Queensland
    • Merged many maps of Queensland with Model that knows birds.
  • NFSA (National Film and Sound Archive), Machine Learning and AI
    • Pilot to have AI transcribe etc material in the archive
    • Internal Transparency
  • Principals of NFSA AI project
    • Maintain Trust – Train only on stuff they have copyright
    • Build effectively and Transparently
    • Create Public Value
  • AI = Archival Intelligence
    • or maybe “Average Inputs”
  • Stereograms created by AI
    • Defaults to the small subset that is online
    • Previously was 1900 colonial pictures
    • Now still colonial but Google products a Sanfran street scene
  • The perfect Training Data is what archives have been putting out for years with lots of metadata
  • OpenAi Whisper trained on lots of youtube videos it turns mumbles into “Like and subscribe” and music fade outs turn into “Than you for watching”
  • The new golden age
    • Previous Golden Age was films explosion between the wars
    • 1980s and 1990s of Video games
  • Australian stories are no longer being made on celleloid and now being on social media
  • Thinks as boomers die off Facebook is dying off.
    • Other platforms my die in the next few years
    • New sites just algorithmically created content, not stuff shared by friends etc
  • What does NFSA do in response to how things change
  • Ability to search transcripts mean they can find people taking about something or someone, not just titles
  • Mass Transcript + Graph. References to cultural things like movies, quotes in unrelated documents.
  • Transcribed 18.7 years of content
  • Hope to open up more later in 2026
  • But don’t forget openness got us in this mess in the first place
    • Need to think before publishing stuff, since now it will be ingested by everyone

The Evolution of the OCI Artifact Revolution by Andrew Block

  • Modern Eras of Computing
  • What technologies came out of the cloud native era – Containers
  • The power of containers
    • Resource Management
    • Consistency
    • Speed
  • The Container format wars – docker vs rkt
    • Docker Ecosystem tied closely to Docker Inc
  • The Open Container Initiative
    • Image Spec, Runtime Spec, Distribution Spec
    • “Containers are just fancy files and fancy processes”
  • Image Manifest
    • Just a json file
    • Media Type header will come up later
  • Expanding beyond Container images
    • OCI can store Artifacts which are content types other than container images
    • Registry must explicitly support it (most of them do now)
  • New stuff you can store
    • Signature
    • Software packages ( .jar, rpm )
  • OCI Image and Distribution Spec 1.1
    • Released 2024
    • artifactType or mediaType
    • Can refer to other artifacts (ie signature for container) and API supports both directions to discover
  • Benefits of OCI Artifacts
    • Standard
    • Centralised Management
    • Reuse existing tools
    • Evolve existing practices
  • What Projects use it
    • Helm and Homebrew both use it.
    • Notary, Sigstore, etc use it to store signations etc of other Containers
    • Argo CD and Flux CD store manifests within OCI artifacts. Easier to give prod servers access to OCI registry rather than git repo
    • Kubernetes OCI Image Volume – Not exactly a OCI Artifact
  • Tooling
    • skopeo and crane let us inspect OCI metadata
    • ORAS – Create and manipulate OCI artifacts
    • The Evolution of the OCI Artifact Revolution by Andrew Block
  • AI
    • Currently uses git, hugging face, Object Storage to store stuff
    • Challenges. Several types of content, lack of standards ways to store and use
    • ModelPack is potential standard solution
    • Leverages stuff already in OCI
  • Demo with helm (using report software called “zot”)
    • Can push chart to oci: url
  • ORAS
    • ORAS can push a simple artifact . Even a simple plain text file

README: The Developer’s forgotten love letter by Swapnil Ogale

  • Technical Writer at AWS
  • “Customers will jump straight to the README, not to your comprehensive docs” – A Senior Developer
  • Story about how a powerful tool with no documentation doesn’t get any traction. A better documented tool that is less powerful gets more traction.
  • It is the first impression of your product. Sometimes the only impression
  • Anatomy of a good README
    • The Hook
    • Getting Started
    • Examples
    • Beyond the Basics
    • Building Trust
  • The Hook
    • Start with user’s pain point, not your technical achievement
    • Problem Solver not Technical Jargon
  • Getting Started
    • What do I install, what version, command that wroks, One good example, where to get help
  • Beyond the Basics
    • Full Docs, How to contribute
  • Building Trust
    • License information
    • Maybe Contributor list
  • Readme driven development
    • Design for users first
    • Think like a user
  • The User Journey
    • What is this?
    • Will it solve my problem?
    • Can I try it easily?
    • What if I get stuck?
  • The first 30 seconds
    • What makes them stay
    • Clear problem statement
    • Easy setup instructions
    • One problem example
  • What works for users?
    • Write like explaining to a friend
    • Use Screenshots and gifs when helpful
    • Break up walls of text
    • Test on fresh machine
    • update when things change
  • What frustrates users – anti-patterns
    • “It is easy, just”
    • Assuming I know the jargon
    • “See the source for details”
    • Installation steps that don’t work
    • No examples
  • Some Templates and Tools
  • AI Tools
    • Loses personality
    • Make sure it has examples
    • Has example AI prompt and wrapper script that we will share
  • Key Takeaways
    • Users are not lazy, they’re busy solving problems
    • “Obvious” is not obvious to them
    • Examples > Explanations
    • Test instructions ohttp://joinbookwyrm.com/n real users
    • README Maintenance is feature work
Share

Everything Open 2026 – Day 1 – Afternoon

The unreasonable cost of open source contribution by Rob Norris

  • Slides: https://despairlabs.com/presentations/open-source-cost/
  • Link to Chris Neugebauer’s Monktoberfest talk in 2024
  • The xkcd diagram is about projects and their funding. Not so much about the people and what they need
  • People talk about: Projects, Foundation, Company, Government, Charity or non profit, Grants
    • The above are not people
    • Who is the “Random person in Nebraska” and what are their wants and needs?
  • I can tell you about my story
    • 30 years of “non-mainstream” computing
    • 20+ years as sysadmin, programmer, etc
    • Overview of family situation. Partner and semi-adult children. 5 people total.
  • Monthly Expanses. All in $AU
    • Rent $2400/month
    • Groceries $2500
    • Utilities $850
    • 2x cars $3100
    • Heath: $2800
    • Total $12,000/month average in 2025
  • Income
    • $14,500 /month
    • Enough to cover month to month but not to to large items
    • $22k/month before Tax
  • This is a lot more than Patreon or similar will support for just about anyone.
  • Set up as a business
    • Set up a business
    • Invoicing
      • Local and International requirements
    • Tax of various types
    • Things a normal person doesn’t have to think about like Insurance, Office Space, Loans, Equipment
    • Contracts. Agreements, IP, Disputes
    • Charging for hours
  • Customers
    • Go off your profile/reputation
    • Grant applications, advertising?
    • Customer relationship management
  • What have we learned
    • Lot of software out there doing critical things
    • It needs to be maintained
    • We don’t value maintenance work
    • We have set up maintainers to fail.
  • “I’m not taking any questions, cause I don’t have any answers”

Roll for initiative: The battle against the beast of AI Slop by J Rosenbaum

  • How to recognise AI Images
    • Zoom in and look for details between elements, especially in the background
    • For video look at it frame by frame, doesn’t stuff jump around
    • Look at facts presented, google the name.
    • Look up the place or objects in it. Do they look like real versions?
  • AI Text
    • Hidden Unicode
    • Weird case, Bold, lists
    • Messed up facts.
    • Lack of an opinion
  • Music
    • Wobble in sustained notes
    • Safe, Homogeneous
  • Protecting yourself against AI slop
    • Duck Duck Go
    • Swearing and -Noai in google doesn’t work anymore
    • Don’t interact with it
    • Tell people who are sharing it
  • Running locally
  • Find Ethical tools. eg “Fairly Trained” , “Mitsua”
  • Protecting your Work
    • Tarpits
    • Glaze, Mist, protects your style from being trained
    • NSFW brushes
    • opt-out
  • People have been hired to tidy up Ai-generated content and make it look less sloppy.

Is it even worthwhile to self-host these days? by Steven Ellis

  • User Personas
    • FAF “Family Acceptance Factor”
      • Some of them have no technical skills
      • Some of them use phones, windows, android, etc
      • Some use facebook for phones, some use instgram
  • How: The Dream vs reality
    • Start with an old laptop maybe
    • Network is critical. Start Clean
  • Focus Technologies vs the nice to haves
  • Why?
    • Cost? – Often a fallacy
    • Security / Privacy – What do I want to share?
    • The Hoster can be compelled to turn data off by government?
    • Maybe beteer buying a service that we trust rather than trying to run ourselves
  • Domain
    • Don’t host your own domain
    • Don’t buy too many domains
    • Small biz should own their own domain
    • Big companies should own all the domains and variations
  • Email
    • Use your domain
    • Have a backup for things like the email bill
    • Self host – Stalwart , Docker Mailserver / Mailcow
  • Family Mail / Small Business
    • Do they need all the features?
    • But need to support multiple devices
    • Hard to scale small to very large business
    • Doesn’t you family need exchange features?
  • Photos
    • Lots of self-hosting options
    • Immich, Photoprism, Pcgallery, Powigo, NextCloud
    • Default Providers
    • Hosting Service
    • Gallery/ Sharing
    • Backups
    • Google One Account
      • Which has local NAS backup
      • and more backups
    • Sync out of Google is getting harder
  • Media
    • 1000s of DVDS, Critical Documents
    • Family videos
    • Accessing the Media
    • Stephen’s approach
      • TrueNas
      • unraid, proxmox, openmedia vault
      • containers for most services
      • Regular offsite backups
  • Iot
    • Matter seems to be the platform of the future
    • Use the Tuya App
    • Alternative Firmwares – ESPHome,
    • IOT vlan so can’t see home network
  • AI
    • Sucks down Power and high spec HW. $$$
    • Self Host home automation, private voice service
    • Can work with older GPUs . Integrated GPU in chips can do enough
  • Self hosting Journey
    • Almost everything in containers
    • Efficient Power supply unit is worth it.
    • Fresh tomato – Firewall on Netgear R7000
    • GigE is probably fast enough
  • Take Aways
    • Not everything scales up or down
    • Automate everything
    • FAF is critical
      • Can your partner / kids / parents use it?
      • Appliance / Containers are very effective
    • Backup everything, regularly
    • Do you want to Provide 24×7 support for the whole family
  • Make sure you document everything?
    • Have an offline copy
  • Hardware redundancy?
    • None but bought better hardware
    • Backups and procedure to recover quickly
  • Network over Power
    • Can sometimes work but try all other options first
Share

Everything Open 2026 – Day 1 – Morning

Breaking to Build: What Security Teaches Us About Openness by Kylie McDevitt

  • Works in Security. Founder of company called Infosec
  • Vulnerability research, Linux devices, Organising various Security events and Confs
  • Why Breaking things matter
    • You can only improve what you can say, security and openness both rely on clarity
  • IoT Code of Practice – 13 Principles, released 2020
  • Code of Practice Project
    • Test approx 50 consumer IoT devices
    • Goal: Practical evidence-based vendor advice
    • Focus common patterns, not single vendor
    • Cameras, doorbells, tops, smart speakers, home automation devices
  • Testing Methodology
    • DUT = Device under test
    • Dynamic analysis of DUT. How it boots, what it seems to do, contact, etc
    • Firmware acquisition
    • Dynamic and static analysis of Firmware
    • Triage results, Look for interesting results to follow further
    • Create exploit to “prove harm”
  • Dynamic Analysis
    • Look at network traffic. websites it connects to. s3 buckets
    • Port scans (may change at different stages)
    • Obtain console access
    • http MITM if poss
  • Firmware acquisition
    • Meta: Had some computer problems here. Unable to record notes
  • Assumptions that break everything
    • Trusted Firmware Sources
    • Local-Only Interfaces
    • One-way trust relationships
    • Hidden features never removed from production
  • What Breaking Teaches Us
    • Patterns show where to focus
    • Fragile assumptions are the real threat
    • Feedback loops make Systems Stronger
      • Clear, constructive guidance for vendors
  • Openness
    • Sharing, Reproducible results, Community standards, Public Education – all feed off each other
    • Intersect Government, Community and Industry
  • Looking Forward
    • Systems are getting more complex going forward
    • More attack surfaces
    • More reliance on shared codebases ( frameworks, open source, vendor common code )
    • Great need for open collaborative defence
  • How we keep improving
    • Keep breaking things – systematically and legally
    • Keep sharing what we have learned
    • Keep building community capacity
    • Keep helping each other succeed
  • “Breaking is the first Step, Understanding is the second, Sharing is what makes the ecosystem stronger”

Encouraging democratic participation with software by Vanessa Teague

  • Slides downloadable
  • Democracy Developers – https://www.democracydevelopers.org.au/
    • Build software that supports democracy
    • Australian based but works worldwide
  • What projects can we do we’d be proud of?
    • Get people of social media and engaging more effectively
    • Inoculate people against misinformation
    • A politician asks a question prompted by a user of our software
  • Projects they have tried
  • Ask Parliament
    • List of questions for MPs or that MPs could ask at committees
    • People could up-vote or down-vote. Show which questions were popular (and media etc could pick up)
    • Never really took off. On the backburner
  • Age Verification Feedback Form that messaged Politicians
    • https://ageofreason.democracydevelopers.org.au/
    • Whole bill was rushed so not really time for it to get live
    • Working to expand it more generally
    • Has a better system to find representatives based on address compared to official site
    • Q: Is this too late in the process to influence actual changes?
  • Explain That Election
    • Note quite live
  • Where did my STV vote go?
    • https://vote.andrewconway.org/
    • Data only available in some areas/elections
    • You put in a sample vote ordering and you can see how that vote was shuffled in that election though the various rounds.

Neighbourhood-First Software: How we roll-out the open web without expecting everyone to self-host by Jade Ambrose

Share

Everything Open 2025

In January 2025 I attended the Everything Open 2025 Conference in Adelaide. The conference was held over 3 days and is the main conference of Linux Australia and is the successor conference to Linux.conf.au (LCA) which I had been attending since 2004. The conference is community run and full price tickets are $AU 850 with Hobbyist tickets half that.

2025 was the 3rd Everything Open (EO) to be held and around 300 people attended. The Conference opened each day with a keynote and then split into 3 streams of talks plus a tutorial stream. Talks range fairly widely, the official blurb is a “conference focused on open technologies, including Linux, open source software, open hardware and open data, and the communities that surround them

The venue was the Adelaide Convention Centre which had plenty of room and was nice enough. They main train lines for Adelaide ran under it with around 8 tracks under the venue. There were good food options a few minutes walk away since the venue is close to the Adelaide CBD.

Accommodation was fairly good. I got a hotel for $150/night about 10 minutes walk away that was near restaurants etc.

Content and attending

I really enjoyed the keynotes this year. All three speakers were interesting and and had great delivery. I also felt there talks were all good and there are several I missed that I’d like to catch-up if/when the videos are out.

I publish my (rough) notes from talks I attend to this blog. A list of here

Unfortunately I’m still masking (as were about 5% of attendees) so I probably didn’t participate in the Hallway track as much I would in the past. It was also fairly small due to relatively small numbers at the conference (see below)

The only organised evening event was the Penguin dinner at the Zoo. Unfortunately we didn’t get to see animals, just the food venue (drinks and chat followed by dinner)

Thoughts on the conference Format and Future

While EO attracted around 300 people which was almost double last year (held in the fairly remote city of Gladstone) but still less than what half a typical LCA attracted before Covid.

Unfortunately EO is still a step down from LCA. There were very few attendees from outside Australia and New Zealand. Part of this is due to disruption of conference going during COVID and part due to the general economic conditions but I think there were some other factors

At LCA Miniconfs were a good way to attract people and provide targeted content. People would come for the Kernel, GLAM or Sysadmin Miniconf (disclaimer I helped run the latter) and stay for the rest of the conference. They could tell their boss they were going to the “Work-related Miniconf” at LCA and staying for the rest.

The lack of Miniconfs also meant the conference was less nimble. While several talks were about LLMs and AI, in the past a LCA would probably have had 1-2 days of Miniconfs devoted to this hot topic (perhaps one day technical for users and a 2nd day for users and policy). Eg in 2020 there was a Kubernetes orientated Miniconf.

The conference being only 3 days and 3+1 streams rather than 3 days of 5+1 (plus 2 days of Miniconfs) seen at later LCAs also means people get less for their buck. Especially since travel will make up a significant cost for many attendees.

The inclusive EO brand also trying to reach out to a broader group means that the conference is less attractive to a technical user. The Irony is of course that LCA was a nominally technical conference with a lot of non-technical content while EO is a branded as a broad conference that is still probably 75% technical talks.

I’ll probably come back next year if the event is held. However the event had yet to be arranged due to lack of a bid. However a group was formed after the this year’s conference and it is likely that an event will happen in Canberra in 2026.

The Linux Australia AGM covered several problems with the conference (see The Linux Australia 2025 AGM video ) including difficulty finding people to run it, problems finding sponsors and the format. Questions were asked about bringing Miniconfs and problems with them were highlighted.

Overall it is difficult to tell where things are going. The conference is fairly successful but struggling to be sustainable. Personally I am not sure on the best path. Perhaps splitting the conference into two could work. Something like 2 days of Linux.conf.au, one day of Miniconfs and then 2 days of EO. But anything would required people to volunteer to help which is difficult right now.

Share

Everything Open 2025 – Day 3 – Afternoon

tips to build and repair empathy with other teams by Cait Macleod

  • Consultant so often works with different teams
  • Tips
  • Signs
    • New to a Team and you notice weirdness
    • Feeling stressed or frustrated
  • Observe
    • Team contexts (eg ops vs dev)
    • Common pain points.
    • Misunderstandings
      • Defensiveness – maybe something else is going on
    • self-awareness
  • Influence
    • Working relationships with individuals
    • Giving Feedback – situation + behavior + impact
    • Challenge or Correct behavour
    • Restructure Interactions
    • Structural Change

I come to bury Ansible, not to praise it! by Daryl Tester

  • Ansible
    • A set of tools doing Infrastructure as Code
    • Runs a Domain Specific Language
    • Agentless
    • Idempotent
    • Inventories, Playbooks, facts, state based
  • Whats my beef with Ansible
    • Small Peeves
      • Transit python agent rather than true agentless
      • Lots of ssh sessions
    • Larger Peeves
      • Cognitive Overload with edge cases with launguage
      • YAML is difficult to work with. Lots of problems
      • Complexity of Variable precidence
      • Also – Global vars everywhere, lack of complex data structures, nested looping, blocks
  • Can we do better?
    • Found I was sometimes bypassing Ansible to work with the direct python. But hard for others to understand
  • Pyinfra
    • Inventories and deploys in python
    • Facts are loaded on demand
    • Requires a posix-ish shell at the other end
    • connectors are how we talk to a managed node ( ssh most common )
    • can run facts/operations from the command line
    • facts/operations are easily written/extended
  • Mode of Operation
    • “run” the inventory – single remote command ssh session
    • connects to hosts
  • On person project
    • Some others patching
    • Version 3 recently out
  • Demo

Lightning Talks

  • OER Collective
    • oercollective.caul.edu.au
    • Space to public Open Textbooks
    • Community, Grants, Professional development
    • Over 50 Open Books published. Creative Commons Licensed, Various formats besides just text
    • Have a talk to your librarian to find if OER Collective is the thing for you
  • Disabled Data Sovereignty
    • Just say “disabled” . Word is okay
    • Against “Data Harms”
    • Disability-justice Informed
    • Ability is a temporary privilege
  • Run a Conference
    • A brief history of the conference.
    • Wasn’t called Linux.conf.au at the start
    • Lots of changes. It evolves
    • Please run a conference, start small
  • tax-ato
    • Update since announced in 2023
    • A personal income tax library in Haskell for Australians
    • Lots of updated features
    • Bugs, feature requests and patches welcome
  • Quirkey Keyboard update
    • Hard to update everybody because they are all use different social media spaces
    • Use blogs, email cause searchable and open to everyone
  • Our purpose and make sure thats what the system does
  • OS solutions to protect daughter’s online browsing habits
    • Education
    • Content Filtering
    • Discussion and Verification
    • Only 7 so higher level of watching than older kids
    • Pi-hole filtering
    • Browser History
    • Browser policies
    • App pulls browsing history and sends to discourd every 5 minutes. Prometheus Metrics
  • How to Program Human Beings
    • I am course talking about Scottish Country Dancing
  • QMK Keyboard
    • Lots of magical macros
  • ipv6
    • No NAT, No DNAT
  • Quadlet – Running containers via systemd
    • included with podman
    • Does all sorts of cool stuff
    • Looks just like another systemd service
  • Blue Hackers
    • In recent years added neuro-diversity – ASD, ADHD, Bipolar 1 and II, etc
    • Also plugging Sunshine Coast Security Conference in mid-2025
  • A quick reminder about Gender
    • Not the same as Sex
    • Could mean several things
    • Lots of non-traditional genders
    • Can change
    • The GenderBread Person – www.genderbread.org
    • Lots of things only sorta connected
    • Gender question should be a text field

Conference Close

  • Thanks everybody
  • If you are keen to run your own conference ( eg EO 2026) contact the council
  • Pycon Au 2025 coming later this year
  • DrupalSouth Melbourne in March 2025
  • Kiwipycon in November 2025
  • DDD Melboune 2025 – 22 Feb – Dev conference
Share

Everything Open 2025 – Day 3 – Morning

You’ve been laid off. Now what? by Mike Jang

  • Author is older
    • Doesn’t advertise age
    • Limits Linkedin to more recent jobs
    • Sees reaction when potential employers see his age
  • Empathy for the Hiring Company
    • What do they want, what are they looking for?
  • 11 Steps after a layoff
    • Negotiate your layoff – eg in US extended medical insurance. From a different budget. The laptop
    • Applying for Unemployment
    • Regain Focus – Accept the job is going and focus on next step
      • Get over your anger. It shows up in Interviews
    • Setup a git repo with resume, stuff you are proud, samples, other professional stuff
      • Clone and customize repo per job potentially
      • Maybe a professional website
      • The git profile is not enough
      • Show you domain expertise – k8s, cicd – say what you have actually done
    • Don’t just ask for help
      • “Reaching out to my network”
      • Be credible – don’t say you “love the company that laid you off”
      • Add a headline with what your expertise do
      • Describe expertise and create posts about them
      • A good linkedin recommendations especially from company that laid you off is good
      • Craft recommendation for others to sign. Offer to write in return
      • Followup posts
      • Elevator pitch. Remind you contacts (cause contacts might only vaguely remember you)
      • Empathy for your contacts, they want to know what to say
      • Laid off groups: common ground
      • Chat groups. Slack, discord. Maybe don’t include those still with your ex-employer. Alumni groups ( job posts, referrals )
      • Social Media – Shares Solutions, Endorse others. Don’t abuse companies or people/groups.
    • Finding a Hiring Manger
      • Target a company. Check see any contacts on Linkedin that work there or 2nd level contacts that do.
    • Customize the Application
      • Match the job description
      • Customize your resume
      • Include a cover letter
      • 4-8 hours / company
      • If the company does open source then contribute to their OS
      • Don’t – No Generic Resumes
      • Link to portfilio and domain knowledge
    • Share your schedule
      • Set up a calendar (you can share a calendar, but block off some time for other other stuff and to show you are busy)
    • Show what you can do – When you should do extra
    • Prepare for the interview
      • Review all your stuff from above
      • Your stories, your portfilio
      • A closing statement, like an elevator pitch with stuff from the interview. Makes it easy for interviewer to prepare their report
      • Followup and thank
      • Help the Interviewer remember you. Followup and remind something postive from interview. But don’t nag after that
    • Negotiate an offer
  • Non-Traditional Searches
    • Specialty Groups – OWASP, Y-Combinator
  • Remember the Empathy
    • They want to solve problems. Show them you can solve those problems.
    • Like your elevator pitch.

Modularisation of Open-Hardware to Tackle the Digital Winter by Paul Gardner-Stephen

  • Mega65 Project
  • nlnet Foundation – Funded from the EU and in turn fund Open Source projects
  • Digital Winter
    • What happens when our ability to build open hardware systems is broken?
    • Supply Chain Disruption
    • Regulatory Capture
      • Especially in Radio frequency space
    • Conflict or social unrest
    • Technology Passes Complexity Event Horizon
      • Already at there for chips
        • Protocol complexity for something like a web-browser
  • If we want to make systems that can survive a digital winter
    • Needs to be simple enough to implement the software
    • Hardware needs to be at least simple enough to salvage parts for bad units
  • Software
    • Simply enough to maintain and have a smaller attack surface
    • But enough complexity to be useful
    • Cut out dependencies
    • Cut out complexity and uneeded feature
    • Graceful degradation if offline or with lower resources
    • If device is small enough ( eg 64 MB of RAM) there is less room for the malware to hide
    • Browser in 32KB ( could be smaller if was in assembler )
  • Previous Board was big
    • Took long time to iterate a new design. Lots to redo each cycle
  • Module System Design Criteria
    • Large PAD size
    • Unambiguous orientation and placement
    • No sharp protrusions so easy to stack boards togeather
    • Relatively small
  • Decisions
    • Half-round castellated Pins
    • Easy to attache and unattached boards from each other as you soldier.
    • Can add glitter to attached modules so tamper obvious
  • Next
    • Design and fabricate various modules
    • Assemble and test
    • Design and fabricate simple case
  • What you can do for your projects
    • Offline functionality
    • Segregate your subsystems
    • Energy and Comms sovereignty
    • Simple 80% alternatives / fall-back modes
    • Fell free to help with our project.
Share

Everything Open 2025 – Day 2 – Afternoon

I skipped a couple of talks to do Hallway track and other stuff

Koha – not your average library system by Aleisha Amohia

  • Name because software was made open source as a gift to the community
  • Started in 1999
  • First fully web-based opensource library system
  • Bugs and external patches soon after
  • Customizable and Configurable
  • Used in 18,000+ libraries
  • It is just a big database
    • Can be used as not just a library system
    • Can be used to catalog other stuff at organisations other than libraries like documents
  • Configurable via CSS, fonts, languages, CMS, feature toggles, etc
  • Customisable views for each branch are possible
  • Special Beyond the code
    • Offline circulation
    • Supports non-ascii characters
    • Translation capability
  • Is it harder to find people to work on stuff since it is writter in perl which is effectively a legacy language? – Has a good onboarding and support for devs and things still work
  • What are challengers with it being open source? –
    • People worry about quality of OSS. Fix: Good robust quality procedures
    • Think it is free – Have good support that is worth paying for
    • DB backend – MySQL and MariaDB

The circle of life: The Digital Skills GitBook project by Sara King

  • Working on project for last 5 years that is in the process of winding up
  • tinyurl.com/5539zzpx <- more information
  • Starting early 2019
  • 5 years later project is coming to the end of a natural cycle
  • Context
    • Group of 60 libraries looking for projects – CAUL Digital Librarians
    • Is there a book that teaches modern not-quite-technical computer skills?
  • With Pandemic lockdowns everybody started working from home
  • Why Gitbook?
    • “Book” is in the term helped
    • Similar project using github etc
    • CAUL eventually went Pressbooks, but not till later
    • Also qualified for free version
    • Learning git was a useful thing
  • Did the community really need this? – Wasn’t checked in detail, but seemed a cool idea
  • Happened at start of pandemic
    • Everyone online
    • Supportive community was good at start of pandemic
  • Took some courses in git and other tools
  • Did a prototype book on another subject to get the hang of the tech
  • “Gave ourselves permission to not know what we were doing”
  • Created chapters of the books to give outline
    • Each Chapter had 3 levels of knowledge in it. Novice, proficient, advanced
  • Went public in late-2021
  • Also did code of conduct, license, contributions guidelines
  • Told people about it via various methods
  • Worked to get people to contribute ad-hoc
  • But didn’t get the amount of contributions they were expecting
  • In 2023 University libraries having problems, budgets shrinking etc
    • People leaving or too busy
    • Some used experience on the project to get new more technical jobs
  • No new people joining to replace those leaving
  • 2025 reflecting on the project
  • Process and product are different
  • We equated enthusiastic about the idea and the process. But didn’t join in or wasn’t super into the product
  • Not shared a lot or got many hits
  • Goal of training people to create stuff was a big success
  • People gained lots of confidence with new tech
  • Support of CAUL was great, but no longer availbale
  • Next? – If people like the process maybe we should talk about that
  • Create a roadmap for other projects
  • Hand it over to somebody else? Doesn’t seem to be interest
Share

Everything Open 2025 – Day 2 – Morning

Skill Trees: Gamifying The Hard Things by Steph Piper

  • A list of skills
  • Each area has a series of skills that can be colored in.
  • Design
    • Hexagons are good
    • Can be done in any order, hard to connect meaningfully
    • Simple, flexable milestones
  • Reception
    • First on was 3d printing & modeling
    • Tested on makerspace student staff members. Good to identify gaps
  • Benefits
    • Reduce imposter syndrome or on the other size overconfidence
    • Target areas for improvement
  • Online on git – https://github.com/sjpiper145/MakerSkillTree
  • How to make a skill tree
    • Flexibility, not too cost restrictive, globally applicable
    • Peer reviewed
    • Final skill tree and translation
  • Book – The Learning Game by Ana Lorena Fabrega
  • Beta testing book of a collection of these skills.
    • Good published through “Make: Magazine”
    • 68 tiles per tree, 1020 skill tiles in the book
  • Tips for writing
    • Continue to evolve and improve
    • Do own illustrations was huge time saver from the publisher
    • Confidence in your work. The publisher will only do the final publishing
  • Looking to fill the gaps
  • Working on a kids version of the book

The Token Wars: Why not everything should be open by Kathy Reid

  • The Token Wars
    • A resource conflict fought through technical, social and legal means
  • What is a token?
    • An atomic unit of text taken from a larger collection called a corpus
    • text -> subwords tokens -> vectorization
    • Transformer architecture
    • Word embeddings capture semantic closeness of words
  • Scaling up to billions of tokens
    • Train the relationships between tokens based on all the text
  • The value of tokens and token economics and the actors in the token wars
    • Are the a public good?
    • No the are rivalrous either excludable or non-excludable
    • LLMs in 2024 were trained on 4 orders of magnitude data than 5 years ago.
    • Estimated 60-160 trillion tokens on the public web and some LLMs are trained on close to all of those
    • Synthetic Data especially low quality slop is polluting the Internet
    • Scrapers pick this up and train on it, concern about Model Collapse ( like a photocopy of a photocopy). Reduces the diversity of what it will produce.
  • Key actors in the token wars
  • Individual content creators
    • Included in corpus without permission
  • Platforms with user-generated content
    • Seeking to get paid for their content ( eg Reddit deal with OpenAI )
  • Archival Institutions
    • Australian National Film and Sound Archive: Maintain Trust, Transparancy, Create Public Value
  • Private Companies
    • Anthropic: Model Context Protocol
  • The AI Companies
    • Have used fair-use. Although some countries don’t have those
    • Companies blocking the common crawl
  • Governments
    • Having trouble balancing interests
  • Token Tactics – Protecting your token treasure
    • Data poisoning
    • Blocking bots and scrapers
  • Data Sovereignty
  • Futures
    • Hunt for more tokens
    • Better ways to block/prevent
    • Better understanding of the alateral damage of the resource conflicts
Share