3 Contributor Policies

Joshua M. Boniface edited this page 6 years ago

This page describes general procedures for the contributors with write access to the repositories. All contributors should seek to adhere to these policies to ensure consistency in the repository.

1. Contributors should set code ownership CODEOWNERS files wherever they consider themselves subject-matter expects, to assist in the review process.

2. PRs to dev should have at least one review by a code owner before being merged. If a section does not have a codeowner, any contributor may review it. More reviews are always better, especially for large PRs or if there are no defined codeowners.

3. PRs to dev should be merged as "Create a merge commit" to ensure the relevant PR is always referenced.

4. PRs to master should only come from dev as a whole, and in the form of a release PR. This PR should be merged as "Create a merge commit" to preserve release history. The PR body should contain a full list of accepted dev PRs. The only exception to this procedure should be emergency PRs which address an extremely time-sensitive issue and where the usual process would be excessively long.

• Home
• Building from source
  • Docker
  • Debian/Ubuntu via Docker
  • Debian/Ubuntu via dpkg-dev
  • Windows (64 bit)
• Contributing to Jellyfin
  • Contributing Code
  • Other Contributions
• Expected Errors
  • Error HttpClient: Error NameResolutionFailure
• Feature Requests
• Issue Guidelines
  • Opening an Issue
  • Issue Labels
• Jellyfin Coding Style
• Jellyfin Debian Repository
  • Clean Install
  • Upgrade from Emby
• Prebuilt Packages
• Social Media
• Web archive of Emby documentation