You want to contribute to emobility-smart-charging? Welcome! Please read this document to understand what you can do:
- Analyze Issues
- Reporting Security Issues
- Contribute Code
- Reporting Security Issues
- Contributor License Agreement Acceptance
Analyzing issue reports can be a lot of effort. Any help is welcome! Go to the Github issue tracker and find an open issue which needs additional work or a bugfix. Maybe you can even find and contribute a bugfix?
When an issue is reported, a committer will look at it and either confirm it as a real issue (by giving the "approved" label), close it if it is not an issue, or ask for more details. Approved issues are then either assigned to a committer in GitHub, reported in our internal issue handling system, or left open as "contribution welcome" for easy or not urgent fixes. An issue that is about a real bug is closed as soon as the fix is committed.
You are welcome to contribute code to emobility-smart-charging in order to fix bugs or to implement new features.
If you find a security issue, please act responsibly and report it not in the public issue tracker, but directly to us, so we can fix it before it can be exploited:
- SAP Customers: if the found security issue is not covered by a published security note, please report it by creating a customer message at https://service.sap.com/message.
- Researchers/non-Customers: please send the related information to secure@sap.com using PGP for e-mail encryption. Also refer to the general SAP security information page.
Due to legal reasons, contributors will be asked to accept a DCO before they submit the first pull request to this projects, this happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.