Today In Edinburgh: The Open Hardware Summit

Edinburgh has a lot of famous exports: stone castles, dramatic skies, and a national talent for making rain feel
personal. But on Friday, May 30, 2025, the city added another gem to the list:
the Open Hardware Summita two-day gathering where people happily argue about documentation,
share circuit boards like trading cards, and treat “open” as a verb, not just a vibe.

Hosted by the Open Source Hardware Association (OSHWA), the summit landed at
The Nucleus Building at the University of Edinburgh and brought together makers, researchers,
artists, engineers, educators, and the occasional person who can solder while making eye contact (a power I will
never understand). If you’ve ever wondered what open-source hardware looks like in 2025beyond “here’s my PCB, good
luck”this is your field report.

First, a quick reality check: what “open hardware” actually means

Open hardware isn’t just “I posted a photo of my prototype on social media.” In the OSHWA definition, it’s about
making the design publicly available so other people can study it, modify it, make it, and even sell
versions of itwithout having to reverse-engineer your intentions from a JPEG and a prayer. In practice, that means
sharing the design in formats people can actually edit (the “preferred format” idea), plus clear documentation and
licensing that doesn’t require a law degree or an exorcism.

And yesthis gets messy. Hardware has atoms, supply chains, safety, and the awkward truth that you can’t “git clone”
a bag of resistors. That’s exactly why a summit like this matters: it’s where openness stops being theoretical and
starts being operational.

Why Edinburgh was a perfect host city

The Summit’s venue, The Nucleus Building, is a shared learning and social hub on the University’s
King’s Buildings campustranslation: plenty of space for talks, tables, workshops, and the kind of hallway
conversations that start with “So I accidentally built a satellite…” and end with “Wait, can I see your repo?”

Edinburgh itself brings the right energy. It’s a city where old stone architecture and modern research culture
coexist without either one trying to win the argument. That’s basically the open-hardware mission statement: respect
the past, share the present, improve the futurepreferably with accessible documentation and fewer proprietary
screws.

What happened at the Open Hardware Summit

The 2025 program was structured like a well-designed dev board: talks on Friday, then a buffet of hands-on learning
(workshops), deeper debates (panels), and community show-and-tell (tables) through Saturday.

Day 1: Talks (Friday, May 30)

Friday’s talk lineup was a reminder that open hardware isn’t “just electronics.” It’s a set of practices that can
apply to knitting machines, conservation research, scientific instruments, assistive technology, satellites, and
even your favorite sensorif you treat openness as a responsibility, not a marketing adjective.

Highlights (and what they say about the movement):

• “All Yarns Are Beautiful” opened the door to a delightful truth: “hardware” includes machines
  that make textiles. Breathing new life into older knitting machines is both a technical achievement and an
  anti–e-waste philosophy you can wear.
• Conservation and environmental monitoring showed up in force, including the Mothbox Project,
  demonstrating how open designs can help researchers build tools that are affordable, adaptable, and replicable
  across different field sites.
• “Maintaining KiCad’s libraries” was a love letter to the unglamorous work that makes open
  ecosystems reliable. If you’ve ever screamed at a footprint at 2 a.m., you already understand why maintenance is a
  form of community care.
• Open hardware in production got real with a case study from Cynthion on building effective
  factory test systems. This is the “open” that survives contact with manufacturingwhere tolerances, test fixtures,
  and repeatability are everything.
• Accessibility and repairability weren’t side topicsthey were central. Talks like
  BrailleRap and reverse-engineering bike components to prevent e-waste emphasized a core theme:
  openness is not only about innovation; it’s about agency.

If you squint, you can see the bigger arc: open hardware is evolving from “cool project” to “durable practice.”
It’s not only about publishing designsit’s about making them usable by people who didn’t sit next to you when you
designed them.

Day 2: Tables, Workshops, and Panels (Saturday, May 31)

Saturday leaned into the social side of open hardware: hands-on workshops, structured panel discussions, and tables
where projects could be touched, tested, questioned, and lovingly nitpicked (the highest form of respect in maker
culture).

Tables: the “show me, don’t tell me” floor

The tables list reads like a playlist made by a very curious robot. You had everything from hacked knitting machine
communities to environmental monitoring stations, music interfaces, open weather satellite ground stations, and
projects exploring time, perception, and physical computing.

Examples that capture the range:

• Edinburgh’s hacked knitting machine scene (local energy, global relevance)
• Low cost environmental monitoring stations (open hardware doing fieldwork)
• Open-weather Automatic Satellite Ground Station (because of course that exists)
• Smart Citizen (monitoring “almost anything,” which is both empowering and mildly ominous)
• Solder Party (tiny boards, big personality)
• Taking Open Hardware and an Open Source Ethos Into Cycling (repair culture meets motion)

Tables are where open hardware becomes tangible. You can see the documentation strategy in real time: QR codes to
repos, printed build guides, labeled parts, and the kind of “ask me anything” conversations that instantly reveal
whether a project is truly openor merely open-ish.

Workshops: the hands-on proof that openness is a skill

Saturday’s workshops were wonderfully eclectic: affective touch design, hacking handmade ceramics with technology,
building an Opencyclone, DIY intimate and reproductive technologies, wave receivers, floating mist makers, even
open-source sigils (because sometimes your enclosure needs a little mysticism).

The common thread wasn’t a componentit was a method: teach people how to build, modify, and document a thing so it
can live beyond one person’s desk. That’s how open hardware scales: not just by sharing files, but by sharing
capability.

Panels: where the “hard problems” get a microphone

Panels covered areas where open hardware has outsized impact and extra responsibility:
Wearable Techniques, Open Source Environmental, Open Source Medical,
Rockets!, and Disability & OSHW.

These topics push openness past hobby territory. When hardware touches bodies, ecosystems, safety, or public
infrastructure, “open” becomes a serious design constraint. The panel format is perfect for this: it surfaces
tradeoffs, ethics, and the uncomfortable-but-necessary questionslike what “safe enough” means when the bill of
materials is one click away from a global audience.

The not-so-secret sauce: licensing, documentation, and the OSHWA certification signal

One reason the Open Hardware Summit stays relevant year after year is that it treats openness as a full stack.
Sharing designs is only the beginning. You also need:

• Editable design files (not just exported PDFs)
• Clear documentation (build steps, calibration notes, gotchas)
• A license that fits hardware (and doesn’t accidentally ban normal use)
• Trademarks handled responsibly (so clones don’t pretend to be originals)

OSHWA’s certification program is one of the movement’s most useful “trust signals.” The certification
mark combines the OSHW gear logo with a unique identifier (UID)a practical way for users to verify
that a project’s definition of “open source hardware” matches the community definition. It’s not a quality stamp
(“this will never break”), but it is a transparency stamp (“the design and terms are available the way open hardware
claims to be”).

Licensing is where many projects either mature… or quietly evaporate. Hardware-focused licenses like the
CERN Open Hardware Licence v2 exist in multiple flavors (permissive vs. reciprocal), and the choice
changes what downstream builders owe back to the community. The summit ecosystem is full of people who’ve seen
licensing done welland people who’ve been burned when it wasn’t.

Open hardware isn’t anti-business. It’s anti-secrets-as-a-service.

A persistent myth says open hardware can’t support sustainable companies. Reality is more nuanced:
open hardware often shifts where value lives. Instead of monetizing scarcity (“only we know how it works”),
teams monetize execution:

• Manufacturing quality and reliable supply chains
• Support, training, and education
• Services and customization
• Community-driven improvements that strengthen the product over time

Platforms and companies in the open-hardware orbit have refined this model for years. Crowdfunding and launch
ecosystems have also helped projects ship in public while still paying for tooling, compliance, and production
realities. The Summit’s programming reflects that maturity: you don’t just hear “open is good,” you hear how open
survives factory floors, documentation debt, and real customers.

If you’re building open hardware, here’s the strategic takeaway

The most successful open hardware projects behave like good maintainers:
they assume other humans will touch their work, misunderstand it, and improve it.
So they design for that reality.

Three practical moves that keep openness from collapsing

1. Document the “why,” not just the “what.”
   Schematics tell you what connects to what. They don’t explain why you chose that regulator, how you tuned that
   sensor, or which failure mode taught you humility.
2. Separate openness from branding.
   Share the design freely, but keep your trademarks clean. Users should be able to build derivatives without
   confusing them with your official product.
3. Plan for maintenance.
   Library upkeep, BOM updates, component substitutions, and build notes are not “extras.” They’re the difference
   between a living project and a museum exhibit.

A quick Edinburgh side quest (because you’re already there)

If you ever attend a future summit in Edinburgh, do yourself a favor: schedule a little time for the city itself.
Open hardware thrives on curiosity, and Edinburgh is basically curiosity with cobblestones.

• Morning: coffee strong enough to compile C++ in your bloodstream, then campus talks.
• Afternoon: tables and hallway chatsbring a tote bag; you’ll collect stickers and ideas.
• Evening: social events and dinner with people who will happily debate whether “open” is a spectrum
  or a binary (spoiler: it’s a spectrum, but everyone argues like it’s binary).

Bonus: of “being there” (the experience, not the brochure)

Picture this: you walk into The Nucleus Building and immediately realize you’re in the right place because the vibe
is half academic conference, half maker fair, and half “someone definitely forgot to sleep.” (Yes, that’s three
halves. It’s open hardwaremath is collaborative here.)

The first thing you notice is the soundscape. Not loudjust busy. A gentle hum of conversations punctuated by the
occasional laugh that means someone has just confessed to a spectacularly avoidable design mistake. Nearby, a table
demo is running on what looks like a breadboarded prototype held together by confidence. Someone else has a polished
device with a laser-cut enclosure and a QR code that takes you straight to editable files, a build guide, and a
license that doesn’t read like ancient prophecy.

You drift toward a cluster of people talking about documentation, whichsurprisinglyis not boring. It’s
passionate. A researcher explains how a tiny missing calibration step can waste weeks for a lab on the other
side of the world. An artist talks about making instructions feel welcoming rather than gatekeep-y. A maker admits
that their first “documentation” was a folder named “final_FINAL_v7,” and everyone nods like they’re in a support
group. (They are.)

The talks feel like a curated tour of the open-hardware universe. You’ll hear about conservation tools used in the
field, a hacked knitting machine that turns old tech into new textiles, and the kind of factory test system talk
that makes you realize “open” can absolutely coexist with serious manufacturing discipline. Between sessions, people
swap project links the way other conferences swap business cardsexcept here, the card is a repo, and the follow-up
is “file an issue if you spot something.”

Then you hit the tables. This is the candy aisle. You see environmental monitoring stations, music interfaces,
satellite-adjacent gear, and experimental objects that blur the line between instrument and artwork. The best part
is the conversational ritual: you ask “How open is it?” and the presenter doesn’t get defensivethey get excited.
They show you the editable files, the BOM, the version history, and the “known weirdness” section that proves
they’ve actually built it more than once.

By late afternoon, your brain is full in the best waylike you’ve binge-watched innovation, but it came with
footnotes and solder. You step outside into Edinburgh air that smells faintly like rain and history. You realize
the summit’s real output isn’t just projects. It’s a shared standard of care: build things, share them honestly,
and make it easier for the next person to learn faster than you did. You head to dinner with new friends, and the
conversation inevitably turns into “What are you building next?”which is the open-hardware version of “See you
tomorrow.”

Conclusion: what Edinburgh proved about open hardware

The Open Hardware Summit in Edinburgh showcased a movement that’s grown up. It’s still playfulfull of creativity,
weird prototypes, and joyful tinkeringbut it’s also serious about standards, ethics, and durability.
Open hardware in 2025 isn’t just about publishing designs. It’s about creating technology people can trust, adapt,
repair, and build uponwhether they’re in a university lab, a community workshop, or a kitchen-table makerspace.

If “open source hardware” is the promise, the Open Hardware Summit is the proof-of-work.