Skip to content

Latest commit

 

History

History
53 lines (39 loc) · 3.8 KB

Contribution.md

File metadata and controls

53 lines (39 loc) · 3.8 KB

Contributing:

We love your opinion! We want the contribution to this project to be as simple and transparent as possible, either: Reporting a bug Discussing the current state of the code Submitting a fix Proposing new features Becoming a maintainer

We Develop with Github

We use github to host code, track issues and feature requests, and accept pull requests.

Pull Request Process

  1. Make sure all build or install dependencies are removed before the end of the layer when you run a build.
  2. Update README.md with details of the interface changes, including new environment variables, exposed ports, useful file locations, and container parameters.
  3. Increase the version numbers in all the sample files and the README.md file to the new version that this pull request would represent.
  4. You can merge the pull request once you have approval from two other developers, or if you don't have permission to do so, you can ask the second reviewer to merge it for you.

Write bug reports with detail, background, and sample code:

Great Bug Reports tend to have:

  1. A quick summary and/or background
  2. Being specified about it.
  3. What you expected would happen
  4. What actually happens
  5. Notes

Code of Conduct: Our code of conduct means that you are responsible for treating all project participants, regardless of their identity, with respect and courtesy. If you are the victim of inappropriate behavior or comments, as described in our Code of Conduct, we are here to help and will do our best to ensure that the abuser receives an appropriate reprimand in accordance with our Code.

Pledge: In the hobby of fostering an open and inviting environment, we as participants and maintainers pledge to creating participation in our mission and our network a harassment-loose enjoy for everyone, irrespective of age, frame size, disability, ethnicity, gender identification and expression, stage of enjoy, nationality, non-public appearance, race, religion, or sexual identification and orientation.

Standards we live by:

  1. Use welcoming and inclusive language
  2. Respect different points of view and experiences
  3. Accept constructive criticism gracefully
  4. Focus on what is best for the community
  5. Show empathy towards other community members

Responsibilities Project managers are responsible for clarifying standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any incident of unacceptable behavior. Supervisors have the right and responsibility to remove, edit, or reject comments, confirmations, codes, wiki edits, issues, and other posts that do not comply with this Code of Conduct, or to temporarily or permanently block posts for any other behavior they may have. consider inappropriate, threatening, offensive or harmful.

Scope: This code of conduct applies both in project rooms and in public spaces when one person represents the project or their community. Examples of representing a project or community include using an official project email address, posting through an official social media account, or acting as a designated representative at an online or offline event. Project supervisors can further define and clarify the presentation of a project.

Enforcement: Cases of abusive, harassing or otherwise unacceptable behavior can be reported by contacting the project team at out email. All complaints will be reviewed and investigated and will result in a response deemed necessary and appropriate to the circumstances. The project team is obliged to maintain secrecy regarding the informant of an incident. More details on specific application policies may be published separately. Project supervisors who do not follow or enforce the Code of Conduct in good faith may have temporary or permanent consequences as determined by other members of the project management team.