From: Shuah <shuah@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Jani Nikula <jani.nikula@intel.com>
Cc: Shuah Khan <shuah@kernel.org>,
gregkh@linuxfoundation.org, corbet@lwn.net,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, conduct@kernel.org,
tab@lists.linux.dev, Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions
Date: Wed, 5 Mar 2025 13:08:51 -0700 [thread overview]
Message-ID: <5a284bee-c332-4af2-b7ad-56296e419e18@kernel.org> (raw)
In-Reply-To: <20250305103108.4943e301@gandalf.local.home>
On 3/5/25 08:31, Steven Rostedt wrote:
> On Wed, 05 Mar 2025 11:54:28 +0200
> Jani Nikula <jani.nikula@intel.com> wrote:
>
>> 2/3 actually means 7/10 for the TAB.
>>
>> Except two of the CoC committee members currently serve on the TAB, and
>> will not vote. Assuming they will also not count for the total, 2/3
>> means 6/8 = 75%.
>>
>> All of a sudden you actually need 3/4 majority in the TAB to approve any
>> CoC measures.
>>
>> Perhaps consider using a simple majority instead? The numbers become
>> 6/10 and 5/8.
>
> I'm a TAB member but I'm speaking for myself and not on behalf of the TAB.
>
> I rather keep it as is and not move it to a simple majority. If the TAB is
> going to make a decision that may affect the ability of a developer to get
> their work done, the issue had better be substantial where it should have no
> problem getting to 75%. Ideally, it should even be unanimous, but there are
> cases where a member may be involved, and decides to abstain.
>
I am in total agreement with Steve on this. The way the document reads now
with this change allows for oversight when the CoC, the TAB and the community
is forced to make tough decisions that impact developer's ability to participate
in the development process.
thanks,
-- Shuah
prev parent reply other threads:[~2025-03-05 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 19:48 Shuah Khan
2025-03-04 20:09 ` Laurent Pinchart
2025-03-04 21:43 ` Shuah
2025-03-04 21:55 ` Steven Rostedt
2025-03-04 23:48 ` Shuah
2025-03-05 9:54 ` Jani Nikula
2025-03-05 15:31 ` Steven Rostedt
2025-03-05 20:08 ` Shuah [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a284bee-c332-4af2-b7ad-56296e419e18@kernel.org \
--to=shuah@kernel.org \
--cc=conduct@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tab@lists.linux.dev \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox