]> git.ipfire.org Git - thirdparty/systemd.git/blame - docs/CONTRIBUTING.md
fs-util: no need for fchmod_and_chown() to access /proc/self/fd directly
[thirdparty/systemd.git] / docs / CONTRIBUTING.md
CommitLineData
c3e270f4
FB
1---
2title: Contributing
3---
4
cc5fddef
LP
5# Contributing
6
945c6e7c 7We 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
8
9## Filing Issues
10
dc6c3de1 11* We use GitHub Issues **exclusively** for tracking **bugs** and **feature** **requests** of systemd. If you are looking for help, please contact our [mailing list](https://lists.freedesktop.org/mailman/listinfo/systemd-devel) instead.
945c6e7c
ZJS
12* We only track bugs in the **two** **most** **recently** **released** **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.
13* When filing an issue, specify the **systemd** **version** you are experiencing the issue with. Also, indicate which **distribution** you are using.
cc5fddef
LP
14* Please include an explanation how to reproduce the issue you are pointing out.
15
945c6e7c 16Following 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 17
75d96e22
LN
18### Older downstream versions
19For older versions that are still supported by your distribution please use respective downstream tracker:
20* **Fedora** - [bugzilla](https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=systemd)
21* **RHEL-7/CentOS-7** - [bugzilla](https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%207&component=systemd) or [systemd-rhel github](https://github.com/lnykryn/systemd-rhel/issues)
22* **Debian** - [bugs.debian.org](https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=systemd)
23
c2205a0d
ZJS
24## Security vulnerability reports
25
26If you discover a security vulnerability, we'd appreciate a non-public disclosure. The issue tracker and mailing list listed above are fully public. If you need to reach systemd developers in a non-public way, report the issue in one of the "big" distributions using systemd: [Fedora](https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=systemd) (be sure to check "Security Sensitive Bug" under "Show Advanced Fields"), [Ubuntu](https://launchpad.net/ubuntu/+source/systemd/+filebug) (be sure to change "This bug contains information that is" from "Public" to "Private Security"), or [Debian](mailto:security@debian.org). Various systemd developers are active distribution maintainers and will propagate the information about the bug to other parties.
27
cc5fddef
LP
28## Posting Pull Requests
29
30* Make sure to post PRs only relative to a very recent git master.
eea98402
FA
31* Follow our [Coding Style](CODING_STYLE.md) when contributing code. This is a requirement for all code we merge.
32* 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 33* 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 34* If you need to update the code in an existing PR, force-push into the same branch, overriding old commits with new versions.
fc696d52 35* 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
36
37## Final Words
38
945c6e7c 39We'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
40
41Thank you very much for your contributions!