Changes for page Beyond-Licensing Town Hall Boston 2016
Last modified by Stefano Maffulli on 2021/09/21 00:37
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. debbryant1 +XWiki.lhawthorn - Content
-
... ... @@ -55,7 +55,7 @@ 55 55 * Beyond licensing: meant to explore open source just beyond the scope of licensing - what is the raison d'etre of the OSI beyond keeping a list of licenses 56 56 * A license is not enough to create a successful community & project, but these things are not as well defined as e.g. The Open Source Definition 57 57 * Open standards requirements are a good addition to the purview of the OSI 58 -* Branding is important for open source projects, see recent post from Shane Curcuru on Beyond Licensing list 58 +* Branding is important for open source projects, see recent post from Shane Curcuru on Beyond Licensing list 59 59 ** Company leadership who is disconnected from marketing dept understanding of open source and who co-opt open source brands / branding (e.g. Hadoop) 60 60 ** People want to work on projects because of the "brand" - reputation, credibility, etc. 61 61 ** Not every project needs to get to the point of needing "branding" but if you wait to long then your brand can have been coopted by businesses, etc. ... ... @@ -84,38 +84,4 @@ 84 84 * Case study approach for business models of open source 85 85 * Bridging the gap with younger/newer open source engineers who have a different understanding of these values and what they need 86 86 ** Newer projects didn't really care about licenses in the first place - look at GitHub 3-4 years ago, now GitHub is recommending a license as you spin up project 87 -* What if OSI was to do something along the lines of harvesting ideas from various sources and then link to references 88 -* Is it that difficult to do this? 89 -* Organizations need to understand the goverance model. We can make lists of things to read, but there is more guidance needed. 90 -* Can we think of a more modern word than governance?? 91 -* If not OSI, who? asks a board member. 92 -* Key idea is to find information to share rather than creating content whole cloth 93 -** to that end, Deb suggests the idea floater volunteer to do a trial project to create a page with reference 94 -* Would be valuable if OSI would come up with language that defined elements of governance 95 -** create a working group to measure the model 96 -** satifies our interest in bringing in new groups 97 -** would like to create a list of indicators that would indicate openness 98 -* The FLOSS Foundations tutorial (OSCON circa 2013-14) is great fodder for starting with material for sharing 99 -* OpenOffice community has actually grown without a community manager 100 - 101 -Recap and close round table: Take-aways, closing toughts, suggestions 102 - 103 -* OSI board should talk about how it's different than other open source entities. 104 -* What's OSI's role in this galaxy of stuff? If OSI can articulate that, from there what goes beyond licencing will fall out. 105 -* Working on licenscing , governance education will help the ecosystem evolve because otherwise. Also branding ad trademark. 106 -* (Patrick) I ike the idea of becoming a resource library of content. Would like to qualify what kind of contet would help. Also eats oru dogfood on reuse rather than creation. 107 -* We didn't talk about how we can get corporations to be better actors in open source. Would a good place to start be identiying exemplary projects 108 -* Josh Berkus's presentation "10 ways to competly destroy your open source project" would be a great resource for this. 109 -* One way to collect it woud be to start the governance model project "why it's important" to have governeace. 110 -* A good example of collecting governance comes from hackerspace design patterns, but it's helped blossomed there. 111 -* We've discussed many ideas we can do, but we need folks that will show up and do things. 112 -* Big issue, getting corporations to understand open source 113 -** increasing level of interest 114 -** need to help 115 -* OSI two things 116 -** Legacy: we can not afford to discontinue stewarding open source 117 -** Today yet: Help under 118 -* Metaphore: Chemical elements . In a more known world, it's understood how elements react together. 119 -* 120 -* Thanks all! 121 121 )))