mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-06 02:24:14 +08:00
186128f753
Add several documents to the development-process ReST book. As we don't want renames, use symlinks instead, keeping those documents on their original place. Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
29 lines
1.4 KiB
ReStructuredText
29 lines
1.4 KiB
ReStructuredText
Code of Conflict
|
|
----------------
|
|
|
|
The Linux kernel development effort is a very personal process compared
|
|
to "traditional" ways of developing software. Your code and ideas
|
|
behind it will be carefully reviewed, often resulting in critique and
|
|
criticism. The review will almost always require improvements to the
|
|
code before it can be included in the kernel. Know that this happens
|
|
because everyone involved wants to see the best possible solution for
|
|
the overall success of Linux. This development process has been proven
|
|
to create the most robust operating system kernel ever, and we do not
|
|
want to do anything to cause the quality of submission and eventual
|
|
result to ever decrease.
|
|
|
|
If however, anyone feels personally abused, threatened, or otherwise
|
|
uncomfortable due to this process, that is not acceptable. If so,
|
|
please contact the Linux Foundation's Technical Advisory Board at
|
|
<tab@lists.linux-foundation.org>, or the individual members, and they
|
|
will work to resolve the issue to the best of their ability. For more
|
|
information on who is on the Technical Advisory Board and what their
|
|
role is, please see:
|
|
|
|
- http://www.linuxfoundation.org/projects/linux/tab
|
|
|
|
As a reviewer of code, please strive to keep things civil and focused on
|
|
the technical issues involved. We are all humans, and frustrations can
|
|
be high on both sides of the process. Try to keep in mind the immortal
|
|
words of Bill and Ted, "Be excellent to each other."
|