History 2001 - Initial eclipse Board of Stewards: Borland IBM Red Hat SuSE MERANT QNX

2. History • 2001 - Initial eclipse.org Board of Stewards: • Borland • IBM • Red Hat • SuSE • MERANT • QNX • Software Systems • Rational Software • TogetherSoft • Webgain

3. History • 2003 – 80+ members • 2004 – re-organized -> non-profit corporation • Full-time management organization established • Coordinate open source projects • Engage with open source community • 2006 – 5 year birthday • Primary IDE for non .NET development

4. Eclipse • Platform supporting: • Underlying needs of many different applications • A variety of active projects producing tools • Supporting entire application lifecycle

5. Eclipse Foundation • Organization: • Member funded • 115+ member companies • non-profit • supports Eclipse open source projects • development mentoring • marketing • support Eclipse community

6. Eclipse Foundation • Members: • Strategic Members • Add-in Provider Members • Associate Members • Committer Members

7. Eclipse Foundation • Members: • Strategic Members: • Companies view Eclipse as strategic platform • Invest financial & developer resources – develop Eclipse technology • Has representation on Eclipse Foundation Bd of Directors • Control strategic direction of Eclipse • Has representation on Eclipse Requirements Council • Input/influence over themes & priorities of Eclipse technology

8. Eclipse Foundation • Members: • Strategic Members: • a. Strategic Consumer – major user of Eclipse tech • b. Strategic Developer – major developer of Eclipse tech

9. Eclipse Foundation • Members: • Strategic Members: • a. Strategic Consumer – major user of Eclipse tech • Annual dues 0.2% of revenue (min $50, max $500K)

10. Eclipse Foundation • Members: • Strategic Members: • b. Strategic Developer – major developer of Eclipse tech • Contribute at least 8 full-time developers • Annual dues 0.12% of revenue (max $250K) • Lead one+ Eclipse Project(s) • Has representation on Eclipse Planning and Arch Council • Direct input – development/architecture of Eclipse

11. Eclipse Foundation • Members: • 2. Add-in Provider Members: • Companies view Eclipse as important part of their Corp/product strategy • Development of Eclipse ecosystem • Must have an Eclipse based offering avail within 12 months of joining. • Required to publicly announce their support for Eclipse • Annual dues - $5000

12. Eclipse Foundation • Members: • Associate Members: • Non-profit organizations • Standards body • Research institute • University • Publisher • Participate in development of Eclipse Ecosystem • Dues – none required • Can submit requirements • Participate in project reviews & membership meetings

13. Eclipse Foundation • Members: • Committer Members: • Must be a Committer: • developer of Eclipse open source • Volunteered/contributed by organizations/individuals • Core developers of Eclipse technology • Can commit changes to source code • May vote for Committer Representatives on Eclipse Bd of Directors

14. Eclipse Ecosystem • Comprised of: • Major technology vendors • Innovative start-ups • Research institutions • Universities • Individuals • Support & extend Eclipse platform

15. Eclipse Open Source Projects • More than 60 • Main Categories: • Enterprise Development • Embedded and Device Development • Rich Client Platform • Rich Internet Applications • Application Frameworks • Application Lifecycle Management (ALM) • Service Oriented Architecture (SOA)

16. Eclipse Platform • Developed: • by open source developers • in Java

17. Eclipse Platform • Deployed on: • Linux • HP-UX • AIX • Solaris • QNX • MAC OS X • Windows based systems

18. Eclipse Platform • provides plug-in based framework • to benefit software providers & end-user • seamless movement between diff tools • easier to create, integrate, & utilize SW tools • saves $ and time

19. Eclipse Platform • Foundation for: • building development environments • building arbitrary tools and applications • (RCP) Rich Client Platform component • used to build arbitrary applications for banking, medial, automotive, and space exploration.

20. Evaluation • Signs they are meeting their goals: • Primary IDE after 5 years • Growing member count (115) • Growing projects count (60) • Corp support – strength • Appear well organized

21. Evaluation • Improvements that could be made: • add clarity for new-comers

22. References: Eclipse Foundation, The. (2007). About us. Retrieved April 3, 2007, from http://www.eclipse.org/org/ Eclipse Foundation, The. (2007). Become a member. Retrieved April 3, 2007, from http://www.eclipse.org/membership/become_a_member/ Eclipse Foundation, The. (2007). Eclipse Foundation Community Awards Announcement: Eclipse Community Awards Winners Announced: Awards Recognize Top Individuals and Technologies in the Eclipse Community. Retrieved April 3, 2007, from http://www.eclipse.org/org/press-release/20070306eclipsecommunityawards.php Eclipse Foundation, The. (2007). Eclipse logos and artwork for members and providers. Retrieved April 3, 2007, from http://www.eclipse.org/artwork/index.php Eclipse Foundation, The. (2007). Eclipse Newcomers FAQ. Retrieved April 3, 2007, from http://www.eclipse.org/home/newcomers.php Eclipse Foundation, The. (2007). Eclipse Platform Overview. Retrieved April 3, 2007, from http://www.eclipse.org/platform/overview.php International Business Machines Corp. (2006). Eclipse Platform Technical Overview. Retrieved April 3, 2007, from http://www.eclipse.org/articles/Whitepaper-Platform-3.1/eclipse-platform-whitepaper.pdf Varhol, P. (2007). Pay attention to eclipse: The technologies being developed under the eclipse umbrella have implications far beyond Java development. [electronic version]. Redmond magazine. Retrieved April 3, 2007, from http://reddevnews.com/columns/article.aspx?editorialsid=1701