Skip to content

Commit bb44dc1

Browse files
committed
Contributing: add "Finding tasks and issues to work on" subsection
It is a common question from newcomers how to find tasks and issues to work on. Add a new section to the "Contributing" document that tries to answer this in general, including linking to our "good first issue" and to our 'Other tasks and "good first issues"' list and suggesting to reviewing code and subscribing to the mailing list. At the same time, update in our issue tracker the 'Other tasks and "good first issues"' to include Nova's and Tyr's issue trackers / TODO list. Rename as well the title to that one, since it really covers tasks in general, not just "good first issues", especially now that we have our users' issue trackers and TODO lists there. It is an issue that has been pinned for a long time, thus it has extra visibility and is a way for others looking at our issue list to find other trackers. We could mention the list here in the website too, but it is easier to update it as one of the "live lists" we have in GitHub instead. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
1 parent 1e86466 commit bb44dc1

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

src/Contributing.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The Rust support is part of the Linux kernel, and thus contributing works the sa
3030

3131
To learn more about the kernel development process, please read the documentation under [`Documentation/process`](https://docs.kernel.org/process/). In particular, please make sure to read [`submitting-patches.rst`](https://docs.kernel.org/process/submitting-patches.html).
3232

33-
In addition, it may be a good idea to contribute a small cleanup or fix somewhere in the kernel (not necessarily to Rust code), in order to get accustomed to the patch-based workflow. From time to time we add ["good first issues"](https://github.com/Rust-for-Linux/linux/contribute) to our GitHub issue tracker for that purpose.
33+
In addition, it may be a good idea to contribute a small cleanup or fix somewhere in the kernel (not necessarily to Rust code), in order to get accustomed to the patch-based workflow. Please see the section below on "Finding tasks or issues to work on".
3434

3535
## Ways to contribute
3636

@@ -48,6 +48,14 @@ There are many ways to contribute to the Rust support in the kernel:
4848

4949
- Helping others on Zulip. For instance, getting them started with the Rust support in the kernel.
5050

51+
### Finding tasks and issues to work on
52+
53+
From time to time we add ["good first issues"](https://github.com/Rust-for-Linux/linux/contribute) to our GitHub issue tracker which are good to get started with Rust kernel development.
54+
55+
In addition, we also have a list of [other tasks "good first issues"](https://github.com/Rust-for-Linux/linux/issues/1058) from our users (e.g. drivers) and other projects.
56+
57+
Finally, reviewing code and subscribing to the mailing list in general are very good ways to identify code you could improve one way or another.
58+
5159
## Getting started with Rust kernel development
5260

5361
Please read the documentation under [`Documentation/rust`](https://docs.kernel.org/rust/). In particular, the [Quick Start guide](https://docs.kernel.org/rust/quick-start.html).

0 commit comments

Comments
 (0)