Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -14,7 +14,7 @@
14	14	* [[Open Clinical>>url:http://www.openclinical.org/]]
15	15	* [[Open Everything>>url:http://www.northatlanticbooks.com/catalog/display.pperl?isbn=9781583944431]] ... and so on.
16	16
17		-I would like to collaborate with the OSI community to formulate a set of criteria through which the OSI could usefully build upon its role as the primary touchstone "brand of trust" for designating **//genuine "open source" production and distribution//**, in a world where "open" branding has become ubiquitous (good) and ambiguous (not good). Of course, it's been wonderful to see the concept proliferate, but what's there to do about "[[openwashing>>url:http://opensource.com/business/14/12/openwashing-more-prevalent]]"? I suggest there's no better-placed entity than the OSI to establish a certification program for "open source" claims beyond the software realm. The OSI could strategically and pro-actively build upon the derivative logo arrangement that was worked out (after-the-fact and a little haphazardly) with [[OSHWA>>url:http://www.oshwa.org/2012/10/17/co-existence/]] to proactively come up with a series of OSI logos derived from the primary logo, for OSI-certified "openness" in domains other than software. This remains to explore and discuss, and I understand that it's a non-trivial proposal. With your vote, I commit to working with others to formulate the concept with various options, and to help facilitate thoughtful consideration. I also commit, of course, to accepting a considered decision by the members and Board to not pursue such a direction.
	17	+I would like to collaborate with the OSI community to formulate a set of criteria through which the OSI could usefully build upon its role as the primary touchstone "brand of trust" for designating **//genuine "open source" production and distribution//**, in a world where "open" branding has become ubiquitous (good) and ambiguous (not good). Of course, it's been wonderful to see the concept proliferate, but what's there to do about "[[openwashing>>url:http://opensource.com/business/14/12/openwashing-more-prevalent]]"? I suggest there's no better-placed entity than the OSI to establish a certification program for "open source" claims beyond the software realm. The OSI could strategically and pro-actively build upon the derivative logo arrangement that was worked out (after-the-fact and a little haphazardly) with [[OSHWA>>url:http://www.oshwa.org/2012/10/17/co-existence/]] to proactively come up with a series of OSI logos derived from the primary logo, for OSI-certified "openness" in domains other than software. This remains to explore and discuss, and I understand that it's a non-trivial proposal. With your vote, I commit to working with others to formulate the concept with various options, and to help facilitate thoughtful consideration. Of course, if after thoughtful consideration the OSI members and the Board decide to not pursue such a direction, I'll be fine with that. I just think the idea should be thoroughly considered.
18	18
19	19	== Enhance the Free/Libre/Open Works (FLOW) Syllabus ==
20	20
...	...	@@ -30,7 +30,7 @@
30	30
31	31	More about my perspective on OSI and the free/libre/open way is available in an interview in the [[November 2014 OSI Newsletter>>url:http://opensource.org/201411Newsletter]]. Here also is a[[ draft version of an academic article>>url:http://projectmanagementhotel.com/attachments/6065/jpotvin_tim-review_resilient-coordination_17jan2015PDF.pdf]] submitted for publication next month in Technology Innovation Management Review. (This version is still in editing, and will be taken offline when the official version gets published in [[TIM Review>>url:http://timreview.ca/]].) In this paper I propose a generalization of the multi-entity coordination methodology that was originally developed through the past three decades by the global free/libre/open source software movement. I offer a general structure for visualizing resilient multi-entity coordination in any domain.
32	32
33		-In Section 2 below I outline two fields in which I have been actively applying the free/libre/open way in domains other than software.
	33	+In the sections below, I outline two fields in which I have been actively applying the free/libre/open way in domains other than software.
34	34
35	35	= I Am What I Do... I Think =
36	36