Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
From “VOLTTRON” to “Eclipse VOLTTRON”:
What It Means and Why It Matters
Wayne BeatonDirector of Open Source Projects
Eclipse [email protected]
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Paul WhiteVP, Member Services
Eclipse [email protected]
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
2Why??????
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Platform for Open Innovation and Collaboration
3
275+Members
350+Projects
1500+Committers
30Professional Staff
By the Numbers
10Working Groups
200M+Lines of Code
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Software is eating the world
4
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
90% of automotive innovations are from software
Mercedes S-Class, Infotainment Subsystem, 20 Mio. LOC50 – 100, networked, ECUs
5
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Open source software is eating the world
6
4xIncrease in open source
private financing over 2011 –’16
65%55%% companies leverage open
source in production % firms contributing to open
source projects
Source: https://opensource.com/business/16/5/2016-future-open-source-survey
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
“Every industrial company will become a software company”
Former GE CEOJeff Immelt
http://www.ge.com/ar2013/pdf/GE_AR13_Letter.pdf 7
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
“Every software company is an open source company”
Eclipse Foundation’s Executive Director: Mike Milinkovich 8
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
But what is “open source”?
9
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Freedom 0 - to run the program, for any purpose
Freedom 1 - to study how the program works, and change it to make it do what you wish
Freedom 2 - to redistribute copies
Freedom 3 - to distribute copies of your modified versions to others
Software Freedoms
10
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
• Is Open Source chaotic?• How does development really work?• What is this “Open Source community”?• How do you manage community contributions?• How do you plan in Open Source?• Isn’t open source going to infect our intellectual
property?• Why would we open source our assets?
Open source questions
11
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
•Better, smarter business–Save costs, faster time to market, improve quality
•Enables collaboration–Consistent sharing of IP
•Rapid adoption of technology–It is free and easy to access
•Scale
Why open source?
12
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Free….
...just likepuppies
By Lucie Tylová, Westik.cz - Westieinfo.com - soukromý archiv, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=4782396
13
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
▪ Far higher levels of experimentation
▪ Innovation through integration
▪ Permissionless innovation
KEEP CALMAND
INNOVATE
Innovation
14
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Predictability
15
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Contribution
● Reduce Costs● Influence
Direction● Attract Talent
16
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
What is an Eclipse Project?The Eclipse Development Process
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
17
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Eclipse Development Process
Defines a process for “success” in open source.
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
0DENY
VALUE
SINGLE PROJECT MULTIPLE PROJECT
TIME
SCOPE
BUSINESS DRIVEN
ENGINEERING DRIVEN
1USE
2CONTRIBUTE
3CHAMPION
4STRATEGIC
INVESTMENT
Open Source Maturity Model
19
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
TL;DR
An Eclipse Project...• Conforms to the EDP and Eclipse IP Policy;• Calls itself an “Eclipse Project” and conforms to Eclipse
Foundation Branding Guidelines;• Operates independently from any specific vendor;• Uses infrastructure provided by the Eclipse Foundation for
core content.
20
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Eclipse Development Process
The Eclipse Development Process is concerned with establishing practices that make projects successful in open source.
• Open Source Rules of Engagement • Level playing field: open, transparent, meritocratic
• Enable an Ecosystem; develop community• Engage in practices that ensure continued viabilityEvery member of the community must have an equal chance to participate
21
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Eclipse IP Policy
The Eclipse IP Policy is concerned with establishing practices to mitigate legal risks associated with building products based on Eclipse software
• Licensing• Copyright• Provenance trackingThe Eclipse IP Team vets significant “project code” contributions and all “third-party” content
22
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Trademarks and Branding
The Eclipse Foundation holds all project trademarks on behalf of the community.
• Trademarks must be managed to remain valid• Cycle of value
• The Eclipse brand adds value to project trademarks• Project trademarks add value to the Eclipse brand
23
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Who’s Who?
24
Governance, oversight
PMC
Committers
Project
Git Issues
Manage, plan, schedule, ...
Push, accept pull requests
Resolve
Contributors
Pull requests
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Rules
Open. Transparent. Vendor neutral.
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Source Code Must Be Up-to-Date
The community must have access to up-to-date source code.• It is impossible to contribute to a project if the available
source code is not up-to-date• You cannot build a community around a project if the
project team excludes the community from the development process
• Project code must be buildable
26
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Communication Must be Open
The community must be able to participate in project communication.
• It is impossible to contribute if you don’t know the project’s goals
• You can’t build community if you can’t communicatePlans, schedule, code, issue tracking, meetings/minutes, ...
27
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The Playing Field Must be Level
The playing field must be level; open to all comers.• All ongoing development activity must be committed to
the official, public repository• Everybody must be able to obtain the code and make use
of it according to the project license• Everybody must be able to raise issues and otherwise
engage directly with project developers• Everybody should be able to build the project code
28
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Must Conform to Policy and Process
• Projects must conform to the Eclipse Development Process• Projects must conform to the Eclipse IP Policy and engage
in the Eclipse IP Due Diligence Process• Projects must conform to the trademark usage and
branding guidelines
29
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Must Reinforce Project Branding
All projects must call themselves an Eclipse Project.• Clear association between the project and an EF brand
must be re-enforced, e.g.• Eclipse Paho• LocationTech GeoTrellis• PolarSys Rover
• All project content must use the associated brand• e.g. project website, documentation, etc.
• Namespaces re-enforce brand• e.g. org.eclipse.paho.*
30
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
“The Keys” Must be Kept Safe
Core infrastructure must be immune from domination by any single individual or organization.
• The EF must hold the keys for core infrastructure• Pick up and carry onOwnership of non-core infrastructure must be shared• Must be able to survive departures of team members
31
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Core Content
Metadata. Source code. Issue Trackers.
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Project Metadata is Core Content
Projects must use the Project Management Interface (PMI) to maintain Project Metadata.
• Teams must keep project metadata up to date• Release plans• Where to find downloads• Where to find repositories, how to build, …• Where to find documentation
33
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Source Code is Core Content
Source code must be actively developed on infrastructure provided by the Eclipse Foundation.
• Official project Git repositories must be the central authority
• Committers must push regularly to official project repositories
• Test code is source codeLevel playing field; open to all comers.
34
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Documentation is Core Content
Documentation is a first-class project resource.• Documentation maintained using the same rules as source
code• Must be deployed on EF infrastructure
• EF website, downloads, documentation server, ...
• May also be deployed elsewhere• e.g. Community website, ReadTheDocs
35
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Issues/Bugs/Tickets are Core Content
Issues must be tracked using infrastructure provided by the Eclipse Foundation.
• Bugzilla• GitHub Issues
36
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Project Dev List is Core Content
The Project Dev list is the main means of contact between the Eclipse Foundation (staff and automatic services) and project team.
• Formal EF process must happen on the devlist (practical: votes, etc.)
• Other project communication must be captured in a public channel
37
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Non-Core Content
Other content must be transparent and open but not necessarily owned/operated by the EF
• User forum discussions, presentations• Builds and downloads• Examples, blogs, social media handles, …Project team must have a means of sharing “the keys”• No single individual or company can exert control
38
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
What Does the Eclipse Foundation Do?
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
39
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
40
MissionStatement
The Eclipse Foundation’s purpose is to advance our open source projects and to cultivate their communities and business ecosystems.
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Building blocks for Innovation and Collaboration Requires:
Infrastructure
IP Management & Licensing
Process & Governance
Community Development
41
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
● Community of Practices: Eclipse Development Process
● Vendor-neutral governance structure○ Legal entity, bylaws, member agreement,
anti-trust policies
● Well defined project lifecycle
● Technical decisions made by project leadership
Process & Governance
42
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
IP Management & Licensing
43
● Management of Committer and Contributor Agreements
● Provenance and License Compatibility
● Trademark ownership for project names
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Community Development
44
● Business development staff to assist with recruitment
● Professional marketing staff
● Event planners
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Infrastructure
45
● Professionally managed open source forge
● Git, Gerrit, Jenkins, download servers, web site hosting
● Scalable and repeatable build service
● SLA for 99.99 uptime
● Flexibility to use Github
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
46
Eclipse Development Process
Defines a process for productizing open source
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Eclipse Working GroupsEnabling Collaborative Development
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
47
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Working Group - Value Proposition
Defines the relationship among companies engaged in a collaborative effort
Represents a formal business relationship with defined common goals
Includes all organizations interested in the target technology
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Sample Initiatives
49
• Joint Governance• Co-Funding• Branding• Specifications and certification
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Eclipse Working Groups Today
50
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
51Copyright (c) 2017, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Validated by Industry Leaders
“No company can realize the IoT on its own… Within the Eclipse Community, through the contribution of many IoT developers, tools and standards are created on an open platform that many companies can benefit from for their IoT applications.”
Stefan FerberCEO, Bosch Software Innovations
Infrastructure
IP Management & Licensing
Governance & Process
Community Development
52
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Parting thoughts...
53
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
The community is the capacity
54
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Engage,Experiment,
Educate
55
Copyright (c) 2018, Eclipse Foundation, Inc. | Made available under the Eclipse Public License 2.0 (EPL-2.0)
Thank-you!
[email protected]@eclipse-foundation.org
www.eclipse.org 56