tjh.dev
+8
-8
Documentation/process/code-of-conduct-interpretation.rst
+8
-8
Documentation/process/code-of-conduct-interpretation.rst
···
45
45
46
46
Maintainers should be willing to help when problems occur, and work with
47
47
others in the community when needed. Do not be afraid to reach out to
48
-
the TAB or other maintainers if you're uncertain how to handle
49
-
situations that come up. It will not be considered a violation report
50
-
unless you want it to be. If you are uncertain about approaching the
51
-
TAB or any other maintainers, please reach out to our conflict mediator,
52
-
Mishi Choudhary <mishi@linux.com>.
48
+
the Technical Advisory Board (TAB) or other maintainers if you're
49
+
uncertain how to handle situations that come up. It will not be
50
+
considered a violation report unless you want it to be. If you are
51
+
uncertain about approaching the TAB or any other maintainers, please
52
+
reach out to our conflict mediator, Mishi Choudhary <mishi@linux.com>.
53
53
54
54
In the end, "be kind to each other" is really what the end goal is for
55
55
everybody. We know everyone is human and we all fail at times, but the
···
125
125
joined or after they have left the committee.
126
126
127
127
The initial Code of Conduct Committee consists of volunteer members of
128
-
the Technical Advisory Board (TAB), as well as a professional mediator
129
-
acting as a neutral third party. The first task of the committee is to
130
-
establish documented processes, which will be made public.
128
+
the TAB, as well as a professional mediator acting as a neutral third
129
+
party. The first task of the committee is to establish documented
130
+
processes, which will be made public.
131
131
132
132
Any member of the committee, including the mediator, can be contacted
133
133
directly if a reporter does not wish to include the full committee in a