Skip to content

Latest commit

 

History

History
104 lines (80 loc) · 4.76 KB

CONTRIBUTING.md

File metadata and controls

104 lines (80 loc) · 4.76 KB

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Do note that this project has a code of conduct; please be sure to follow it in all of your project interactions.

Pull Request Process

  1. Ensure any install or build artifacts are removed before the end of the layer when doing a build
  2. Update the README.md and/or any other related doc file with details of changes to the collection.
  3. Update CHANGELOG.md and increase the version numbers in galaxy.yml to the new version that this Pull Request would represent. The versioning scheme we use is (mostly) SemVer.
  4. Ensure unit tests and sanity tests pass. No PR will be merged if a test is failing. See docs/development_environment.md to prepare your development environment to run these tests.
  5. If a new software type is included for discovery, at least one automatic unit test for this software must be included in tests/unit/plugins/action/auto/resources. In docs/creating_auto_test.md you can find information on how to generate this kind of test files.
  6. Keep software instance data structure. Use the standard fields: bindings, files, endpoints and messages to store those kinds of information. If some data cannot be considered in any of those fields, store it in extra_data field. No new fields should be created apart from children of extra_data fields.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Showing empathy towards other community members
  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community

Examples of unacceptable behavior by participants include:

  • Use of sexualized language or imagery and unwelcome sexual attention or advances
  • Insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project leadership.

All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4