Changes for page Joseph Potvin 2015

Last modified by Administrator on 2016/04/05 11:27

From version 1.1 >
edited by Joseph Potvin
on 2015/02/22 19:42
To version < 2.1 >
edited by Joseph Potvin
on 2015/02/22 20:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,15 +10,15 @@
10 10  ** [[Open Source Industrial Machinery>>url:http://opensourceecology.org/]]
11 11  ** [[Open Source Prosthetics>>url:http://openprosthetics.org/]]
12 12  * [[Open Clinical>>url:http://www.openclinical.org/]]
13 -* [[Open Everything>>url:http://www.northatlanticbooks.com/catalog/display.pperl?isbn=9781583944431]]
13 +* [[Open Everything>>url:http://www.northatlanticbooks.com/catalog/display.pperl?isbn=9781583944431]] ... and so on.
14 14  
15 -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). Yes 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 entity better placed than 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.
15 +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 disscuss, 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.
16 16  
17 17  == 1.2 Enhance the Free/Libre/Open Works (FLOW) Syllabus ==
18 18  
19 -I'd like to advance [[the FLOW Syllabus>>url:http://wiki.opensource.org/bin/Projects/flow-syllabus]] in several ways to support continuing education. This is a curated collection of online external learning resources that offer clear and useful freely-available web-based information from diverse sources to explain or illustrate the free/libre/open way (ethics, methods, processes, governance, HR management, strategy, security, law or financing). This syllabus does not shy away from delving deeply into primary concepts. It is [[designed for both business and technical people>>url:http://wiki.opensource.org/bin/download/Projects/flow%2Dsyllabus/flow%2Dsyllabus_intro_15jul2014PDF.pdf]].
19 +With your vote, I'd like to advance [[the FLOW Syllabus>>url:http://wiki.opensource.org/bin/Projects/flow-syllabus]] in several ways to support continuing education. This is a curated collection of online external learning resources that offer clear and useful freely-available web-based information from diverse sources to explain or illustrate the free/libre/open way (ethics, methods, processes, governance, HR management, strategy, security, law or financing). This syllabus does not shy away from delving deeply into primary concepts. It is [[designed for both business and technical people>>url:http://wiki.opensource.org/bin/download/Projects/flow%2Dsyllabus/flow%2Dsyllabus_intro_15jul2014PDF.pdf]].
20 20  
21 -This resource arose initially from my own firms's 2013 commercial contract with a Fortune 500 company that asked for a 5-day internal training course for their managers who had already been highly active in free/libre/open projects for years, but who wanted understand several complex issues more deeply. I suggesting to my client that this was a common need, and that we ought to make this a re-usable collection of learning materials that could be shared with anyone. I could then deliver to them a particular instance of the course on-site. They enthusiastically agreed. After delivery, my client and I jointly approached the OSI to ask if they'd like to host further development of the syllabus as a shared resource for advanced learning about the free/libre/open way. This initiative now involves collaboration with the [[Open Educational Resource university (OERu)>>url:http://oeru.org/]] and others. In 2014 the FLOW Syllabus has expanded to include the FLOW Video Series (coming soon!) with the first three episodes being animated and produced by the communications team at [[University of Southern Queensland>>url:http://www.usq.edu.au/]] all under CC-by 4.0:
21 +This resource arose initially from [[my own firm>>url:http://www.opman.ca]]'s 2013 commercial contract with a Fortune 500 company that asked for a 5-day internal training course for their managers. They had already been highly active for years in advanced free/libre/open projects, but they wanted to more fully understand several complex issues and get up-to-date on recent court decisions and conceptual developments. I suggesting to my client that this was a common need, and that we ought to make this a re-usable collection of learning materials that could be shared with anyone. I could then deliver to them a particular instance of the course on-site. They enthusiastically agreed. After delivery, my client and I jointly approached the OSI to ask if they'd like to host further development of the syllabus as a shared resource for advanced learning about the free/libre/open way. This initiative now involves collaboration with the [[Open Educational Resource university (OERu)>>url:http://oeru.org/]] and others. In 2014 the FLOW Syllabus has expanded to include the FLOW Video Series (coming soon!) with the first three episodes being animated and produced by the communications team at [[University of Southern Queensland>>url:http://www.usq.edu.au/]] all under CC-by 4.0:
22 22  
23 23  * Episode 1: "Constraints on the FLOW of Ideas for Devices"
24 24  * Episode 2: "Expression of an Abstract Idea + Tangible Device" (Explanation of the reasons for decision in the 2014 US Supreme Court Case, Alice Corp v. CLS Bank)
... ... @@ -25,10 +25,12 @@
25 25  * Episode 3: "Do You Want to RENT an Idea? Or Harness the FLOW of Ideas?"
26 26  
27 27  
28 -== 1.3 Some Recent Reflections ==
28 +== 1.3 Some General Reflections ==
29 29  
30 -More about my perspective on OSI and the free/libre/open is available in an interview in the [[November 2014 OSI Newsletter>>url:http://opensource.org/201411Newsletter]]. Here also is a[[ draft version of an article>>url:http://projectmanagementhotel.com/attachments/6065/jpotvin_tim-review_resilient-coordination_17jan2015PDF.pdf]] submitted for publication in Technology Innovation Management Review. It proposes 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, and outlines a general structure for visualizing resilient coordination in any domain.
30 +More about my perspective on OSI and the free/libre/open 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 get published in [[TIM Review>>url:http://timreview.ca/]].) I'm proposes 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, and I offer a general structure for visualizing resilient multi-entity coordination in any domain.
31 31  
32 +In Section 2 below I outline two fields in which I am actively applying the free/libre/open way in domains other than software.
33 +
32 32  = 2. I Am What I Do... I Think =
33 33  
34 34  == 2.1 Free/Libre/Open World (FLOW) Payments ==
... ... @@ -45,4 +45,4 @@
45 45  
46 46  * [[Open Source Security Strategy>>url:http://c2.com/cgi/wiki?OpenSourceSecurityStrategy]] (from 2003)
47 47  * Getting Open Source Login INto Governments ([[GOSLING>>url:http://www.goslingcommunity.org/]]; 2003-Present)
48 -* Government Official Open Source Engagement ([[GOOSE>>url:http://projectmanagementhotel.com/attachments/5938/gosling2goose_10years_4may2012.png]]; 2006-2012) The resulting "High Resilience Environment" (HRE) today provides the multi-organizational governance arrangements a free/libre/open system stack that runs the core infrastructure for several mission-critical services in Canada such as https://www.masas-x.ca/en/ and https://buyandsell.gc.ca/ and http://www.nss-snrs.gc.ca/en/index.page
50 +* Government Official Open Source Engagement ([[GOOSE>>url:http://projectmanagementhotel.com/attachments/5938/gosling2goose_10years_4may2012.png]]; 2006-2012) The resulting "High Resilience Environment" (HRE) today provides the multi-organizational governance arrangements a free/libre/open system stack that underlies some of the core infrastructure for several mission-critical services in Canada such as https://www.masas-x.ca/en/ and https://buyandsell.gc.ca/ and http://www.nss-snrs.gc.ca/en/index.page

Submit feedback regarding this wiki to [email protected]

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation