Hide last authors
sheeri 9.2 1 Time: Thursday April 21st, 2016, 18:00-21:00
mollydb 1.1 2
lhawthorn 10.1 3 **Location**: [[Bocoup Office>>url:https://bocoup.com/]]
mollydb 1.1 4
5 201 South Street, Floor 1
6 Boston, MA 02111
7
lhawthorn 10.1 8 The Bocoup folks ask that attendees enter through our back door at 50 Utica St., Boston, MA
9
10 **Parking**:
11
12 Street parking is metered but inconsistent in the area
13
14 //Parking Garages//:
15
16 South Station Garage: Address: 750 Atlantic Ave, Boston, MA 02111 ~/~/ Phone: [[(617) 345-0202>>path:tel:%28617%29%20345-0202]]
17
18 Chinatown Garage: Address: 125 Lincoln St, Boston, MA 02111 ~/~/ Phone: [[(617) 416-6201>>path:tel:%28617%29%20416-6201]]
19
20
21 **Public Transportation/ MBTA**:
22
23 South Station (Red Line) is a 5 min. walk away
24
25 Chinatown Station (Orange Line) is an 8 min. walk away
26
27 **Agenda**
28
lhawthorn 4.2 29 Come meet the OSI Board! At this town hall style meeting, members of the OSI Board will share their ideas and plans for the future, talk about the organization's mission and concerns, and, hopefully, hear from you about your ideas and how you think the OSI can best serve the open source community.
mollydb 1.1 30
mollydb 2.2 31 There will be snacks and (non-alcoholic) drinks!
mollydb 4.1 32
mollydb 7.1 33 RSVP below:
mollydb 4.1 34
mollydb 7.1 35 1. Deb Bryant
36 1. Molly de Blanc
37 1. Leslie Hawthorn
38 1. Patrick Masson
39 1. Mike Milinkovich
40 1. Allison Randal
41 1. Paul Tagliamonte
42 1. Italo Vignoli
43 1. Stefano Zacchiroli
ChrisAniszczyk 7.2 44 1. Chris Aniszczyk (tentative)
DuaneObrien 8.2 45 1. Duane O'Brien
ShaneCurcuru 8.3 46 1. Shane Curcuru
mollydb 4.1 47
48 (((
49 [[Read more about the OSI Board>>url:https://opensource.org/docs/board-annotated]].
lhawthorn 4.2 50
51 Read the [[Beyond-Licensing email archives>>url:https://lists.opensource.org/pipermail/beyond-licensing/]] for more details about the project.
lhawthorn 10.2 52
53 **Meeting Notes**
54
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 * 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 * Open standards requirements are a good addition to the purview of the OSI
Deborah Bryant 10.25 58 * Branding is important for open source projects, see recent post from Shane Curcuru on Beyond Licensing list
lhawthorn 10.2 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 ** People want to work on projects because of the "brand" - reputation, credibility, etc.
lhawthorn 10.3 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.
62 ** Foundations exist to hold marks and allows for use of them in a sane way, e.g. differently than a trademarked name of a 'project' which is owned by a VC funded company
lhawthorn 10.4 63 ** Company involvement can skew the perception of your project before you are aware it is happening
lhawthorn 10.5 64 * Open source needs marketing & marketing education! ~^~^
lhawthorn 10.4 65 ** OSI can provide education and basic models for trademark usage or amplify signal of modern trademark guidelines & FOSS Marks project
66 ** Guide on what to worry about and when in your lifecycle for branding for projects so you don't burn cycles or get co-opted
lhawthorn 10.6 67 ** 80% of trademark enforcement can be done with no cash outlay, just by sending a letter - can OSI provide templates for these polite letters?
lhawthorn 10.8 68 * Governance models
69 ** Copyright aggregation - this can be dangerous if any one entity exercises too much control over code base copyright
lhawthorn 10.10 70 ** How do we organize our open source project
lhawthorn 10.8 71 * Social responsibility of the open source movement / organizations within it
72 ** Are codes of conduct something we should talk about as a best practice?
lhawthorn 10.9 73 ** Free software and policy, e.g. bill introduced in New York City Council advocating government prefer FOSS in procurement - cuts costs, use local contractors vs. big vendors, set target for amount of open source being used, software produced by government should be released as open source
lhawthorn 10.10 74 * How to tell if a particular project is "good" to engage with / contribute to
75 * How do we engage authentically with open source communities when we're a business using/creating open source software
76 * OSI has capacity and neutrality to compile and index this kind of best practices content, the question is where to start - we want to be the 'reference desk'
77 ** Would there be a peer review process for this content?
78 ** What is the approval process for a particular document / syllabus / piece of work?
79 *** Could be the committer model to avoid endless debate
80 * Employee and employer relationship around open source stuff - employment contracts, expectations of time to spend contributing, copyright assignment in work for hire situations, etc.
lhawthorn 10.15 81 * Sustainability of working on open source as an independent developer
82 * Dealing with large and old companies trying to figure out how to use and deal with open source software and change agency within their organization
lhawthorn 10.19 83 ** documenting the journey of these long existing companies to open source, e.g. Airbus determining the only way to support software in their aircraft, which can be in service 50-80 years, requires open source
lhawthorn 10.20 84 * Case study approach for business models of open source
lhawthorn 10.24 85 * Bridging the gap with younger/newer open source engineers who have a different understanding of these values and what they need
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
Deborah Bryant 10.25 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!
mollydb 4.1 121 )))

Submit feedback regarding this wiki to webmaster@opensource.org

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