Life at Eclipse

Musings on the Eclipse Foundation, the community and the ecosystem

Archive for the ‘Foundation’ Category

One Big Step for EclipseRT

The future of Java technology in the enterprise rests with its rapidly evolving ability to regain its original promise of lightweight, flexible and dynamic application development and deployment. In other words, the faster Java gets to the stackless stack, the brighter its future will be. As James Governor said in his seminal article, “component-based development is a common idea, but component-based production is a whole different ballgame.” That has been the vision of the EclipseRT project since its inception: the ability to support deployed runtimes which use only those components actually required by the applications at hand. This is an inherently service-based approach, and one which has seen rapid adoption by enterprise Java and Enterprise Service Bus vendors.

SpringSource has long been one of the most visible and vocal leaders of lightweight, componentized Java runtimes. Today, they bring that leadership to Eclipse. The Virgo project proposal brings to EclipseRT project a key component (no pun intended) required to provide a complete offering of OSGi-based runtimes from the Eclipse Foundation: a complete module-based Java application server designed to run enterprise Java applications. Based on SpringSource’s dm Server, we believe this project will increase the momentum of the enterprise Java developer community under the Eclipse umbrella.

The past couple of years, “establish Eclipse runtime technology as the leading open source runtime platform” has been on the top of the list of the strategic goals of the Eclipse Foundation. The recently announced Gemini project — and now Virgo — go a long way towards realizing that vision.

You can read more about Virgo on Adrian Colyer’s blog post.

[Revised to fix broken link to Adrian’s post.]

Written by Mike Milinkovich

January 12, 2010 at 9:16 am

Posted in Foundation, Open Source

It’s a Dessert Topping and a Floor Wax

Last week we saw probably more conversation than any of us wanted about the notion that Eclipse is a trade association and therefore not an open source community. I believe that perspective to be misguided as it implies those two states are somehow mutually exclusive. They are not. And it is our community’s embrace of both that makes Eclipse unique.

The Eclipse Foundation is and always will be a trade association. It is also and always will be an open source community. This duality is built into our bylaws, our organization and, I would assert, our DNA. Consider the following sentence from the first paragraph of our Bylaws:

The purpose of Eclipse Foundation Inc., (the “Eclipse Foundation”), is to advance the creation, evolution, promotion, and support of the Eclipse Platform and to cultivate both an open source community and an ecosystem of complementary products, capabilities, and services.

That sentence captures the very essence of the Eclipse Foundation. Our mission is to both move the technology and community forward and to work on its commercialization. The “trade association” of member companies financially support the operations of the Eclipse Foundation. Over 70 of them also provide committers who work on projects. There are relatively few obligations that an Eclipse member company undertakes when they sign the membership agreement, but one of the most important is to create a commercial offering based on Eclipse technologies. It is that obligation which completes the loop from open source to commercialization to trade association and back. Those trade association members are not strangers: they are companies that are intimately involved in and committed to the success of the entire Eclipse community.

There is no doubt that the focus on commercialization places added burdens on Eclipse projects. Our development and IP processes require real work to comply with. But there is value in that labour, and the value is in the added use, adoption, commercialization and plain old respect that the Eclipse brand brings to a project. Not every Eclipse-based open source project needs to be hosted at the Foundation. For some projects, our processes may be too heavyweight. But those projects are still a valuable part of the broader Eclipse ecosystem.

The Eclipse community is also an open development community. I strongly believe that our development process has all of the attributes of openness, transparency and meritocracy that open development requires. Our unique approach to open source development is what enables things like the annual release train, which is arguably the best run, most predictable feat of software engineering on the planet. And let’s not forget that although many projects at Eclipse are supported by developers working at member companies, there are many also projects with active participants who are here as individuals.

But there is also no denying that we have our challenges. Every project would love to have more resources and more community involvement. We need to make it easier for newcomers to contribute. There are projects who frankly don’t do a great job of welcoming contributions. We have to attract more resources committed to evolving the core platform. We have a major new release of the platform coming next year. The staff and the Board of the Eclipse Foundation recognize all of these challenges and are working very hard to address them.

The balance between a trade association and an open source community makes Eclipse unique in the software industry. We have always been both, and that has always been an important part of our success. We are different, and in my mind that is a very good thing. I believe that we should all be very proud of the organization that we have created.

Written by Mike Milinkovich

December 11, 2009 at 10:21 am

Posted in Foundation, Strategy

Membership Value Programs for 2010

Monday I blogged about some of the program plans we have for 2010 that are targeted at our project and committer community. Today, let’s turn to some of the things that we have in store for our members and the commercial ecosystem around Eclipse. Not all of these are new, but in each case there is significant value to the community, and there are at least a few new twists that we have planned for 2010.

  • Events: First of all, we are going to be continuing with the program items which have been very successful for the community the past couple of years. Amongst the most successful are the event programs that deliver the Eclipse Days and the Democamps. You may not be aware of this, but each of these events is sponsored in part by the Eclipse Foundation, in conjunction with one or more member companies. They have been enormously successful for bringing the community together, and in delivering value to members. For next year we are planning Democamp programs that line up with the Helios and e4 releases. And we hope to work with the members to bring even more topical Eclipse Days to your locale.
  • Conferences: EclipseCon and Eclipse Summit Europe are significant events in the annual calendars of the ecosystem. Although the content is very technical, a great deal of the talks are relevant to Eclipse users and adopters. The exhibit halls are also a great place for companies to show the cool products that they’ve been building with Eclipse. Running these conferences is a huge amount of work for a small organization such as the Eclipse Foundation, but they do great things for the ecosystem.
  • Eclipse Marketplace: As Ian blogged about yesterday, this week saw the launch of our new “Eclipse Marketplace”. This is a completely new replacement for the venerable Eclipse Plug-in Central (EPIC) website that has served the community well for so many years. Marketplace is a new code base with more features and more flexibility. (As an aside, I would like to recognize the great work that Genuitec, Instantiations and EclipseSource (formerly Innoopract) did in creating EPIC, and then helping us with transitioning its hosting to the Eclipse Foundation.) In 2010 we are going to be looking to expand Marketplace’s visibility in a couple of interesting ways:
    • We are going to be creating a Marketplace client that will ship with the Helios packages. The hope is that by making it easy to get plug-ins directly from within the IDE that will be able to drive more traffic to the commercial and open source plug-ins which make up the Eclipse ecosystem. Please comment on the bug where we are gathering requirements.
    • We are going to be working to make it easier for users and adopters to find products and services which are based on particular Eclipse projects. Using the data that we will have in Marketplace you will, for example, be able to find the companies that offer services for a particular Eclipse project.

    By the way, if you just read the above and are thinking “that’s lame, where’s the Eclipse AppStore?” you are not alone. We looked long and hard at doing an appstore in 2010 but in the end decided that we just did not have the resources. It turns out that while building the infrastructure for a commercial appstore may be tractable for an organization as small as the Eclipse Foundation, dealing with the legal and tax issues of selling in countries around the world is not. We will be re-evaluating this decision again next year.

  • Ship Helios and e4: Many readers may be surprised to see this topic listed under the program value for the commercial membership. After all, aren’t these Eclipse open source projects? They are indeed. But in terms of the value that the Eclipse Foundation brings to its commercial membership, these major new releases represent a lot of marketing, IT and IP value add from the Foundation staff. The annual release train brings enormous value to the commercial ecosystem because it provides them with a stable, predictable and IP reviewed platform each year upon which products can be built. The release train has been enormously beneficial to the commercial ecosystem. Obviously, most of the work is done by the project community. But it also represents the single largest work item on our annual calendar at the Eclipse Foundation.

So those are a few areas that the Foundation staff will be working on next year. I hope you agree that it looks like a busy and productive year coming up in 2010.

Written by Mike Milinkovich

December 9, 2009 at 4:28 pm

Posted in Foundation, Strategy

This Week’s Announcements

Hearty congratulations are due to Microsoft, Soyatec and Tasktop for their announcements yesterday regarding Eclipse and Silverlight, Azure and Windows 7. It is great to see Microsoft providing support to the ecosystem to ensure Eclipse remains a great development environment for the Windows platform (which still represents almost 80% of our users on any given day).

Much of this progress results from work led by Vijay Rajagopalan, a Principal Architect in the Interoperability Technical Strategy team at Microsoft. Vijay has been working closely with the Eclipse Foundation since just before EclipseCon 2009 and we’re very happy with the progress we’ve made.

Written by Mike Milinkovich

October 29, 2009 at 10:54 am

Posted in Foundation

Welcome to the EPL

A bit of good news for the Eclipse Public License this morning comes from Intuit, which announced that their community site code.intuit.com will be using the EPL.

Intuit had previously decided to use the Common Public License, but when we pointed out that it had been superseded at the OSI by the EPL, they agreed that it made sense to go with the EPL. It turns out that some of the links and pages at the OSI had not yet been updated, and thanks goes to Russ Nelson for fixing those quickly!

All-in-all a good outcome for the EPL. It’s great to see the increasing adoption of our license by the broader open source community. It is now the license used by the Topcased and Symbian communities as well as a growing number of projects on code.google.com and sourceforge.

Written by Mike Milinkovich

August 6, 2009 at 12:00 pm

Posted in Foundation, Open Source