Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
© 2002 IBM Corporation
Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Mad...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
What is Eclipse?
Open Sour...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
History of the Eclipse Org...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
The Members of Eclipse
16 ...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Eclipse Eco-System – Commu...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Example of Eclipse Based C...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Eclipse Economics 101
Proj...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Eclipse is a Level Playing...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
The Eclipse Community is U...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Technology Matters: Secret...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Process Matters: Is Open S...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Eclipse Project Lifecycle
...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
enable
validate
reduce
str...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Community Involvement
An a...
© 2002 IBM Corporation
Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Mad...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Why Open Source?
Open sour...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Open Source: The Next Step...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
The Business Model for
Ope...
© 2002 IBM Corporation
Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Mad...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Eclipse Uses OSGi
Eclipse ...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
OSGi Uses Eclipse
Eclipse ...
Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0
Future Steps
The Eclipse E...
© 2002 IBM Corporation
Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Mad...
Upcoming SlideShare
Loading in …5
×

Keynote - Eclipse - Accelerating OSGi Adoption - Mike Milinkovich, Executive Director Eclipse Foundation

361 views

Published on

OSGi World Congress 2005

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Keynote - Eclipse - Accelerating OSGi Adoption - Mike Milinkovich, Executive Director Eclipse Foundation

  1. 1. © 2002 IBM Corporation Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse: Accelerating OSGi Adoption Mike Milinkovich Executive Director Eclipse Foundation
  2. 2. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 What is Eclipse? Open Source Community Universal Development Platform Ecosystem Member Supported Foundation Builds Enables Enables Supports
  3. 3. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 History of the Eclipse Organization Initiated by IBM in 2001 and supported by a wide range of vendors. Original Consortium board comprised Borland, IBM, MERANT, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft and Webgain Eclipse Today Independent not-for-profit Foundation formed in 2004 111 members, including major Java, Linux and Embedded vendors (BEA, Borland, JBoss, IBM, SAP, RedHat, Novell, Monta Vista, Wind River, Mentor, ENEA, QNX,…) 50+ open source projects 50 million download request to date 1 million Eclipse 3.1 downloads in 40 days
  4. 4. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 The Members of Eclipse 16 Strategic Members 80 Add-in Providers 15 Associate Members (Publishers, Research Institutes, Standards Org., etc.) Large community of open source developers (500++)
  5. 5. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse Eco-System – Community of Add-in Providers 80 Add-in Provider members; 950+ available Eclipse add-ins 500+ Eclipse based projects on SourceForge www.eclipse-plugins.info www.eclipseplugincentral.com www.surceforge.net
  6. 6. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Example of Eclipse Based Commercial Tools Enterprise IT Borland Together Edition for Eclipse HP OCMP OClet Development Env. IBM Rational Application Developer Oracle Collaxa BPEL Designer SAP NetWeaver Studio Linux Novell/SuSE Linux SDK Red Hat Developer Studio Intel Compiler for Linux Embedded PalmOS Dev Suite Monta Vista DevRocket Wind River Workbench QNX Momentics TimeSys TimeStorm IDE Tensilica Xtensa Xplorer IDE Mentor Graphics Nucleus Edge
  7. 7. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse Economics 101 Projects Users Committers Vendors O pportunity Profits Adoption Quality Exemplary Tools APIs and Frameworks Licensing Model
  8. 8. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse is a Level Playing Field Eclipse is unique in the transparent way in which software firms co- operate in the creation of new technology A new model: The level playing field and open interaction of a standards organization …..with the wonderful attribute that the output actually runs! Innovation happens best in development, not in standards organizations This model is a large component of what drives companies to join as Strategic Members Shared cost, shared risk for developing the underlying building blocks for products Often based on open standards Still lots of room for competition All of this is predicated by having an open and transparent governance model
  9. 9. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 The Eclipse Community is Unique Commercial-friendly Most projects led by companies Compelling model for shared industrial development Commercial-friendly licensing model Focused on predictability Have hit their dates four releases in a row Open and transparent development and roadmap processes Recognition that predictability spurs adoption Focused on quality Explicit Eclipse quality objectives Focus on frameworks and extensible, exemplary tools Clearly defined mission The Eclipse technology is a vendor-neutral, open development platform supplying frameworks and exemplary, extensible tools
  10. 10. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Technology Matters: Secrets to Success Core (OSGi) Lightweight Extensible Core Project 1 Project 4 Project 2 Project 3 Eclipse-hosted projects E.g. the Java Development Tool Lots of others Open Source Projects Related Open Source Projects Vendor Vendor Vendor value-add User User User value-add Vendor and User value-add migrates into projects
  11. 11. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Process Matters: Is Open Source Chaotic? OS projects are highly structured Explicit rules (more than in most closed source projects) Who may change the source code? Who is responsible for delivering? Who decides about the architecture? … Commit right rules: public "meritocracy" Only a small number of developers can modify the source code: committers Key architecture defined by a small team of lead developers Peer pressure among committers – continuous reviewing Continuous review and feedback by the community Contributions from outside have to be reviewed by committers
  12. 12. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse Project Lifecycle Pre-proposal Proposal Validation/Incubation – establish a fully- functioning open-source project Implementation/Mature Archived – after reaching the end of their natural lifecycle Official Reviews between each phase
  13. 13. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 enable validate reduce stress deliberate The Eclipse Way continuous testing continuous integration consume your own output community involvement new & noteworthy retrospectives end game always have a client component centric dynamic teams built to last API first milestones firstearly incremental planning enable validate attract show progress transparency learn update validate explore
  14. 14. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Community Involvement An active community is the major asset of an F/OSS project F/OSS project gives and takes: F/OSS developer gives: Listen to feedback and react Demonstrate continuous progress Transparent development F/OSS developer takes: Answer user questions so that developers do not have to do it Report defects and feature requests Validate technology by writing plug-ins Submit patches and enhancements Give and take isn’t always balanced The community isn’t shy and is often demanding
  15. 15. © 2002 IBM Corporation Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Open Source and Open Standards
  16. 16. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Why Open Source? Open source allows multiple stakeholders to share the cost and benefits of a single shared implementation Vendors, customers and standards bodies can all participate as equals Multiple groups can influence and participate in the architecture and in the support of a freely available framework Consumers avoid proprietary lock-in Vendors can invest in a shared platform Multiple benefits for adopters: Open source allows for easier understanding of a framework Trace issues through the actual source code Don’t have to rely on only incomplete documentation Easy to workaround issues by modify source code and shipping it with your product. Open source project continues to fix defects and enhance the software No royalty for redistribution.
  17. 17. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Open Source: The Next Step 1980’s 2000’s 1990’sProprietary solutions – technology driven by vendors. Focus on barriers to entry and economic rents for vendors Consumer-driven demand for open standards and inter- operability. Implementations remain proprietary. Shared, open source implementation of standards. Vendors focus on differentiation and services.
  18. 18. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 The Business Model for Open Source and Open Standards Shared implementations of standards: Save time to market Increase rate of standards adoption Reduce risk Provide thought leadership and first mover advantages to supporting vendors Yes, open source means shareholder value! Vendors who share open source implementations still compete Product differentiating features Service, support Branding, routes to market
  19. 19. © 2002 IBM Corporation Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse and OSGi
  20. 20. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Eclipse Uses OSGi Eclipse is based on an implementation of the OSGi framework R4.0 specification The concept of an Eclipse plug-in is synonymous with an OSGi bundle Eclipse today has the best tooling environment for building and deploying OSGi-based applications GUI tool for manifest editing Manifest file validation
  21. 21. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 OSGi Uses Eclipse Eclipse 3.1 is an immediately available implementation of the OSGi R4.0 framework specification Based on Eclipse 3.0 experience, Eclipse team brought many requirements to the OSGi for consideration during R4.0 development Eclipse has placed OSGi implementations onto the machines of millions of Java developers
  22. 22. Copyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Future Steps The Eclipse Equinox project has “graduated” to become part of the Eclipse Platform top-level project Bring more visibility to the OSGi community at Eclipse The Embedded Rich Client (eRCP) project is aimed at bringing Eclipse runtime technology to mobile and constrained devices Continued partnership with the OSGi Alliance for the benefit of both organizations
  23. 23. © 2002 IBM Corporation Confidential | Date | Other Information, if necessaryCopyright © 2005, Eclipse Foundation, Inc. Made available under the Eclipse Public License v1.0 Thank you!

×