🏆 Eclipse Foundation
DINAcon 2020 Business Award winner
Using Eclipse Che
Here you can find references to useful documentation and hands-on guides to learn how to get the most of Eclipse Che: - Customize Che workspaces for your projects - Run VSCode Extensions in Che workspaces - Configure Che for your teams
Feedback and Community
We love to hear from users and developers. Here are the various ways to get in touch with us: * Support: You can ask questions, report bugs, and request features using GitHub issues. * Public Chat: Join the public eclipse-che Mattermost channel to discuss with community and contributors. * Twitter: @eclipse_che * Mailing List: firstname.lastname@example.org * Weekly Meetings: Join us in our Che community meeting every second monday.
If you are interested in fixing issues and contributing directly to the code base: - :bug: Submitting bugs - :pagefacingup: Contributor license agreement - :checkeredflag: Development workflows - :okhand: Review source code changes - :pencil: Improve docs - :building_construction: Che architecture - :octocat: Che repositories - :sparkles: Good first issue for new contributors
Extending Eclipse Che
- Add a new language support. (to be provided soon)
- Package your favorite VSCode extensions and make them available in Che.
- Write your own VSCode extension that runs on a dedicated side car container.
- Build and package your custom Che-Theia editor with your extensions and plugins.
The following CentOS CI jobs are associated with the repository:
master- builds and push Maven artifacts on each commit to the
nightly- builds and push Maven artifacts, builds CentOS images and pushes them to quay.io on a daily basis from the
release- builds and push Maven artifacts, builds images from the
releasebranch. CentOS images are public and pushed to quay.io.
Che is open sourced under the Eclipse Public License 2.0.