Leadership - Revision history

Marcin at 21:46, 26 September 2019

2019-09-26T21:46:04Z

← Older revision		Revision as of 21:46, 26 September 2019
Line 4:		Line 4:

	In open source hardware, structure is more fractal than in open source software projects. That means - while we follow [[Product Ecologies]] and a [[Construction Set Approach]] - any product can stand on its own as a complete project. Thus, governance should in principle be easier at OSE - as the entire economy is open for open-sourcing - and many leaders can rise up to take on leadership. This takes many people, and we welcome leaders rising across all product, service, and enterprise categories.		In open source hardware, structure is more fractal than in open source software projects. That means - while we follow [[Product Ecologies]] and a [[Construction Set Approach]] - any product can stand on its own as a complete project. Thus, governance should in principle be easier at OSE - as the entire economy is open for open-sourcing - and many leaders can rise up to take on leadership. This takes many people, and we welcome leaders rising across all product, service, and enterprise categories.

			=Links=
			*[[Meritocratic Do-ocracy]]

Marcin at 20:02, 26 September 2019

2019-09-26T20:02:37Z

← Older revision		Revision as of 20:02, 26 September 2019
Line 3:		Line 3:
	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 on the OSE wiki.		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 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.		In open source hardware, structure is more fractal than in open source software projects. That means - while we follow [[Product Ecologies]] and a [[Construction Set Approach]] - any product can stand on its own as a complete project. Thus, governance should in principle be easier at OSE - as the entire economy is open for open-sourcing - and many leaders can rise up to take on leadership. This takes many people, and we welcome leaders rising across all product, service, and enterprise categories.

Marcin at 20:01, 26 September 2019

2019-09-26T20:01:02Z

← Older revision		Revision as of 20:01, 26 September 2019
Line 1:		Line 1:
	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. The official projects included in the GVCS are shown at the [[Taxonomy]] page - if you know how to name it, you know how it fits with the GVCS. While there are 50 tools in the GVCS - there are many other related enterprises or derivatives that can be developed from these tools. Enterprise is important, as the project can grow only by generating customer-visible value. Thus, we include enterprise development - and in particular - [[Distributive Enterprise]] development - as the final level of development for any of our technologies.		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. The official projects included in the GVCS are shown at the [[Taxonomy]] page - if you know how to name it, you know how it fits with the GVCS. While there are 50 tools in the GVCS - there are many other related enterprises or derivatives that can be developed from these tools. Enterprise is important, as the project can grow only by generating customer-visible value. Thus, we include enterprise development - and in particular - [[Distributive Enterprise]] development - as the final level of development for any of our technologies.

	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.		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 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.		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.

Marcin at 20:00, 26 September 2019

2019-09-26T20:00:08Z

← Older revision		Revision as of 20:00, 26 September 2019
Line 1:		Line 1:
	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. The official projects included in the GVCS are shown at the [[Taxonomy]] page - if you know how to name it, you know how it fits with the GVCS. 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.		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. The official projects included in the GVCS are shown at the [[Taxonomy]] page - if you know how to name it, you know how it fits with the GVCS. While there are 50 tools in the GVCS - there are many other related enterprises or derivatives that can be developed from these tools. Enterprise is important, as the project can grow only by generating customer-visible value. Thus, we include enterprise development - and in particular - [[Distributive Enterprise]] development - as the final level of development for any of our technologies.

			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.		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.

Marcin at 19:57, 26 September 2019

2019-09-26T19:57:51Z

← Older revision		Revision as of 19:57, 26 September 2019
Line 1:		Line 1:
	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.		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. The official projects included in the GVCS are shown at the [[Taxonomy]] page - if you know how to name it, you know how it fits with the GVCS. 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.		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.

Marcin at 19:56, 26 September 2019

2019-09-26T19:56:35Z

← Older revision		Revision as of 19:56, 26 September 2019
Line 1:		Line 1:
	Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]], the [[OSE Vision]], and [[OSE Roadmap]]. In the voluntary project of OSE, leadership is essentially self-selecting. Technical leads ~~are selected~~ by the [[BDFL]].		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.

Marcin at 19:49, 26 September 2019

2019-09-26T19:49:13Z

← Older revision		Revision as of 19:49, 26 September 2019
Line 1:		Line 1:
	Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]], the [[OSE Vision, and [[OSE Roadmap]]. In the voluntary project of OSE, leadership is essentially self-selecting. Technical leads are selected by the [[BDFL]].		Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]], the [[OSE Vision]], and [[OSE Roadmap]]. In the voluntary project of OSE, leadership is essentially self-selecting. Technical leads are selected by the [[BDFL]].

Marcin at 19:35, 26 September 2019

2019-09-26T19:35:19Z

← Older revision		Revision as of 19:35, 26 September 2019
Line 1:		Line 1:
	Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]].		Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]], the [[OSE Vision, and [[OSE Roadmap]]. In the voluntary project of OSE, leadership is essentially self-selecting. Technical leads are selected by the [[BDFL]].

Marcin: Created page with "Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the GVCS. Commits must follow OSE Specifications."

2019-09-26T19:31:23Z

Created page with "Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the GVCS. Commits must follow OSE Specifications."

New page

Open Source Ecology product development generally follows governance via meritocracy. Merit is gained by commits to the [[GVCS]]. Commits must follow [[OSE Specifications]].