Code of Conduct: Let's revamp it.
[muen/linux.git] / Documentation / process / index.rst
1 .. raw:: latex
2
3         \renewcommand\thesection*
4         \renewcommand\thesubsection*
5
6 .. _process_index:
7
8 Working with the kernel development community
9 =============================================
10
11 So you want to be a Linux kernel developer?  Welcome!  While there is a lot
12 to be learned about the kernel in a technical sense, it is also important
13 to learn about how our community works.  Reading these documents will make
14 it much easier for you to get your changes merged with a minimum of
15 trouble.
16
17 Below are the essential guides that every developer should read.
18
19 .. toctree::
20    :maxdepth: 1
21
22    howto
23    code-of-conduct
24    development-process
25    submitting-patches
26    coding-style
27    maintainer-pgp-guide
28    email-clients
29    kernel-enforcement-statement
30    kernel-driver-statement
31
32 Other guides to the community that are of interest to most developers are: 
33
34 .. toctree::
35    :maxdepth: 1
36
37    changes
38    submitting-drivers
39    stable-api-nonsense
40    management-style
41    stable-kernel-rules
42    submit-checklist
43    kernel-docs
44
45 These are some overall technical guides that have been put here for now for
46 lack of a better place.
47
48 .. toctree::
49    :maxdepth: 1
50
51    applying-patches
52    adding-syscalls
53    magic-number
54    volatile-considered-harmful
55    clang-format
56
57 .. only::  subproject and html
58
59    Indices
60    =======
61
62    * :ref:`genindex`