Leadership

Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the GVCS, which assumes participation in a collaborative process. Commits must follow OSE Specifications, the OSE Vision, and OSE Roadmap. People are free to contribute to the wiki. Projects may be merged into the main trunk of OSE. Usually, for every product, there is a main trunk and other versions, as determined by the technical leadership. In the voluntary project of OSE, leadership is essentially self-selecting. Technical leads can be made official by the BDFL, otherwise people are welcome to contribute informally and without any permission from the rest of the community. Good work rises to the top - which can be manifested by economic viability and the creation of right livelihood from know-how generated on the OSE wiki.

In open source hardware, structure is more fractal than in open source software projects. Thus, governance should in principle be easier at OSE - as the entire economy is open for open-sourcing. This takes many people, and we welcome leaders rising across all product, service, and enterprise categories.