-
Dennis Hendriks authored- Point to contact page rather than forum / dev-list. - GitLab is primary for non-committer communication, not dev-list.
Dennis Hendriks authored- Point to contact page rather than forum / dev-list. - GitLab is primary for non-committer communication, not dev-list.
Contributing to Eclipse ESCET™
Contributions are always welcome!
Project description
The Eclipse Supervisory Control Engineering Toolkit (Eclipse ESCET™) project provides a toolkit for the development of supervisory controllers. The toolkit has a strong focus on industrial applicability, e.g. to cyber-physical systems. The toolkit includes tooling to support the entire development process of (supervisory) controllers, including among others specification, supervisory controller synthesis, simulation-based validation and visualization, formal verification, real-time testing, and code generation.
For more information, see:
-
Website: https://eclipse.dev/escet
-
Project home: https://projects.eclipse.org/projects/technology.escet
Developer resources
For more information regarding source code management, builds, setting up a developer environment, coding standards, how to contribute, and more, see the Eclipse ESCET development documentation at:
The project maintains the following source code repositories:
-
Main repository: https://gitlab.eclipse.org/eclipse/escet/escet.git
-
Website repository: https://gitlab.eclipse.org/eclipse/escet/escet-website.git
These can also be accessed via a web interface:
-
Main repository: https://gitlab.eclipse.org/eclipse/escet/escet
-
Website repository: https://gitlab.eclipse.org/eclipse/escet/escet-website
The main repository has released content in its master branch, and current developments go into the develop branch.
New website versions are deployed from the build of the main repository.
Changes should therefore be made to the main repository, rather than directly to the website repository.
This project uses GitLab to track ongoing development and issues:
Since the website repository does not have its own issue tracker, issues for the website should be made on the main repository as well. Be sure to search for existing issues before you create another one. Remember that contributions are always welcome!
To contribute source code (e.g. patches) via GitLab, see:
To create issues, reply to issues, contribute patches and merge requests, etc, you need an Eclipse Foundation account. It can easily be created at https://accounts.eclipse.org/user/register.
Please start each commit message with the issue number, e.g. #NNN Commit summary. for issue NNN.
The main repository can be built using the build.sh or build.cmd script located in the root of that repository.
Eclipse Contributor Agreement
Before your contribution can be accepted by the project team, contributors must electronically sign the Eclipse Contributor Agreement (ECA).
Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file.
For more information, please see the Eclipse Committer Handbook: