workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Shuah Khan <shuah@kernel.org>,
	gregkh@linuxfoundation.org, corbet@lwn.net
Cc: Shuah Khan <shuah@kernel.org>,
	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>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions
Date: Wed, 05 Mar 2025 11:54:28 +0200	[thread overview]
Message-ID: <87h647yf8r.fsf@intel.com> (raw)
In-Reply-To: <20250304194813.11049-1-shuah@kernel.org>

On Tue, 04 Mar 2025, Shuah Khan <shuah@kernel.org> wrote:
>  Any decisions regarding enforcement recommendations will be brought to
>  the TAB for implementation of enforcement with the relevant maintainers
> -if needed.  A decision by the Code of Conduct Committee can be overturned
> -by the TAB by a two-thirds vote.
> +if needed.  Once the TAB approves one or more of the measures outlined
> +in the scope of the ban by two-thirds of the members voting for the
> +measures, the Code of Conduct Committee will enforce the TAB approved
> +measures.  Any Code of Conduct Committee members serving on the TAB will
> +not vote on the measures.

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.


BR,
Jani.


-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-03-05  9:54 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 [this message]
2025-03-05 15:31   ` Steven Rostedt
2025-03-05 20:08     ` Shuah

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=87h647yf8r.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=conduct@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.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