diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-10-19 10:28:14 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-10-22 07:33:35 +0100 |
| commit | d84feee76f7f8171550ea2859c16f393599d0f58 (patch) | |
| tree | 4508c38d39a94109b5599102f93ef77595ee03c8 /Documentation/process | |
| parent | 79dbeed36f7335ec6432029dbf019ebce28e963e (diff) | |
| download | linux-d84feee76f7f8171550ea2859c16f393599d0f58.tar.gz linux-d84feee76f7f8171550ea2859c16f393599d0f58.tar.bz2 linux-d84feee76f7f8171550ea2859c16f393599d0f58.zip | |
Code of Conduct Interpretation: Properly reference the TAB correctly
We use the term "TAB" before defining it later in the document. Fix
that up by defining it at the first location.
Reported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Acked-by: Chris Mason <clm@fb.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Theodore Ts'o <tytso@mit.edu>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/process')
| -rw-r--r-- | Documentation/process/code-of-conduct-interpretation.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst index b14441711f7b..ecf84cd29735 100644 --- a/Documentation/process/code-of-conduct-interpretation.rst +++ b/Documentation/process/code-of-conduct-interpretation.rst @@ -45,11 +45,11 @@ regarding conduct issues. Maintainers should be willing to help when problems occur, and work with others in the community when needed. Do not be afraid to reach out to -the TAB or other maintainers if you're uncertain how to handle -situations that come up. It will not be considered a violation report -unless you want it to be. If you are uncertain about approaching the -TAB or any other maintainers, please reach out to our conflict mediator, -Mishi Choudhary <mishi@linux.com>. +the Technical Advisory Board (TAB) or other maintainers if you're +uncertain how to handle situations that come up. It will not be +considered a violation report unless you want it to be. If you are +uncertain about approaching the TAB or any other maintainers, please +reach out to our conflict mediator, Mishi Choudhary <mishi@linux.com>. In the end, "be kind to each other" is really what the end goal is for everybody. We know everyone is human and we all fail at times, but the @@ -125,9 +125,9 @@ are listed at <URL>. Members can not access reports made before they joined or after they have left the committee. The initial Code of Conduct Committee consists of volunteer members of -the Technical Advisory Board (TAB), as well as a professional mediator -acting as a neutral third party. The first task of the committee is to -establish documented processes, which will be made public. +the TAB, as well as a professional mediator acting as a neutral third +party. The first task of the committee is to establish documented +processes, which will be made public. Any member of the committee, including the mediator, can be contacted directly if a reporter does not wish to include the full committee in a |