It’s not the license we choose, it’s the communities we build

It’s not the license we choose, it’s the communities we build. In open source hardware and software circles a lot of time is devoted to figuring out the best license. For license enthusiasts this is a passionate topic with unlimited debate on mailing lists, for folks shipping open-source hardware, the majority of shipping Open-source hardware still uses Creative Commons-Share-Alike-Attribution to display their intent. Maybe that will change one day as new licenses are written.

We think what really matters in the community we all build, the support we offer to our customers and the code we publish. Our guess is that most of the issues with open-source hardware will not be solved in court or with lawsuits. Creating and celebrating a community of people & companies sharing hardware for the benefit of each other is where the real action is at. Putting a strongly worded text file on a download page makes intentions clear (always a good idea) but in the end – it’s the community of people we’re part of that will be the most benefit when things go incredibly good, or the rare times when someone just wants to be a jerk.

Make a robot friend with Adafruit’s CRICKIT – A Creative Robotics & Interactive Construction Kit. It’s an add-on to our popular Circuit Playground Express, FEATHER and other platforms to make and program robots with CircuitPython, MakeCode, and Arduino. Start controlling motors, servos, solenoids. You also get signal pins, capacitive touch sensors, a NeoPixel driver and amplified speaker output. It complements & extends your boards so you can still use all the goodies on the microcontroller, now you have a robotics playground as well.

Join 7,500+ makers on Adafruit’s Discord channels and be part of the community! http://adafru.it/discord

CircuitPython in 2018 – Python on Microcontrollers is here!

Have an amazing project to share? Join the SHOW-AND-TELL every Wednesday night at 7:30pm ET on Google+ Hangouts.

Join us every Wednesday night at 8pm ET for Ask an Engineer!

Follow Adafruit on Instagram for top secret new products, behinds the scenes and more https://www.instagram.com/adafruit/

Maker Business — Fewer startups, and other collateral damage from the 2018 tariffs

Wearables — Battery wash cycle

Electronics — How to make your own magnetic field probe!

Biohacking — The State of DNA Analysis in Three Mindmaps

Python for Microcontrollers — One year of CircuitPython weeklies!

Get the only spam-free daily newsletter about wearables, running a "maker business", electronic tips and more! Subscribe at AdafruitDaily.com !


  1. Right on. I want to make open hardware to help make more and better open source. I’m a hardware geek, not a license geek, I really don’t care about the license. I’ve taken to releasing most hardware public domain now because it’s the least amount of fuss for reuse. Firmware that is for tutorials is always public domain too, but sometimes complicated firmware (often the real work) is CC BY-SA simply so I don’t need a written public domain release from firmware contributors.

  2. Yep. I’ve been saying that for a while. My “Open source license” is a proxy for “These are the people I hang out with.”

    Oh, and for us EEs, reading the resistor would be a LOT easier if we could just type 150 10% (for the resistor below). I don’t even think about them as numbers anymore. It’s just a 150 ohm resistor, not a 1 5 X 10E1 resistor.

Sorry, the comment form is closed at this time.