2012.05 eclipse how it works

2,038 views
1,908 views

Published on

Presentation at the Eclipse Day Toulouse event on May 24, 2012

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,038
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
81
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

2012.05 eclipse how it works

  1. 1. Eclipse: How It WorksIan SkerrettVice President MarketingEclipse Foundation
  2. 2. Agenda• A quick introduction to Eclipse• Eclipse Open Source Engineering Processes• Open Source Business 101• The Open Source Maturity Model• Eclipse Industry Working Groups24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 2
  3. 3. Open Source Questions• Is Open Source chaotic?• How does development really work?• What about the Open Source community?• How do you manage community contributions?• How do you plan in Open Source?24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 3
  4. 4. Agenda• A quick introduction to Eclipse• Eclipse Open Source Engineering Processes• Open Source Business 101• The Open Source Maturity Model24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 4
  5. 5. Eclipse: The Leading Developer Community24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 5
  6. 6. Members of Eclipse24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 6
  7. 7. The Members of Eclipse  185 members  11 Strategic Members  1 Enterprise Member  1025 committers, representing 100+ organizationsStrategic MembersEnterprise Members24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 8
  8. 8. 8 Years in a Row70 6260 Indigo 62 Projects 46 Million Lines of Code50 400+ committers 46 49 companies40 18 countries 39 33 3330 24 23 2120 18 17 1010 7 30 Eclipse 3.0 Eclipse 3.1 Callisto Europa Ganymede Galileo Helios Indigo24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 9
  9. 9. So Eclipse Has...• Millions of users• Thousands of products• One thousand developers• Hundreds of companies, hundreds of projects• Predictable schedules• World class intellectual property management• Fifteen employees24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 10
  10. 10. Agenda• A quick introduction to Eclipse• Eclipse Open Source Engineering Processes• Open Source Business 101• The Open Source Maturity Model24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 11
  11. 11. 8 Years in a Row70 6260 Indigo50 62 Projects 46 Million Lines of Code 4640 39 33 3330 24 23 2120 18 17 1010 7 30 Eclipse 3.0 Eclipse 3.1 Callisto Europa Ganymede Galileo Helios Indigo24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 12
  12. 12. Platform Modularity: The Eclipse Experience Ease of Integration New Plug-ins are and Extensibility First Class Spurs Innovation Citizens – same footing for Plug-ins everyone Platform Run-time Open API and commercially friendly licensing – LowCompetition can take place barriers to Entryon implementations – usersdecide winners Successful Ecosystems are built on this model! 24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 13
  13. 13. The Project Lifecycle24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 14
  14. 14. How is the Development Done? continuous continuous consume your testing integration validate own output enable drive with open eyes community end “The Eclipse Way” reduce stress transparency involvement game milestones attract Erich Gamma and John Wiegand always have first show progress to latest new & a client update learn noteworthy validatecomponent early incremental API centric planning first retrospectives enable explore dynamic built to validate teams last24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 15
  15. 15. Open Source Rules• 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 rights: 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 committers24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 16
  16. 16. Planning continuous continuous consume your testing integration validate own output enable drive with open eyes community end reduce stress transparency involvement game milestones attract show progress to latest first always have new & a client update learn noteworthy validatecomponent early incremental API centric planning first retrospectives enable explore dynamic built to validate teams last24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 17
  17. 17. Planning• Release themes establish big picture – Community input – Planning council new source of input• Component teams define component plans• Project Management Committee collates initial project plan draft – Tradeoff: requirements vs. available resources – committed, proposed, deferred• Plan initially spells out – themes – milestones – compatibility (contract, binary, source, workspace)• Plan is alive24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 18
  18. 18. Ongoing Risk Assessment• Address high risk items and items with many dependencies early• Maintain schedule by dropping items (if necessary) – we will drop proposed items – we hate to drop committed items – prefer fewer completed items than more items in progress• High risk items are sandboxed to reduce risk to other items – prefer to serialize highest risk items (to minimize integration pain)24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 19
  19. 19. Project Rhythm continuous continuous consume your testing integration validate own output enable drive with open eyes community end reduce stress transparency involvement game milestones attract show progress to latest first always have new & a client update learn noteworthy validatecomponent early incremental API centric planning first retrospectives enable explore dynamic built to validate teams last24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 21
  20. 20. Milestones• break down release cycle into milestones • before/after – We use 6 weeks quality• milestones are a miniature development cycle ready to ship – Plan, execute, test, retrospective• milestone builds are good enough to be used by the community t 3.5 3.6 “hanging rope” milestones reduce stress, keep quality high
  21. 21. Continuous Integration• Fully automated build process• Build quality verified by automatic unit tests• Staged builds – nightly builds (some projects even more frequently) • discover integration problems between components – weekly integration builds • all automatic unit tests must be successful • good enough for our own use – milestone builds • good enough for the community to use24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 23
  22. 22. Practice Makes Perfect• 7 milestones, 4 release candidates – 11 chances to practice releasing• Projects denoted N0, N1, N2, N3 – Build in order of dependencies – Early builds takes days, later builds take hours• Build to shared repository, make everything available to the community for feedback and testing24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 24
  23. 23. Community Involvement • An active community is the major asset of an OSS project • OSS project gives and takes: – OSS developer gives: • listen to feedback and react • demonstrate continuous progress • transparent development – 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 – community isn’t shy and is demanding24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 26
  24. 24. Testing continuous continuous consume your testing integration validate own output enable drive with open eyes community end reduce stress transparency involvement game milestones attract show progress to latest first always have new & a client update learn noteworthy validatecomponent early incremental API centric planning first retrospectives enable explore dynamic built to validate teams last24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 27
  25. 25. Testing• Innovate with confidence• Tests run after each build• Test kinds Testing – correctness tests Defects • assert correct behavior – performance tests • assert no performance regressions – based on a database of previous test run measurements Kent Beck – JUnit handbook – resource tests, leak tests • assert no resource consumption regressions
  26. 26. Agenda• A quick introduction to Eclipse• Eclipse Open Source Engineering Processes• Open Source Business 101• The Open Source Maturity Model24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 34
  27. 27. Why?• Do any of these matter to your organization? – Cost – Time to market – Agility – Innovation – Industry standards and platforms – Safety – Security24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 35
  28. 28. Software Matters to Your Business24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 36
  29. 29. The avionics software beginnings • First significant use of software for avionics : the 80’s 12 M - A330/340 67 10000 68 4 volume (k.bytes) 2 M - A310 4 M - A320 69 1000 70 71 100 200k - A300FF 72 73 23k - A300B 10 74 23 4k 75© AIRBUS FRANCE S.A.S. Tous droits réservés. Document confidentiel. 1 76 65 77 70 75 80 85 90 95 78 Year 79
  30. 30. 90% of automotive innovations are realised by softwareMercedesS-ClassInfotainment 50 – 100Subsystem networked20 Mio. LOC 24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 ECUs 38
  31. 31. Why an Open Source Platform?• Open Source development model encourages open innovation – Openness, Transparency, Meritocracy – Vendor neutrality• Open Source licensing allows competitors to collaborate on shared platforms – No requirement for royalties. – No single control point of intellectual property• Open Source business model encourages rapid adoption of technology – It is free and easy to access• Open Source can allow companies to disrupt the business models of their competitors and their supply chain24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 39
  32. 32. The Traditional Software BusinessModel is Broken  Software development cost structures today have no correlation to creating value for customers  80% of new development and maintenance investment goes to build and support infrastructure for which companies derive zero differentiating product value Value Infra 24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 40
  33. 33. Compete On What Matters  Define very precisely what your competitive differentiators are for your customers or you’re going out of business  Focus all possible energies there, and acquire everything else from OSS, or help build it in OSS Value Build this in and with open source, even Infra if that means working with your direct competitors.24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 41
  34. 34. Or in other words… Value Compete on systems Infra Collaborate on the platform24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 42
  35. 35. Agenda• A quick introduction to Eclipse• Eclipse Open Source Engineering Processes• Open Source Business 101• The Open Source Maturity Model24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 44
  36. 36. Maturity Model VALUE APPROPRIATED VALUE CO-CREATION VALUE APPROPRIATION COUPLING MANAGEMENT 3 CHAMPION 2 CONTRIBUTE 1 USE 0 DENY TIME ENGINEERING DRIVEN BUSINESS DRIVEN SINGLE PROJECT SCOPE MULTIPLE PROJECT24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 45
  37. 37. ISV Business Drivers Use Contribute Champion Collaborate Redefine Explore Fill gaps in Champion OS Gain positional Change value feature set of project advantage for proposition of Reduce build company’s company’s offer delivered costs product Steer new product in a to customers functionality market Improve and its segment Decrease time to market software evolution quality24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 46
  38. 38. Enterprise Business Drivers Use Contribute Champion Collaborate Redefine Explore Fill gaps in Champion OS Create an Redefine the feature set of project industry relationship Reduce build company’s platform for with your costs product Steer new shared supply chain functionality infrastructure Decrease time Improve and its to market software evolution quality24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 47
  39. 39. Eclipse Moving Forward• How can we apply Eclipse best practices to building Industry platforms?• How to enable collaboration and innovation around a common platform?
  40. 40. Eclipse Industry Working Group• Provide a governance structure at Eclipse for industry collaborations and open innovation• Enable end-user centric collaborations• Open source projects continue to focus on building and shipping code
  41. 41. Eclipse Industry Working Group• Legal and licensing framework for sharing IP• Governance structure to ensure vendor neutrality• Best practices for large-scale distributed development• Technical architecture that allows of independent and shared innovation
  42. 42. Polarsys24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 54
  43. 43. Automotive IWG24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 55
  44. 44. Machine-to-Machine24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 56
  45. 45. Thank You! Questions? Ian.skerrett@eclipse.org @ianskerrett24-May-2012 Copyright (c) 2012, Eclipse Foundation, Inc. Made available under the Eclipse Public License 1.0 57

×