Skip to main content

Oreon Contribution Policy

Anyone may contribute to Oreon. Contributions can include code, packaging, documentation, testing, design work, or bug reports.

Clear rules help make sure contributions can safely become part of the project.

Ownership of contributions​

Contributors must only submit work that they have the legal right to contribute.

By submitting code or other contributions to Oreon repositories, you confirm that:

  • the work is your original contribution, or
  • you have permission to submit the work under the project license
  • you are giving us permission to hold the code, and that you cannot claim to "own" any parts of the code whatsoever

Contributions that violate this policy cannot be accepted.

Licensing​

All Oreon repositories must include a license file.

Allowed licenses include GPLv2, GPLv3, MIT, or other licenses approved by the Oreon project leader.

Repositories should prefer GPLv3 unless there is a specific reason to use another license.

Licensing agreement​

All contributions included in Oreon must follow the license of the repository they are submitted to.

By submitting a pull request, patch, or other contribution to an Oreon repository, you agree that your contribution will be distributed under the same license as the repository.

This ensures that all project code remains legally consistent.

Development repositories​

Official Oreon development happens in the project's public repositories.

Contributors may use personal repositories during development. However, code intended to become part of Oreon must eventually be submitted to the official Oreon repositories.

Once code is merged into an Oreon repository, it becomes part of the project and is governed by the project license.

Commit messages​

All commits must include at least some detail. We do not like commits that are vague and don't explain what has changed.

Pull requests​

Pull requests should clearly explain the purpose of the change.

Contributors should include:

  • a clear description of the change
  • a reasonable commit history
  • any relevant testing information

Maintainers may request changes before accepting a contribution.

Not every contribution will be accepted.

Maintainer responsibilities​

Maintainers are responsible for protecting the stability and direction of a given sub-project.

Maintainers may:

  • review and merge contributions
  • request changes to proposed work
  • reject contributions that do not align with project goals
  • revert changes that cause problems