Published June 2018
Welcome to the seventh annual Eclipse Foundation Community Report. Comments and feedback on the style and content would be appreciated at email@example.com.
Except where noted this report will cover the period April 1, 2017 to March 31, 2018.
The Eclipse Foundation’s mission is summarized as follows:
The Eclipse Foundation’s purpose is to advance our open source software projects and to cultivate their communities and business ecosystems.
This makes the Eclipse community a unique open source community. Not only are we interested in building open source code and community, but we are equally committed to creating a commercially successful ecosystem around that code. This combination of interests has been a key part of Eclipse's success.
In short, our vision for the Eclipse community is
To be the leading community for individuals and organizations to collaborate on commercially-friendly open source.
The following are the strategic goals of the Eclipse Foundation for 2018, as established by the Board of Directors.
Over the past year, the Board has made a number of strategic decisions that will impact how Eclipse evolves in the future. A brief summary of these is listed below. More details can be found in the minutes of the Board, found on our website.
As of April 30, 2018, the Eclipse Foundation has twelve (12) strategic members, including CA Technologies, CEA List, Fujitsu, IBM, itemis AG, Obeo, Oracle, Payara Services, Red Hat, Robert Bosch GmBH, SAP, and Tomitribe.
Of note, the Eclipse Foundation also counts over 1500 committers. Committers are entitled to membership in the Foundation, and play a valuable role in the Eclipse Foundation governance, including representation on the Eclipse Board and many working group steering committees.
The Foundation finished 2017 with 270 member companies. By the end of April 2018, that number increased to 274 member companies. A total of 34 new companies joined as new members of the Foundation from May 1, 2017 through April 30, 2018, including
ADLINK Technology Inc., Astraea Inc, Baloise Holding AG, BTC Business Technology Consulting AG, Calypso Networks Association, Castalia Solutions, CloudBees Inc., Cloudera Inc, Contact Software GmbH, Enalean SAS, Fujitsu Limited, GFOSS - Open Technologies Alliance, Hazelcast Inc, InfluxData, JavaPro, JNBridge, LLC, Kynetics, Lightbend Inc, M3S Research Unit at the University of Oulu, Merantix GmbH, Mindus SARL, Nanjing Glaway Software Co. Ltd, Orange S.A., Pacific Northwest National Laboratory (PNNL), Paranor Engineering AG, PRFC, Skymind Inc., The University of York, toem GmbH, Tomitribe Corporation, TUEV SUED Auto Service GmbH, University of L' Aquila, University of Zagreb Faculty of Electrical Engineering and Computing (FER), V2COM.
The recruitment of new projects and members has been greatly assisted by the strategy of creating Eclipse working groups. As participation in working groups grows, our membership has grown and diversified into different industries such as automotive, aerospace, geospatial, and the Internet of Things.
Internet of Things (IoT) The Eclipse IoT Working Group is a community of organizations and individuals building open source technology that is used to build IoT solutions. Eclipse IoT has 34 different open source projects and 42 working group members. The technology portfolio include technology for embedded constrained devices, IoT gateways, and IoT cloud platforms.
New members of the Eclipse IoT Working Group in the past 12 months include: ADLINK Technology, Cloudera, CONTACT Software, DB Systel, InfluxData, Intel, Kichwa Coders, Nokia, Orange, SAP, V2COM
A number of new projects joined the Eclipse IoT community in the past year, including
In an effort to provide integrated “stacks” of IoT frameworks and runtimes, a new sub-committee of the IoT Working Group focusing on integration topics was formed at the end of 2017. It is tasked with facilitating cross-project communication and synchronization of the Eclipse IoT projects’ roadmaps and APIs.
The Eclipse IoT Working Group continues to undertake a number of community outreach and development programs, including the following:
LocationTech, hosted by the Eclipse Foundation, is a working group developing technologies with spatial awareness. Now in its fifth year, LocationTech includes 18 members and 13 projects. During the past 12 months, a number of major milestones were achieved, besides significant releases by a number of projects, a first simultaneous release was made.
Strategic members of the LocationTech working group include Boundless, IBM, Oracle, and Red Hat. Participant solutions members include: Astraea (joined as new member), Azavea, CCRi, OGC, Planet, RadiantSolutions, SensorUp, Terranado, and VividSolutions.
Alll key projects (LocationTech GeoWave, LocationTech GeoGig, LocationTech GeoTrellis, LocationTech GeoMesa and LocationTech JTS) were incorporated in the first LocationTech simultaneous release in November 2017.
LocationTech was prominently represented at FOSS4G Global 2017 in Boston, the largest global open geospatial conference. The working group and its members and projects were represented in all aspects of the program: talks, BOFs, workshops, code sprint, exhibition area, and B2B sessions. On a regional level, LocationTech co-organized with URISA the CalGIS 2017 conference in May in Oakland, in support of its members and community. A large part of the program was dedicated to featuring the various LocationTech projects.
The Science Working Group (SWG), hosted by the Eclipse Foundation, works to solve the problems of making science software interoperable and interchangeable. It was founded in June 2014 and is now in its third year of operation. The Science working group has grown to 15 members and 10 projects. This report covers the period from March 2016 to March 2017.
The group has the following members:
In its fourth year, the following projects joined the working group:
The group hosted an Unconference at EclipseCon France in June 2017 with a special workshop dedicated to the Eclipse January project. During the conference eight talks for the Science track were presented.
Also in October 2017, the group coordinated their annual common release for some of its projects. The aim was to make the working group more visible and ensure that some of the projects depending on each other were synchronized. A joint press statement was released by the Eclipse Foundation and Oak Ridge National Labs on the topic of the release.
At EclipseCon Europe 2017, Tracy Miranda gave an overview of the activities and projects of the Eclipse Science Working Group under the title “Science@Eclipse.” The group also participated in the Unconference prior to the conference.
In August 2017 the XACC project was featured in the Eclipse Newsletter.
The Eclipse Long-Term-Support Working Group has become inactive. It is the Foundation’s intention to dismantle the Eclipse Foundation hosted LTS infrastructure in the second quarter of 2018.
The Eclipse openMDM (measured data management) Working Group wants to foster and support an open and innovative ecosystem providing tools and systems, qualification kits, and adapters for standardized and vendor independent management of measurement data in accordance with the ASAM ODS standard.
Since May 2017, the openMDM working group has changed its development effort. The Eclipse Foundation has been tasked to contract a product manager as well as a standing development team funded by the working group. While a few IP issues and code refactoring was holding up the team, good progress has been made. Regular milestone releases are taking place and the working group is targeting a major release in the summer of 2018. The ASAM ODS based software stack is now tested by various German OEMs and product companies and is likely to go into productive environments in 2018.
openMDM technology is expected to become part of the Eclipse openADx initiative.
The PolarSys Working Group focuses on providing open source development solutions for Software and Systems Engineering. It has 25 members and 18 projects hosted on the PolarSys forge. New members in the period include Glaway Software, PRFC, Malardalen University and University of York.
During the past 12 months, PolarSys members continued to improve the PolarSys established solutions (Capella and Papyrus) with a focus on product management and usability. PolarSys participated to several conferences, including Incose Symposium, Models 2017, and Euroforum in order to promote these solutions.
Airbus submitted a new project, PolarSys libIMS, the reference implementations of a standard middleware that serves as a guide for interconnection of modules (software or hardware) with avionic test benches. Polarsys B612, the open source font designed for readability, received the Industry award from “L’Observeur du design” and was references by several font referencing websites. OpenCert and CHESS benefited from new efforts in the context of the AMASS european research project to create an open platform for safety assurance and certification processes.
During the year, PolarSys members dedicated some effort to improve SWTBot, and to start the definition of a PolarSys release train as a way to enable medium-term support (~3 years) for the PolarSys solutions.
This period was also the second year of operation of the Papyrus Industry Consortium, a PolarSys hosted industry consortium (IC) of 15 members dedicated to the advancement of the Papyrus ecosystem. The Papyrus IC sponsored exhibit booths at different conferences including EclipseCon France, Models 2017, EclipseCon Europe, and Euroforum. All the committees of the Papyrus IC were active this year including the Steering Committee, the Architecture Committee, the Product Management Committee, and the Research Committee. The Product Management Committee continued its effort to organize Papyrus Industry consortium Product Line and to design streamlined version of the Papyrus tool platform; the Papyrus for Information Modeling was improved, and the plans for Papyrus UML Light and Papyrus SysML were defined. Finally, the consortium decided to fund the support of UML2 to make sure that this foundation component is included in Eclipse Photon, and to ensure a transition to a management of this component by a larger part of the community.
In June 2017, PolarSys members created the Capella Industry Consortium to foster the development of the Capella ecosystem. The Capella IC has 6 members and welcomed Glaway Software, the first PolarSys member from Asia in January 2018. During the predio, the Capella IC participated to several events, including a Capella Day (co-located with EclipseCon France) as a launch event, Incose Symposium, Euroforum, and ERTS. The Capella IC also organized several webinars that attracted more than 350 participants from more than 130 organizations.
The Eclipse openPASS Working Group was initiated in August 2017 by three German car manufacturers: BMW, Daimler, and Volkswagen.
The rise of advanced driver assistance systems and partially automated driving functions leads to the need of virtual simulation to assess these systems and their effects. This especially refers, but is not limited, to safety effects in traffic. There are various methods and tools for prospective evaluation of safety systems with respect to traffic safety. Implementing the methodology by creating and maintaining the SIM@openPASS platform will support reliability and transparency of results obtained by simulation. The growing number, complexity, and variety of those vehicle functions make simulation an essential part in research, development, testing, public rating, and homologation and is thus, directly or indirectly, required by all stakeholders in vehicle safety, including manufacturers, suppliers, insurance companies, legislators, consumer advocates, academia.
The Eclipse openPASS Working Group is the driving force behind related development of core frameworks and modules. The Eclipse openPASS WG endeavors to make sure that openPASS related Eclipse projects are in line with external important developments. The goal is a broad availability of different modules.
Work on the related Eclipse simopenpass project started immediately after the creation of the working group and was mostly executed by the fourth founding member, the Munich based company ITK Engineering GmbH. While there are still issues with the existing code base, the car manufacturers have started installing and using the code base. A milestone release is now available, and development and contributions from various company continue.
For the future, we expect code consolidation and growth of the related ecosystem.
In January 2018, the German TÜV Süd joined the openPASS Working Group.
openPASS technology is expected to become part of the Eclipse openADx initiative.
The EclipseCon conferences, Eclipse Days, and DemoCamps are the primary events that the Eclipse Foundation supports to help foster the strong personal relationships in the community that only face-to-face contact can create. We highly encourage all Eclipse community members to participate in one or more of these events.
EclipseCon France was held in June 2017 and had 250 attendees. The conference returned to its original format as a full two-day event. The Unconference, always well attended at EclipseCon France, was held at a new location, and again was well attended. The conference was held during a significant heat wave in Toulouse, and was run at the same time as the annual Fête de la Musique festival that runs throughout Toulouse.
EclipseCon Europe celebrated its twelfth anniversary in October 2017, with 609 people in attendance. This event was co-located with the OSGi Community Event, and included a great collection of technical sessions, BoFs, the IoT Playground, and included a fascinating talk by Roberto Di Cosmo of INRIA about their project to build “a universal software knowledge base”. The conference also hosted a number of dedicated events, including the IoT Day, the CDT Summit, and Project Quality Day. Feedback from the conference from both attendees and sponsors continues to be very strong, with many stating this was the best EclipseCon conference yet.
The Eclipse Foundation’s fiscal year end is December 31. Our auditors are the firm Deloitte & Touche, LLP. The Eclipse Foundation is incorporated in the State of Delaware, USA as a 501(c)6 not-for-profit. Our headquarters are located in Ottawa, Canada. The Eclipse Foundation also has a wholly-owned German subsidiary, Eclipse Foundation Europe GmbH.
Membership renewals remained strong, and working group revenue and website advertising were both steady compared to 2016. The organization continues to be on a solid financial footing, and the migration of Java EE to the Eclipse Foundation represents an opportunity for new membership growth. The financial impact of strategic membership is always significant to the Foundation. We were pleased to have Fujitsu, Payara Services, and Tomitribe all join as strategic members in the first four months of 2018, largely due to their participation in the new Jakarta EE working group. This counterbalanced the impact of Ericsson changing their membership from Strategic to Solutions members, and Codenvy’s ceasing as a strategic member due to their acquisition by Red Hat in June, 2017.
Looking forward to 2018, the Board has approved a budget forecasting a $0.2M loss.
|In US $ millions||2014||2015||2016||2017||2018 Budget|
Eclipse Foundation Brand Evolution
Simultaneous Releases for both Science and LocationTech Working Groups
Ongoing Marketing Research
During the time period spanning April 1, 2017 to March 31, 2018, the Eclipse Foundation received 2,926 requests for intellectual property review and completed 2,499 reviews. This represents a massive spike in the demands made on the Eclipse IP Team over the previous period (1,933 and 1,894 respectively).
The Eclipse Intellectual Property Policy was updated in 2016 to include two types of IP Due Diligence for the third-party software used by open source projects hosted by the Eclipse Foundation. Type A Due Diligence involves a license certification only and Type B Due Diligence provides our traditional license certification, provenance check, and code scan for various sorts of anomalies. Prior to this change, project teams would have to wait until the full application of what we now call Type B Due Diligence was complete before issuing a release. Now, a project team can opt to push out a Type A release after having all of their third-party libraries license certified.
Project teams appear to be enthusiastically taking advantage of this new type of due diligence. The rate by which requests for Type B reviews arrive appears to have dropped somewhat over the last two reporting periods, but still remains very strong (the statistical trend is still upwards) while the adoption of Type A is spiking.
As of the end of March 2018, we have 59 projects using Type A IP Due Diligence. All new projects are being directed to employ Type A Due Diligence for all incubation releases and encouraged to defer the decision whether or not to switch to Type B (license certification, provenance check, and code scan) until graduation. There is, of course, no specific requirement to switch at graduation or ever, but we are actively encouraging project teams to defer the decision of whether or not to switch from Type A until at least that point.
The Eclipse IoT and Technology Top Level Project together accounted for more half of the intellectual property reviews initiated between April 1, 2017 and March 31, 2018. This aligns well with the rates of new project creation in those Top Level Projects (approximately 65% of all new projects created in in that time frame were created under Eclipse Technology and Eclipse IoT Top Level Projects).
As the primary incubator for new projects, it’s natural that the Eclipse Technology Top Level Project is the leading source of requests for intellectual property review. The breakdown by project shows a great deal more diversity than in previous years (while the Eclipse Technology Top Level Project accounts for most of the IP reviews, only two Eclipse Technology Projects are in the top top ten consumers).The Eclipse Keti (IoT) project stands out as the high consumer of intellectual property resources. The rapid growth of the IoT project space continues to translate into high individual project representation in the “top-ten” consumers of intellectual property resources.
In June 2017 the Eclipse community shipped Eclipse Oxygen, its twelfth annual simultaneous release. Including previous releases of the Eclipse Platform, this was the fourteenth release that was shipped on time, to the day. A total of 83 projects participated in the Oxygen simultaneous release. The release comprises 71 million lines of code produced by 283 committers from 46 member companies, with contributions from 417 non-committer contributors.
Six projects joined the Eclipse Photon Simultaneous Release: the Eclipse aCute and Eclipse TM4E projects add support for C# language and TextMate® grammars to the Eclipse IDE; the Eclipse RedDeer project adds new options for testing SWT and RCP applications; and the Eclipse Collections, EclipseLink, and Eclipse Yasson projects add new runtimes.
The project teams from Eclipse EGerrit, Eclipse Sphinx, Eclipse Orion, and Eclipse Subversive SVN Team Provider decided to drop out of the simultaneous release. Perhaps the biggest implication of this list of dropped projects is that it is no longer possible to provide out-of-the-box support for SVN. In practice, none of our packages include this support anyway, so developers who require that functionality must go to Eclipse Marketplace to add it; these developers will likely find an alternative such as SubClipse.
This predictable release schedule has been a key part of the Eclipse Community's success over the years, and is an important part of the success of the Eclipse ecosystem.
The number of proposals that we receive year-after-year is on an upward trend. We’re off to a very good start in 2018, having received 27 new project proposals in 2018Q1.
The following projects were proposed at the Eclipse Foundation in 2017:
Since 2013, the Foundation increased its collaboration with academics, researchers, and industries by participating in several European projects. The Foundation’s main objective in these projects is to help the consortium engaged in each project build an open source platform and community around their respective EU research project.
The positive side effects are
As of March, 2018, Eclipse Foundation Europe is a research partner in seven large European research projects.
Eclipse Foundation Europe also created a research consortium named GEMOC. This open and international initiative aims to coordinate and disseminate the research results regarding the support of the coordinated use of various modeling languages that will lead to the concept of the globalization of modeling languages.
Our number of committers grew past 1,500 in early 2018.
The EMO is committed to providing a robust and dependable server and software infrastructure, including professional support staff to assist projects and working groups in achieving their goals effectively and efficiently, as well as steadily improving services to the Eclipse committers and the projects they work on. Here is a sampling of some infrastructure metrics, plus some improvements we've put into place over the past year.
Back to the top