Re: [Tech-board-discuss] Linux Kernel Code of Conduct Committee: September 30, 2023

Greg KH <[email protected]> Mon, 16 Oct 2023 17:03:10 +0200
Newsgroups dev.linux.lists.tech-board-discuss
Message-ID <2023101626-equal-blazer-6b4b@gregkh>
On Mon, Oct 16, 2023 at 10:39:33AM -0400, Steven Rostedt wrote:
> On Wed, 4 Oct 2023 10:54:16 -0600
> Shuah Khan <[email protected]> wrote:
> 
> > Dear TAB members,
> > 
> > Please review this Code of Conduct Report for April 1, 2023 through
> > September 30, 2023 and give us feedback.
> > 
> 
> Sorry for the late reply, just been way behind in work lately.
> 
> > 
> > --------------------------------------------------------------------
> > Linux Kernel Code of Conduct Committee: September 30, 2023
> > 
> > In the period of April 1, 2023 through September 30, 2023, the Code of
> > Conduct Committee received the following reports:
> > 
> > Unacceptable behavior or comments in email: 4
> > 
> > The result of the investigation:
> >   - Education and coaching clarifying the Code of Conduct conduct
> >     related to normal review and patch acceptance process: 3
> >   - Clarification on the Code of Conduct conduct related to
> >     maintainer rights and responsibility to reject code: 1
> > 
> > The reports were about the discussion during the patch review and
> > decisions made in rejecting code and these actions are not viewed
> > as violations of the Code of Conduct.
> > 
> > Please see the excerpt from the Responsibilities section in the
> > code-of-conduct-interpretation.rst document:
> > 
> > "setting expertise expectations, making decisions and rejecting unsuitable
> > contributions are not viewed as a violation of the Code of Conduct."
> 
> Sounds to me that people are trying to use the CoC as a way to get code
> accepted?

Yes, people are trying to use the CoC as a way to push back on patch
rejections, it's not anything new, unfortunately :(

> Well, there's only 4 reports in a month. I hope that's not too
> much of a hassle.

4 reports in 6 months, it's not much of a hassle so far.

thanks,

greg k-h