OSE Governance

Organization

edit

Index Guide 2012 Rollout Plan | Mission Needs Funding Structure Strategy Governance | Media Marketing | Development Documentation Archive

GVCS Tools | Tasks Resource Map Network | Meetings | International Places Europe | Start your project!

OSE is currently run as a BDFL under the direction of Marcin Jakubowski. The governance structure revolves around the completion of the GVCS 50 tools by 2028, with the following requirements:

1. OSE Roadmap - involves a prioritized and strategic rollout that is negotiable only by the Board of Directors, with decisions influenced by OSE Advisors. Yearly Critical Paths are drafted.
2. Anyone is welcome to develop and document GVCS or related products on the OSE Wiki, which is openly editable.
3. All contributions to the wiki are open source according to the OSE License
4. Product and strategy must comply with OSE Spec, and can be evaluated by the OSE Spec Score. Compliance with Product Ecologies further specifies the development path. It should be specified that the greatest governance risk is assuring compliance with OSE Spec and Product Ecologies. The reason for OSE Spec and Product Ecologies is to create a minimum, lowest cost set that still meets or exceeds industry standards - but does so at a theoretically achievable 100-1000 lower cost. The lower cost is achieved by open source (10x cost reduction), lifetime design (10x lower cost), and Modularity/Product Ecologies (10x). Open source, lifetime, modular design is the critical value proposition of OSE.
5. OSE is a Distributive Enterprise organization.
6. The primary activity of OSE is R&D&E -open source product Research and Development and Education. Distinctions are made between 4 units of OSE operations: OSE Inc, the corporate entity that is a container for OSE activity; OSE global, collaborative, open source appropriate technology R&D; facility operations at the OSE Headquarters or other campuses; and its revenue-generating enterprises (XM Workshops, kit production, training, immersion workshops, swag, and other)
7. OSE is a meritocracy. Merit is gained by involvement in the core development process and by certification. OSE Certification can occur as a Development Team member, an OSE Fellow, or a producer using the OSE brand. Specific license agreements for using the OSE brand are crafted on an individual basis.
8. OSE Org Chart defines roles. Current filled roles are the BDFL, CTO, Graphics Lead, Community Manager, and Power Cube Lead.
9. OSE Fellows are the highest status of developer at OSE as a full time role. Fellows do R&D on the Critical Path, and work together with the CTO on product development, as verified by the ability to generate revenue via Extreme Manufacturing Workshops.
10. CTO and Fellows make collaborative decisions on specifics of products, where products comply with the Roadmap, Critical Path, and OSE Spec. Simple majority determines specifics of product instances, with CTO and Fellows having one vote each.
11. Fellows make a quarterly individual product release, with Product Release added to the Critical Path.
12. Fellows may tap OSE Developers and SMEs for assistance in their Product Release Schedule.
13. Product Releases are tracked via the Simple Development Template with 100% marking complete burndown
14. CFO makes funding decisions. Fellows can submit research budgets for approval by CTO. CTO evaluates proposals based on OSE Spec. Fellows must be in Good Standing
15. OSE Developers are official part time developers. OSE Developers may submit requests to the CTO for resource support in their prototyping tasks if they are in Good Standing.

There are forks of OSE which encourage the true Open Source philosophy and have a democratic hierarchy, like

OSEG - Open Source Ecology Germany[[1]]

OSEE - Open Source Ecology Europe[[2]]

OTF - Open Tech Forever[[3]]

OSE_Fr - Open Source Ecologie in France [[4]] basing its governance on Sociocratic principles.