]>
Commit | Line | Data |
---|---|---|
c3e270f4 FB |
1 | --- |
2 | title: Contributing | |
4cdca0af | 3 | category: Contributing |
b41a3f66 | 4 | layout: default |
c3e270f4 FB |
5 | --- |
6 | ||
cc5fddef LP |
7 | # Contributing |
8 | ||
945c6e7c | 9 | We welcome contributions from everyone. However, please follow the following guidelines when posting a GitHub Pull Request or filing a GitHub Issue on the systemd project: |
cc5fddef LP |
10 | |
11 | ## Filing Issues | |
12 | ||
c4bc2e93 | 13 | * We use [GitHub Issues](https://github.com/systemd/systemd/issues) **exclusively** for tracking **bugs** and **feature** **requests** (RFEs) of systemd. If you are looking for help, please contact [systemd-devel mailing list](https://lists.freedesktop.org/mailman/listinfo/systemd-devel) instead. |
c85b6ff1 | 14 | * We only track bugs in the **two** **most** **recently** **released** (non-rc) **versions** of systemd in the GitHub Issue tracker. If you are using an older version of systemd, please contact your distribution's bug tracker instead (see below). See [GitHub Release Page](https://github.com/systemd/systemd/releases) for the list of most recent releases. |
c4bc2e93 | 15 | * When filing a feature request issue (RFE), please always check first if the newest upstream version of systemd already implements the feature, and whether there's already an issue filed for your feature by someone else. |
945c6e7c | 16 | * When filing an issue, specify the **systemd** **version** you are experiencing the issue with. Also, indicate which **distribution** you are using. |
cc5fddef LP |
17 | * Please include an explanation how to reproduce the issue you are pointing out. |
18 | ||
945c6e7c | 19 | Following these guidelines makes it easier for us to process your issue, and ensures we won't close your issue right-away for being misfiled. |
cc5fddef | 20 | |
75d96e22 LN |
21 | ### Older downstream versions |
22 | For older versions that are still supported by your distribution please use respective downstream tracker: | |
23 | * **Fedora** - [bugzilla](https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=systemd) | |
21d19a7a | 24 | * **RHEL/CentOS** - [bugzilla](https://bugzilla.redhat.com/) or [systemd-rhel github](https://github.com/systemd-rhel/) |
75d96e22 LN |
25 | * **Debian** - [bugs.debian.org](https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=systemd) |
26 | ||
c2205a0d ZJS |
27 | ## Security vulnerability reports |
28 | ||
153d5975 | 29 | See [reporting of security vulnerabilities](SECURITY.md). |
c2205a0d | 30 | |
cc5fddef LP |
31 | ## Posting Pull Requests |
32 | ||
33 | * Make sure to post PRs only relative to a very recent git master. | |
eea98402 FA |
34 | * Follow our [Coding Style](CODING_STYLE.md) when contributing code. This is a requirement for all code we merge. |
35 | * Please make sure to test your change before submitting the PR. See the [Hacking guide](HACKING.md) for details on how to do this. | |
91b80820 | 36 | * Make sure to run the test suite locally, before posting your PR. We use a CI system, meaning we don't even look at your PR, if the build and tests don't pass. |
a87c45a8 | 37 | * If you need to update the code in an existing PR, force-push into the same branch, overriding old commits with new versions. |
fc696d52 | 38 | * After you have pushed a new version, add a comment about the new version (no notification is sent just for the commits, so it's easy to miss the update without an explicit comment). If you are a member of the systemd project on GitHub, remove the `reviewed/needs-rework` label. |
cc5fddef LP |
39 | |
40 | ## Final Words | |
41 | ||
945c6e7c | 42 | We'd like to apologize in advance if we are not able to process and reply to your issue or PR right-away. We have a lot of work to do, but we are trying our best! |
cc5fddef LP |
43 | |
44 | Thank you very much for your contributions! |