Life at Eclipse

Musings on the Eclipse Foundation, the community and the ecosystem

Archive for the ‘Open Source’ Category

An update on the Eclipse Foundation’s move to Europe

In May we announced that the Eclipse Foundation is becoming a Belgian international nonprofit association. I wanted to take this opportunity to provide you with an update on the progress of the transition, the next steps, and what it all means to our global community of developers and diverse membership base.

Let’s start with where we are in the process. At time of writing, all of the incorporation and related documents have been filed with the Belgian authorities, and we are waiting for the Royal Decree which will formally create our new entity, the Eclipse Foundation AISBL. This normally takes on the order of sixty days and we expect the process to be finalized by early-to-mid October.

In parallel, the Board of Directors of the Eclipse Foundation, Inc. have approved a series of changes to the Bylaws and Membership Agreement of the existing Delaware, USA-based entity and we will be seeking the approval of the membership-at-large for those changes. To our members and committers, please stay tuned for your voting credentials in late August. In addition, some revisions have been made to our IP Policy and Antitrust Policy to enable both our US and Belgian entities to have exactly the same policies.

Once the new Belgian entity Eclipse Foundation AISBL is created and the approvals are finalized to the Eclipse Foundation, Inc.’s Bylaws and Membership Agreement, all members will be required to update their Membership Agreement and related other agreements. You will be asked to join Eclipse Foundation AISBL, and to resign your membership in the existing US organization. At the same time, we will be asking you to re-sign your Member Committer and Contribution Agreement (MCCA) and any Working Group Participation Agreements.

So exactly what’s changing?

As part of moving to European-based governance, effective October 1st we will be restating our membership dues for both the Belgian-based Eclipse Foundation AISBL and the existing Eclipse Foundation, Inc. in euros while retaining the same numeric value. So if you are currently paying $20,000, the dues in the new organization will be 20.000€. We understand that due to currency exchange rates this represents an increase in  dues. To help mitigate that, all members who renew between October 1, 2020 and September 30, 2021 will have their euro-based membership fees discounted by 10%. This modest increase is the first fee increase we have had in almost 15 years, and we hope that members appreciate the merit of stating all fees in euros as we complete this transition.

As part of the European transition, we are changing the name of the Solutions Members membership level to Contributing Members. We feel that this will better reflect the current, diverse group of organizations who participate and contribute to the Eclipse ecosystem in many ways, including, but not limited to, leading and contributing to our open source projects, and offering products and services based on Eclipse Foundation technologies.

Working Group Participation Agreements (WGPAs) will be updated to reflect the change of the corporate domicile to Belgium, as will the working group charters once approved by the respective Steering Committees. There are no fee changes to any working group participation associated with this transition, though some working groups may decide to restate their fees in Euros at some point in the future, similar to membership fees. As always, the budgets and fees established for each working group are determined by the Steering Committee of the working group.

For our committers, if you are an individual Committer Member you will be asked to execute the new Belgian Membership Agreement. If you have previously executed a committer agreement with the Eclipse Foundation as an individual, then you will need to re-execute the new version of the Individual Contributor Agreement.

For committers who are employees or consultants of a member company who has a Member Committer and Contributor Agreement (MCCA), your employer will be asked to execute the new MCCA, and no actions will be required on your part.

Our new GitLab-based forge physically hosted in Europe is operational and available as a choice for any projects that would like to use it. As we expand our presence in Europe, we anticipate new exciting opportunities for our global community members to participate and contribute in new open source projects. More announcements on this front will be coming soon.

What’s staying the same?

As far as day-to-day interactions with the Eclipse Foundation, nothing will change for member organizations or committer members. Our projects and working groups will continue to run as is, and the recently modified IP Policy and Antitrust Policy of the Eclipse Foundation AISBL are identical to those of the US organization. Eclipse Foundation AISBL will become the steward of the Eclipse Public License and govern our community’s license going forward. The bulk of the Foundation’s operations will continue to be split between Europe and Canada, and you can expect your engagement with the staff of the Foundation to remain unchanged.

When is this all happening?

There are a lot of moving parts with this corporate restructuring, and we ask in advance for both your patience and your active engagement and support. Here are some upcoming key dates that members and committers need to be aware of:

  • August 31, 2020: Voting begins on approving the necessary changes to the Eclipse Foundation, Inc. (EF-US) Bylaws and Membership Agreement. Voting will go until September 29th. The new EF-US Bylaws and Membership Agreement will go into effect as soon as practicable after the completion of the membership vote.
  • October 1, 2020: The new dues structure stated in euros will go into effect. Renewals for existing members will receive a 10% discount for the following twelve months.
  • Soon after the Royal Decree which legally establishes the Eclipse Foundation AISBL we will be contacting all of our members and committers to update their agreements with the new Belgian entity. This may include your membership agreement, committer agreements, and working group participation agreements as applicable.

I hope that this post has helped update you on the execution of the transition and the way forward for the next exciting phase of our community’s expansion. If you have questions or feedback, feel free to reach out to me, or to our team at eclipse-europe@eclipse.org. Thank you for your continued support!

 

Written by Mike Milinkovich

August 20, 2020 at 6:03 am

Jakarta EE Is Taking Off

With the results of the 2020 Jakarta EE survey and the initial milestone release of the Jakarta EE 9, it’s clear the community’s collective efforts are resonating with the global Java ecosystem.

Before I get to the survey results, I want to say a huge thank you to everyone who took the time to participate in the survey. We received nearly 2,200 responses from software developers, architects, and decision-makers around the world — an increase of almost 20 percent over last year’s survey. With your insight, we’ve gained a clear and comprehensive view of enterprise Java strategies and priorities globally, which in turn we are freely sharing with the ecosystem.

Jakarta EE Adoption and Compatible Implementations Are on the Rise

Less than a year after its initial release, Jakarta EE has emerged as the second-place cloud native framework with 35 percent of respondents saying they use it. While the Spring and Spring Boot frameworks are still the leading choices for building cloud native applications, their usage share dropped 13 percent to 44 percent in the 2020 survey results.

Combined, Java EE 8 and Jakarta EE 8 hit the mainstream with 55 percent adoption. Jakarta EE 8 was responsible for 17 percent of that usage, despite only shipping for the first time in September 2019. This is truly significant growth.

We’re also seeing a strong uptick in Jakarta EE 8 compatible products. Companies including IBM, Red Hat, Payara, Primeton, TmaxSoft, and Apusic now have Jakarta EE 8 Full Platform compatible products. Since January 2020, we’ve had four new Full Platform compatible implementations and one new Web Profile compatible implementation. In addition to Eclipse GlassFish 5.1, this brings Jakarta EE 8 adoption to 12 compatible products. This is an outstanding achievement for the Jakarta EE community to have more full platform compatible products in 8 months than Java EE 8 had in over 2 years. You can see the complete list here.

You can also expect to see additional compatible implementations in the coming months as more applications are passing Technology Compatibility Kit (TCK) tests and are well on their way to becoming certified as Jakarta EE 8-compatible products.

Architectural Approaches Are Evolving

This year’s Jakarta EE survey also showed a slight drop in the popularity of using a microservices architecture for implementing Java systems in the cloud compared to last year. At the same time, use of monolithic architectures for implementing Java systems in the cloud nearly doubled since last year’s survey and is now at 25 percent.

These results may indicate that companies are pragmatically choosing to simply “lift and shift” existing applications to the cloud instead of rearchitecting them as microservices.

Interestingly, the survey also indicated the Jakarta EE community would like to see better support for microservices in the platform. When you combine this fact with the rise of Jakarta EE, it’s reasonable to believe developers may be starting to favor vendor-neutral standards for building Java microservices over single-vendor microservices frameworks.

The Industry Is Moving to the New Jakarta EE Namespace

The support we’re seeing for the adoption of the new namespace in Jakarta EE 9 reinforces the value the industry sees in Jakarta EE. Technology leaders are already investing to ensure their software supports the Jakarta EE 9 namespace changes and others have indicated they will do the same. Some of these implementations include:

  • Eclipse GlassFish 6.0 milestone release is available to download
  • Jetty 11.0.0-alpha0 milestone release is available to download
  • Apache Tomcat 10.0 M6 milestone release is available to download
  • Payara Platform 6 milestone release coming in Q4 2020
  • OpenLiberty 20.0.0.7 Beta release is available with basic Web application support to download
  • Apache TomEE 9.0 milestone release using Eclipse Transformer project tools is available to download
  • WildFly 21 is planning a milestone release for fall 2020
  • Piranha Micro p20.6.1 milestone release is available to download.

While the Jakarta EE 9 tooling release doesn’t include new features, it’s a very important and necessary step on the road to Jakarta EE 10 and the next era of innovation using cloud native technologies for Java. With the full Jakarta EE 9 release in fall this year, Jakarta EE will be ideally positioned to drive true open source, cloud native innovation using Java.

Diversity, Achieved

One of the items that I am particularly happy about is the achievement of establishing Jakarta EE as a vendor-neutral, community-led technology platform. When we started the process of moving Java EE from Oracle to the Eclipse Foundation there were some who doubted that it could be accomplished successfully. The numbers tell the story: Oracle’s contributions are still leading the pack at 27%, but the community-at-large is

JakartEEDev v2
now over 40%. Contributions from our other members are led by Payara, VMware (Pivotal), Red Hat, and IBM. Based on these results, it is clear that Jakarta EE has truly achieved its original objective of becoming a vendor-neutral, community-led industry initiative. A lot of people worked very hard to achieve this, and I’m thrilled by the results.

Discover Jakarta EE

Here are three ways to learn more about Jakarta EE and understand why it’s gaining mainstream adoption so quickly:

  • Join the community at the Jakarta EE 9 Milestone Release Virtual Party and networking opportunity on Tuesday, June 23 at 11:00 a.m. EDT. To register for the event, click here.
  • Find out more about the Jakarta EE 9 milestone release here.
  • Review the complete 2020 Jakarta EE Survey results here.

Edit: Reflect IBM’s contributions
Edit #2: Add link to Apache TomEE download

Written by Mike Milinkovich

June 23, 2020 at 7:03 am

The Eclipse Foundation Is Moving to Europe

Today we are announcing that the Eclipse Foundation is transitioning itself to become a European-based organization, specifically a Belgian international nonprofit association. I wanted to take this opportunity to share with you our plans for the transition and what the announcement means to our community.

Let’s begin with some context. The first quarter of 2020 was the most successful in our organization’s history, as measured by the addition of 40 new member companies, five new working groups, and 11 new project proposals. Over the last few years, our community has expanded to create new projects in technology areas such as cloud and edge applications, IoT, artificial intelligence, digital ledger technologies, open processor designs, and many others. Combined with our roots in Java, tooling and rich client platforms, and modeling, this has made Eclipse Foundation the home of an incredibly diverse range of exciting, commercially-focused open source technologies.

Our goal is to continue this growth and diversification, and to continue to establish the Eclipse Foundation as an institution enabling global open collaboration and innovation. We believe that this strategy makes the Foundation, and by extension your investments in our open source projects, more secure and sustainable.

We believe this “move to Europe” is the most effective way for us to achieve this goal.   The reason is straightforward – while we support a diverse, international ecosystem, most of our growth has already been happening in Europe. With 170 of our member organizations and more than 900 of our committers based in Europe, the Eclipse Foundation is, by those measures and others, already the largest open source organization in Europe.

Which brings me to today’s announcement. By creating the Eclipse Foundation AISBL, an international non-profit association based in Brussels, we are furthering our vision of the Eclipse Foundation as a global institution that builds on our existing membership base, active developer community, and strong institutional relationships to enable the free flow of open software innovation. We believe that our transition to Europe will help to advance toward this goal, for the benefit of industries and developer communities worldwide.

Here are the highlights of our action plan:

  • We expect to create the Belgian international non-profit association by July 2020.
  • In parallel, we will establish a modern open source project development forge based on GitLab and physically hosted in Europe. We expect the forge to be operational this summer. This will provide our projects and committers a third option for their development forge.
  • The Eclipse and Eclipse Foundation names, trademarks, and brands will be controlled by the new Belgian entity, as will the core policies such as antitrust and intellectual property. Going forward our membership dues will be stated in euros.
  • The Eclipse Foundation, while currently a USA incorporated not-for-profit organization, already manages its operations split between Canada and Europe, so there will be minimal to no impact to the Foundation’s operations.

So, what does this move mean for our members? For our corporate members, there is no immediate change.  Our projects and working groups will continue operating exactly as they are.  Once we have the Belgian entity up and operating, we will reach out to you with more details, but do expect your engagement with the Foundation to remain largely unchanged.

To our Committer members, as well as our project committers and contributors, the message is two-fold. First, thank you for your commitment and participation. Second, keep doing what you’re doing. In the near-term, it will be “business as usual” for committers and contributors of Eclipse projects. In the medium term, we are standing up a new GitLab-based forge physically hosted in Europe that will be available as a choice for any projects that would like to use it.

And, critically important as it is the main driver for the move, as we expand our presence in Europe, we anticipate new opportunities for our global community members to participate in innovative new open source projects.

Read the full text of the announcement here. Additional resources and information on the Eclipse Foundation’s plans and how interested parties can get involved at eclipse.org/europe. Resources include:

I hope that this has helped clarify our motivations and the way forward for the next exciting phase of our community’s expansion. More details will follow over the coming weeks as we quickly execute on these plans, but if you have questions in the interim, feel free to reach out to me, or to our team at eclipse-europe@eclipse.org.

I look forward to this exciting next chapter together – thank you for your continued support!

 

Written by Mike Milinkovich

May 12, 2020 at 4:00 am

Posted in Foundation, Open Source

The 2020 IoT Developer Survey Goes to the Edge

Our 2020 IoT Developer Survey is open until June 26, and for the first time, the survey includes questions about how developers are incorporating edge computing technologies into their IoT solutions.

With your input, everyone in the IoT ecosystem — original equipment manufacturers (OEMs), software vendors, hardware manufacturers, service providers, enterprises of all sizes, and individual developers — will have a better understanding of the latest IoT solutions and service development trends and how these trends impact their strategies and businesses.

Completing the survey also gives you a unique opportunity to influence the roadmaps of the Eclipse IoT Working Group and the Eclipse Edge Native Working Group. IoT and edge technologies are intrinsically intertwined, and your choices for development tools, architectures, deployment technologies, security, connectivity, and other aspects will help ensure our working groups continue to focus on your top priorities and requirements for cloud-to-edge IoT solution development.

This is the sixth year for the IoT Developer Survey, and every year the survey results provide valuable insight into the requirements, priorities, and perceptions in active IoT developer communities. In 2019, we received more than 1,700 survey responses, including more than 1,100 responses from developers who were working on IoT projects in a professional capacity — a clear indication the IoT ecosystem recognizes the value of the survey results.

With your input, we were able to identify relevant IoT technologies, leading architectures, applications, and standards on a global scale. The 2019 survey also revealed that IoT development is expanding at a rapid pace, fueled predominantly by increasing investments in industrial markets. The results highlighted developers’ focus on IoT platforms, home automation, and industrial automation.

The IoT Developer Survey is distinct from, but complementary to, our IoT Commercial Adoption Survey. The IoT Commercial Adoption Survey goes beyond the developer perspective to find out what organizations are doing with IoT and their plans for production deployments. With the results from this survey, stakeholders including software vendors, IoT platform vendors, IoT solution providers, and manufacturing organizations gain critical insight into the right next steps for their businesses.

Take a Few Minutes to Complete the IoT Developer Survey

The IoT Developer Survey is the IoT industry’s largest developer survey and I encourage all developers in the IoT ecosystem to add their voice. It takes less than 10 minutes to complete.

You can access the survey here.

Written by Mike Milinkovich

May 11, 2020 at 8:30 am

Posted in Foundation, Open Source

Eclipse Theia and VS Code Differences Explained

After we announced the release of Eclipse Theia 1.0 and published a blog about it, we received a number of questions about the differences between Theia and Visual Studio (VS) Code and why we’re calling Theia “a true open source alternative” to VS Code. Here are some clarifications I hope will help people understand the differences between the two and the value of Theia.

In the Words of Microsoft

I want to emphasize that VS Code is a great product that is loved by many developers. This is the primary reason Theia adopted many of the VS Code user experience features.

But, VS Code is not truly open source. Microsoft explains it well in their VS Code FAQ: “…it is more accurate to say that Visual Studio Code is “built” on open source, rather than “is” open source…”

Purpose

The first thing to understand is that, at least for this release, Theia is not intended to be a tool that developers download and use directly. There isn’t even a developer tool download available from the Theia project.

Theia 1.0 is intended as a production-ready platform that any company (e.g. ARM, D-Wave, Gitpod, Google, Red Hat) or community (e.g. Arduino) who wants to provide their adopters with a modern developer experience can build from. The easiest way to see Theia in action is to try products such gitpod.io, or Red Hat Code Ready Workspaces, or ARM’s mbed Studio.

Licensing and Data Collection

Eclipse Theia is built, distributed, and used under the Eclipse Public License, a commercial-friendly open source license approved by the Open Source Initiative.

The VS Code repository on GitHub includes code that is licensed by MIT, but the VS Code distribution is released under a proprietary Microsoft product license. For most developers this is not an issue, as the tool is free, as in free beer. However, this approach means that it is difficult for companies and communities other than Microsoft to use VS Code in their own products. They require an open source platform which is free, as in freedom.

The Microsoft VS Code license also indicates the software may collect information about how the software is used and who is using it, and then send that data to Microsoft. The license makes it clear you can opt out of many telemetry data collection scenarios, but not all.

Vendor Neutrality

Eclipse Theia is freely available to everyone who wants to use it. There are no obligations to, or dependencies on, any company that has contributed to the code base or that uses it.

VS Code is a Microsoft product that is largely developed as open source, but is controlled by Microsoft. Anyone who relies on VS Code is then dependent on the future investment of Microsoft to continue supporting on-going development of the product. Theia is one of the most active and diverse projects at the Eclipse Foundation with steady contributions from ARM, Ericsson, Red Hat, SAP, TypeFox, and others.

Architecture

Theia builds on top of many of the core open source pieces of VS Code such as the Monaco editor, the extension model, Language Server Protocol and the Debug Adapter Protocol. But Theia and VS Code are architecturally different in two main ways:

  • Eclipse Theia allows developers to create desktop and cloud IDEs using a single, open source technology stack. Microsoft now offers VS Online for cloud development environments, but like VS Code, it cannot be used in open source initiatives such as Gitpod.
  • Eclipse Theia allows developers to customize every aspect of the IDE without forking or patching the code. This means they can easily use Theia as a base to develop desktop and cloud IDEs that are fully tailored for the needs of internal company projects or for commercial resale as a branded product. VS Code is a developer IDE only. It was never intended to be used as the base for other IDEs, extended, or further distributed.

Extensions

Theia uses the same extension model as VS Code, so any extension that works with VS Code will work with Theia. Unfortunately, the terms of use for the Microsoft Marketplace can only be accessed from Microsoft products. Because of that, Theia uses the open source extensions in the vendor-neutral Eclipse Open VSX marketplace. These extensions can be used by anyone, with no restrictions, whether they’re developing in Theia or in VS Code. Better yet, the code that implements the Open VSX marketplace is open source, and enabling self-hosted repositories within your organization is one of the stated goals of the project.

Get More Information

For more insight into the differences between Eclipse Theia and VS Code, read the Jaxenter interview with Theia project co-lead, Sven Efftinge.

To learn more about Theia and start using it, visit the website.

Written by Mike Milinkovich

May 5, 2020 at 9:00 am

Posted in Open Source