Discover the Embedded Cloud DevTools Special Interest Group
Brian King, the Cloud DevTools community manager at the Eclipse Foundation, explains why the Eclipse Cloud DevTools Working Group has created the Foundation’s first special interest group (SIG), who is involved, and what they hope to achieve.
Q. What drove the need for a special interest group (SIG) within the Eclipse Cloud DevTools Working Group?
A. Over the last year or two, we received numerous inquiries about cloud development tools from embedded tool vendors. Most of these vendors are still invested in traditional desktop tools, such as the Eclipse IDE, but they’re exploring their strategy and their entry point to cloud development for embedded software.
We saw a fantastic opportunity to bring these organizations together as a special interest group (SIG) to collaborate on technical initiatives within the Cloud DevTools working group for embedded software development. Because group members have a shared area of focus, the SIG concept lends itself to much closer collaboration than it does at the broader working group level.
Q. What is the relationship between the SIG and the Eclipse Cloud DevTools Working Group?
A. For starters, the work done in the SIG must be consistent with the working group charter. We’ve established the embedded SIG with a “trial run” model. Organizations can get involved and talk with all of the other interested parties during a three-month incubation period. At the end of the three-month period, they can either officially join the Eclipse Cloud DevTools Working Group and continue in the SIG, or drop out gracefully.
It’s been a successful model. So far, three companies involved in the SIG — Arm, STMicroelectronics, and Renesas — have become members of the working group. The other two participants — EclipseSource and Ericsson — were already members of the working group.
Q. What stage is the SIG at in its development?
A. We had an open kickoff call in late February with representatives from eight or nine organizations, so the group is just getting started. It’s a great time for additional organizations to get involved because they can really help shape the direction and activities of the group. The group just nominated its first chairperson — Rob Moran from Arm — who will set up meetings, create the agenda, and decide on the work items.
During the kickoff meeting, we had a couple of demos, and those were real “aha” moments for everyone on the call because there was a perception among some that cloud software in this domain was vaporware. These are real-world applications that are already being used.
Arm demonstrated its Mbed Studio product, which is built on Eclipse Theia. It’s currently available as a desktop application, but is being rebranded and will also run in-browser. And Ericsson demonstrated a memory inspection tool, which is a very important capability in that environment. It really showed that things are happening in the embedded tools industry.
Q. What are the group’s goals?
A. The primary goal is to accelerate the move from desktop tools for embedded development to cloud-hosted tools. As part of this effort, the group will develop and promote technical standards to help drive innovation in the embedded tool ecosystem. This will help to create a foundational layer for cloud development tools upon which embedded tool vendors can innovate.
By collaborating, the group can bring these foundational pieces to market faster to accelerate their momentum and adoption. They can also help to identify and fill gaps in the Eclipse Cloud DevTools ecosystem that are specific to embedded environments.
Q. Has a tactical approach to achieve these goals been developed at this point?
A. The starting point is Eclipse Theia. It’s a mature technology, it’s widely used in the marketplace, and it runs in desktop and cloud environments. So, it provides a great option for embedded tool vendors. The first steps are to ensure Theia offers basic embedded developer functionality and can be extended for device-specific features.
To accomplish this, a new code stream called Theia Blueprint has been created from Theia. Vendors can use the Theia Blueprint code as a template application and foundation to build their own software for their own use case. They can then feed that experience back into the group as the basis for discussion around additional features and APIs that are needed and protocols that should be standardized.
These efforts will give embedded tool vendors a more mature project to use as the basis for commercial tools.
Q. Are there other aspects of embedded cloud development tools that are likely to be addressed in the SIG?
A. Naturally, the conversation and focus areas will evolve as the group wants them to. But another likely focus area is determining the most efficient way for organizations to invest in cloud- and web-based embedded development tools while they’re still investing in desktop solutions. What does the migration path to the cloud look like? There’s going to be a long tail for that migration because these organizations will still have many customers using their current products as they evolve to the cloud.
Q. How can organizations learn more about the SIG and get involved?
We encourage everyone to join the conversation, even if they’re not currently an Eclipse Foundation member.