linux-kernel - Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5a284bee-c332-4af2-b7ad-56296e419e18@kernel.org>
Date: Wed, 5 Mar 2025 13:08:51 -0700
From: Shuah <shuah@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>, Jani Nikula <jani.nikula@...el.com>
Cc: Shuah Khan <shuah@...nel.org>, gregkh@...uxfoundation.org,
 corbet@....net, workflows@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, conduct@...nel.org, tab@...ts.linux.dev,
 Miguel Ojeda <ojeda@...nel.org>
Subject: Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement
 decisions

On 3/5/25 08:31, Steven Rostedt wrote:
> On Wed, 05 Mar 2025 11:54:28 +0200
> Jani Nikula <jani.nikula@...el.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