Welcome to the openDuT community. We appreciate contributions and suggestions.
Start here for info on how to contribute and help improve the project.
When contributing, please observe the Eclipse Community Code of Conduct.
If you have a bug to report or would like to suggest a feature, please open an issue.
To contribute code to this project, you will need an Eclipse Foundation account and agree to the Eclipse Contributor Agreement.
See more info at https://www.eclipse.org/projects/handbook/#contributing-contributors.
Code contributions can be submitted via pull requests.
To do so, fork this repository, apply the suggested changes and create a pull request to integrate them.
The pull request should be created against the development branch.
Before creating the request, please ensure the following:
- No breakages: All builds and tests pass (CI/CD).
- Docs updated: Make sure any changes and additions are appropriately included into the design and user documentation.
After opening your request, we will also check these in addition to a technical review.
Our goal is to keep the development branch in a releasable state.
Try to make atomic changes or if a change has to be split in such a way that the intermediate steps are not functional,
then ideally introduce a feature toggle until the new working state is reached.
If this is ensured, it also allows us to merge your changes early on, to reduce unnecessary busywork from merge conflicts.
Contact the project developers via chat, the project's "dev" mailing list or raise an issue.
- Chat: https://chat.eclipse.org/#/room/#automotive.opendut:matrix.eclipse.org
- Dev list: https://www.eclipse.org/mailman/listinfo/opendut-dev
- Issues: https://github.com/eclipse-opendut/opendut/issues
The Eclipse openDuT project has a call every second Wednesday between 15:30 and 16:30 UTC.
Everyone in the community is welcome to join!
See the Eclipse SDV Community Calendar for the exact dates and joining instructions.
The calendar can be found here: https://sdv.eclipse.org/get-engaged/