Baphomet is the dedicated bot for nulloctet matrix
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

91 lines
4.1 KiB

  1. # Contributing
  2. When contributing to this repository, please first discuss the change you wish to make via issue,
  3. email, or any other method with the owners of this repository before making a change.
  4. Please note we have a code of conduct, please follow it in all your interactions with the project.
  5. ## Pull Request Process
  6. 1. Ensure any install or build dependencies are removed before the end of the layer when doing a
  7. build.
  8. 2. Update the README.md with details of changes to the interface, this includes new environment
  9. variables, exposed ports, useful file locations and container parameters.
  10. 3. Increase the version numbers in any examples files and the README.md to the new version that this
  11. Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
  12. 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
  13. do not have permission to do that, you may request the second reviewer to merge it for you.
  14. ## Code of Conduct
  15. ### Our Pledge
  16. In the interest of fostering an open and welcoming environment, we as
  17. contributors and maintainers pledge to making participation in our project and
  18. our community a harassment-free experience for everyone, regardless of age, body
  19. size, disability, ethnicity, gender identity and expression, level of experience,
  20. nationality, personal appearance, race, religion, or sexual identity and
  21. orientation.
  22. ### Our Standards
  23. Examples of behavior that contributes to creating a positive environment
  24. include:
  25. * Using welcoming and inclusive language
  26. * Being respectful of differing viewpoints and experiences
  27. * Gracefully accepting constructive criticism
  28. * Focusing on what is best for the community
  29. * Showing empathy towards other community members
  30. Examples of unacceptable behavior by participants include:
  31. * The use of sexualized language or imagery and unwelcome sexual attention or
  32. advances
  33. * Trolling, insulting/derogatory comments, and personal or political attacks
  34. * Public or private harassment
  35. * Publishing others' private information, such as a physical or electronic
  36. address, without explicit permission
  37. * Other conduct which could reasonably be considered inappropriate in a
  38. professional setting
  39. ### Our Responsibilities
  40. Project maintainers are responsible for clarifying the standards of acceptable
  41. behavior and are expected to take appropriate and fair corrective action in
  42. response to any instances of unacceptable behavior.
  43. Project maintainers have the right and responsibility to remove, edit, or
  44. reject comments, commits, code, wiki edits, issues, and other contributions
  45. that are not aligned to this Code of Conduct, or to ban temporarily or
  46. permanently any contributor for other behaviors that they deem inappropriate,
  47. threatening, offensive, or harmful.
  48. ### Scope
  49. This Code of Conduct applies both within project spaces and in public spaces
  50. when an individual is representing the project or its community. Examples of
  51. representing a project or community include using an official project e-mail
  52. address, posting via an official social media account, or acting as an appointed
  53. representative at an online or offline event. Representation of a project may be
  54. further defined and clarified by project maintainers.
  55. ### Enforcement
  56. Instances of abusive, harassing, or otherwise unacceptable behavior may be
  57. reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
  58. complaints will be reviewed and investigated and will result in a response that
  59. is deemed necessary and appropriate to the circumstances. The project team is
  60. obligated to maintain confidentiality with regard to the reporter of an incident.
  61. Further details of specific enforcement policies may be posted separately.
  62. Project maintainers who do not follow or enforce the Code of Conduct in good
  63. faith may face temporary or permanent repercussions as determined by other
  64. members of the project's leadership.
  65. ### Attribution
  66. This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
  67. available at [http://contributor-covenant.org/version/1/4][version]
  68. [homepage]: http://contributor-covenant.org
  69. [version]: http://contributor-covenant.org/version/1/4/