Eclipse Open VSX is an established tool. Open VSX is new. Open VSX (registry) is THE marketplace. Can we really use the Open VSX registry? Many questions surround this emerging service and project. We will explain Ericsson’s viewpoint.
We will go over Eclipse Open VSX’s more unique selling points. We will briefly go over the legal side, even though the presenter is not a lawyer. We will discuss how this project will affect both Eclipse Theia implementations such as Blueprints, CDT Cloud, Theia Cloud, etc... and VSCodium as well as CodeOSS their forks. With modern IDE’s popularity, the marketplace is king and queen. However, it is not a free ride.
We will also explain Ericsson's deep interest in Open VSX as well as its vision for using this platform to enhance its software development endeavors. We will share Ericsson’s strategy using Open VSX and an internal instance:
- Decentralized design: As Open VSX is not designed to be monolithic, an instance can be hosted locally, we will discuss the status of the Ericsson internal deployment as well as the reasons for adopting a tiered/hybrid solution.
- Collaboration led innovation: To be blunt, Eclipse Open VSX is in a unique position. It needs to serve everybody. This is a huge opportunity in terms of requirement gathering. How can we capitalize on it?
- Security and governance: This is a major opportunity on the open-source side, and a deciding factor internally. We shall discuss the implications of using VSX for our software compliance, and highlight our common ground in the ecosystem.
- Community engagement and contributions: Ericsson believes in building collaborative communities. Open VSX is a strategic technology that we will develop. We wish to ensure our vision of the project contributes to the community at large and that we can share knowledge, code contributions and requirements.
Join us to see why Ericsson is deeply interested in Eclipse Open VSX as well as the registry and how this initiative aligns with its software development goals. Discover how Open VSX unlocks new opportunities for collaboration, customization, and security, and learn how Ericsson aims to actively contribute to this growing ecosystem. This talk is aimed at tool developers and OSPOs (Open-Source Program Office), it will show how Ericsson plans on handling internal marketplaces and controlling our SBOMs (Software Bills of Materials).