enabling industry collaborations

Download Enabling Industry Collaborations

Post on 10-May-2015

990 views

Category:

Technology

0 download

Embed Size (px)

TRANSCRIPT

  • 1.Eclipse Foundation: Enabling Industry Collaborations

2. Open Innovation Open Innovation is a paradigm that assumes that firms can and should use external ideas as well as well as internal ideas. The Open Innovation paradigm treats R&D as an open system. Open Innovation is sometimes conflated with open source methodologies for software developmentWhile open source shares the focus on value creation throughout an industry value chain, its proponents usually deny or downplay the importance of value capture. from Open Innovation: Researching a New Paradigm 3. The Drive for Collaboration Improved Supply Chain Efficiencies Reduce cost and waste of software development Better integration of supply chain Enable innovation within the supply chain Drive Forward New Technology Platforms Increased importance of interoperability between organizations and technologies Software is a core competency in all industries Capitalize on Open Source Maturity 4. AIRBUSFRANCES.A.S.Tousdroitsrservs.Documentconfidentiel. Open Source Day SIEMENS-VDO 27th September 2006 page Supply Chain Efficiencies One example : AIRBUS A300 Program began in 1972 and will stop in 2007 2007-1972 = 35 years... Support will last until 2050 2050-1972 = 78 years !!! On board software development for very long lifecycle products 5. Defects in Ecosystem 6. Collaboration in the Software Industry Software development cost structures today have no correlation to creating value for customers. 80% of new costs and maintenance costs go to build and support infrastructure for which companies derive zero differentiating product value. Infra Value 7. Compete On What Matters Define very precisely what your competitive differentiators are for your customers or youre going out of business Focus all possible energies there, and acquire everything else from OSS, or help build it in OSS Infra Value 8. Open Source Maturity Model 0. Deny 1. Use 2. Contribute 3. Champion 4. Collaborate 5. Redefine Scope Time Value Captured Value co-creation Value capture Coupling management Multiple Projects Single Project Business DrivenEngineering Driven 9. What do you need for open collaborations 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 9 10. Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure What do you need for open collaborations? 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 10 11. Governance Who and how are decisions made? Who controls the intellectual property: copyright, trademark, dom ain names, etc.? Does anyone or company have special status or is it a level playing field for all parties? 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 11 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 12. Infrastructure A forge to host the development and IP Code repositories Bug database IP Management database Web sites, wikis Download mirrors Build and release management 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 12 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 13. IP Management and Licensing Consistent and common set of legal agreements that will cover the intellectual property created by the collaboration. Software license that allows for downstream commercialization. For open source projects, IP Management that ensures license compatibility. IP cleanliness to ensure provenance 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 13 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 14. Projects and Processes Development process that enables large-scale distributed development Support involvement of many different organizations Open source project based on the principles of openness, transparency and meritocracy 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 14 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 15. Ecosystem Development 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 15 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure How do ecosystems grow and add value? How can all stakeholders participate? What are the best practices for creating an ecosystem? 16. Eclipse Working Groups 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 16 17. Eclipse Working Groups Eclipse is the industrys best model for vendor- neutral collaboration Eclipse Working Groups: Licensing model for sharing co-developed innovation IP management to maximize commercialization opportunities Project model for coordinating investments and activities Governance model to ensure a level playing field for all participants Eclipse gives you these out of the box 12-Dec-2012 17Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 Governance IP Mgt & Licensing Projects & Process Ecossytem Development Infra-structure 18. Projects and Process at Eclipse 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 18 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 19. Community of Projects 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 19 Over 250 Open Source Projects 20. Eclipse Project Lifecycle 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 20 Proposal Incubation Mature Top Level Project Creation Review Graduation Review Archived Board Approval 21. Principles of Open Source Projects @ Eclipse 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 21 Transparent Open Meritocratic 22. Technology Agnostic Definition of an Eclipse Project: Conform to the Eclipse Development Process Conform to the Eclipse Intellectual Property Policies and its related procedures Licensed under the Eclipse Public License unless otherwise and unanimously approved by the Board. There is no requirement that Eclipse projects must utilize the Java language or OSGi modularity (plug-in) model. 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 22 23. Large Scale Distributed Development 12-Dec-2012 23Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 3 7 10 21 23 33 39 62 72 17 18 24 33 46 55 0 10 20 30 40 50 60 70 80 Eclipse 3.0 Eclipse 3.1 Callisto Europa Ganymede Galileo Helios Indigo Juno Projects Million LOC 24. Foundation Services 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 24 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 25. Eclipse Public License Default license for all Eclipse projects Commercially friendly weak copyleft license Allows commercial re-licensing of binaries Modern patent license, with reasonable termination clause in event of litigation 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 25 26. Dual-licensing With the approval of the Board, Eclipse projects can be dual-licensed Most common scenario is EPL + BSD(3-clause) We have our own named EDL (Eclipse Distribution License) Dual licensed projects include: Orion, Lyo, EclipseLink and JGit. Jetty and Gemini are dual-licensed EPL+ALv2 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 26 27. Licensing Flexibility Working Groups can have blanket Board approvals for hosting projects under other licenses. Examples: Polarsys: EPL and LGPL LocationTech: EPL, MIT, BSD and ALv2 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 27 28. IP Management at Eclipse Code Originates from Three Sources 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 28 Committers Contributors Third party source (other OSS projects) Eclipse Projects 29. IP Due Diligence Check for: Provenance: Who wrote this code and how did they agree to the license? License suitability: Is license compatibly with project license Patent searches are not done. What is checked: Initial contributions for new projects Significant new contributions from contributors (>250 loc) All third party open source projects included in Eclipse projects 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 29 30. We Use Tools to Help Us Keyword search tools (from IBM) Code print matching tools (Black Duck) IPZilla content management and workflow 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 30 31. Foundation Services 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 31 Governance IP Mgt & Licensing Projects & Process Ecosystem Development Infra- structure 32. Open Infrastructure 12-Dec-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 32 Code Repositories Bug Tracking Continuous Integration Build Code Review Tool 33. 99.8% ++ uptime of last 6 years High Availabi

Recommended

View more >