The solution
In the mid-2000s robotics research was a patchwork: a gifted software developer might lack hardware knowledge, a path-planning expert might not know vision, and every lab rebuilt drivers and navigation from scratch. Stanford PhD students Eric Berger and Keenan Wyrobek set out to build a baseline system academia could share — 'something that didn't suck' in all of those dimensions. Investors kept calling the 'Linux of Robotics' too ambitious, but Scott Hassan, an early Google architect who had built eGroups on open source, funded exactly that vision at Willow Garage.
Willow Garage's tactics read like a playbook for seeding a standard. It invited the leaders of about a dozen open-source robotics frameworks to a two-day workshop with a genuine promise: we will hire engineers to build your dream infrastructure — tell us what to start from. The group agreed a fresh codebase with clean licensing was essential, and the attendees left personally invested. The PR2 Beta Program then awarded free robots to eleven institutions — Stanford, MIT, Berkeley, Bosch, KU Leuven, Tokyo and more — on one condition: the recipient open-sourced its robotics work.
ROS 1.0 shipped in January 2010 and the PR2 went on sale that September, but by then the ecosystem ran itself: outside groups had contributed from the start, an internship program spread the know-how, and within two years Rethink's Baxter became the first commercial robot on ROS. Willow Garage itself was absorbed in 2013, having already handed ROS to the Open Source Robotics Foundation it created in 2012.
What it achieved
Give away the robots and the code, set the standard
Why it worked
Robotics software had no shared infrastructure, so every hour of research duplicated plumbing instead of advancing the field — the pain was universal and the willingness to share was high.
Clean licensing was treated as a first-class design goal, removing the copyright ambiguity that had stalled earlier open-source robotics efforts.
Free flagship robots bought real commitments: institutions that would never have standardized on one vendor's stack happily standardized on hardware they got for free with code they could keep.
Enlisting rival framework leaders as co-designers converted potential competitors into invested evangelists before launch.
What can be applied
When shared infrastructure can't be built for profit, fund it once and give it away. One string — what you build belongs to everyone — turned a whole research field into the standard's co-authors.
Aftermath
The Open Source Robotics Foundation took over ROS maintenance in 2013 and has released a new version every year since; ROS 2 arrived in 2017 to carry the standard into real-time and industrial use through ROS-Industrial consortiums in the Americas, Europe and Asia-Pacific. NASA's Robonaut 2 ran ROS on the International Space Station in 2014, and in 2018 Microsoft ported ROS to Windows while Amazon launched RoboMaker on AWS. What began as one startup's giveaway is now the default software platform of the robotics industry it set out to create.
FOLLOW THE EVIDENCE
The sources
- The Origin Story of ROS, the Linux of Robotics spectrum.ieee.org
- PR2 — ROBOTS: Your Guide to the World of Robotics robotsguide.com