The objective of this project is to manage runtime extensions for cloud IDEs such as Theia. A runtime extension is one that can be plugged into a running application. In contrast, a compile-time extension is one that is baked into the application when it is built. Theia currently supports both: runtime extensions (plug-ins) using the VS Code extension API and compile-time extensions using the Theia extension API. The latter are already published to the npm Package Registry and are therefore not in the scope of this project.
The initial focus will be on extensions that follow the VS Code extension API. Further extension formats may be added in case Theia or other relevant cloud IDE projects decide to abandon the VS Code format. This is rather unlikely, but in theory such a step could become necessary because the VS Code format is governed solely by Microsoft.
The Extension Registry will include the following components:
Server
Web Interface
Command Line Interface (CLI)
The following topics are not on the initial agenda, but are potentially in the scope of this project:
The following topics are not in the scope of this project:
| Repo | Commits | Reviews | Issues |
|---|---|---|---|
| https://github.com/EclipseFdn/open-vsx.org | 465 | 239 | 1985 |
| https://github.com/eclipse/openvsx | 384 | 200 | 137 |
There have been 849 commits made by 19 people on 2 repositories over the last 12 months.
There have been 2122 issues submitted by 1566 people on 2 repositories over the last 12 months.
There have been 439 reviews submitted by 22 people on 2 repositories over the last 12 months.
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/ecd.openvsx