Today, most people understand the concept of Open Source – certainly we expect most readers of this blog to understand it. View the code, use the code, copy the code, change the code, and, depending on the license, contribute back changes or not.
What many people don’t get, and something we here at Hyperledger and The Linux Foundation pride ourselves on doing well, is Open Governance.
The Linux Foundation, and all of our 75+ open source projects, are not-for-profits building the greatest shared R&D investment in history. Open Governance is central to this promise.
What is Open Governance?
Open Governance means that technical decisions – which features to add, how to add them and when, among others – for a given Open Source project or projects are made by a group of community-elected developers drawn from a pool of active participants. It is as close to the ideal of pure technical meritocracy as one can get and we strive continuously to reach that ideal.
Hyperledger recently concluded its 2017-2018 Technical Steering Committee (TSC) election, and so we thought it an opportune time to explain the ABCs of Open Governance. Please note that this is one Open Governance implementation and clearly not the only way to do it, but rather one proven and effective way.
Read more about how Hyperledger approaches governance at the Hyperledger blog.