rust/pin-init/CONTRIBUTING.md

1 # Contributing to `pin-init`
3 Thanks for showing interest in contributing to `pin-init`! This document outlines the guidelines for
4 contributing to `pin-init`.
6 All contributions are double-licensed under Apache 2.0 and MIT. You can find the respective licenses
7 in the `LICENSE-APACHE` and `LICENSE-MIT` files.
9 ## Non-Code Contributions
25 problems or just have questions related to `pin-init` in the Linux kernel, you can also ask your
26 questions in the [Rust-for-Linux Zulip](https://rust-for-linux.zulipchat.com/) or see
27 <https://rust-for-linux.com/contact>.
33 `pin-init` is used by the Linux kernel and all commits are synchronized to it. For this reason, the
34 same requirements for commits apply to `pin-init`. See [the kernel's documentation] for details. The
37 [the kernel's documentation]: https://docs.kernel.org/process/submitting-patches.html
39 Contributions to `pin-init` ideally go through the [GitHub repository], because that repository runs
44 [GitHub repository]: https://github.com/Rust-for-Linux/pin-init
55 Commits must have a meaningful commit title. Commits with changes to files in the `internal`
57 change and its rationale. You also have to add your `Signed-off-by` tag, see [Developer's
61 …n]: https://docs.kernel.org/process/submitting-patches.html#sign-your-work-the-developer-s-certifi…
67 If you make changes to the top-level crate documentation, you also need to update the `README.md`
71 kernel version of this library. Those files are documented in the `sync-kernel.sh` script at the
72 very bottom in the `--exclude` flag given to the `git am` command.