[dummy-responder] contribution guidlines

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

• (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

• (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

• (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

• (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Code of Conduct

The [dummy-responder] Code of Conduct applies to this WG.

[dummy-responder] Code of Conduct: https://gitlab.bjoernbartels.earth/devops/dummy-responder/-/blob/master/CODE-OF-CONDUCT.md

Resources

• Website: https://dummy-responder.net
• GitLab project group: https://gitlab.bjoernbartels.earth/devops/dummy-responder/
• Documentation repository: https://gitlab.bjoernbartels.earth/devops/dummy-responder/-/blob/master/website/docs/

Reporting Potential Security Issues

If you have encountered a potential security vulnerability, please DO NOT report it on the public issue tracker: send it to us at info@bjoernbartels.earth instead. We will work with you to verify the vulnerability and patch it as soon as possible.

When reporting issues, please provide the following information:

• Component(s) affected
• A description indicating how to reproduce the issue
• A summary of the security vulnerability and impact

We request that you contact us via the email address above and give the project contributors a chance to resolve the vulnerability and issue a new release prior to any public exposure; this helps protect users and provides them with a chance to upgrade and/or update in order to protect their applications.

Recommended Workflow for Contributions

...

Running Coding Standards Checks

...

Running Tests

...