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: <4d44dry7ypmiglysj5ovrv3zv2g6uabezosck6ae6hkf2wha4i@eculpqwugece>
Date: Thu, 14 Nov 2024 10:02:49 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: gregkh@...uxfoundation.org, corbet@....net, workflows@...r.kernel.org, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, rdunlap@...radead.org, 
	daniel@...ll.ch, laurent.pinchart@...asonboard.com, broonie@...nel.org, 
	Linus Torvalds <torvalds@...ux-foundation.org>, Miguel Ojeda <ojeda@...nel.org>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, Steven Rostedt <rostedt@...dmis.org>, 
	Dan Williams <dan.j.williams@...el.com>, Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH v3] Documentation/CoC: spell out enforcement for
 unacceptable behaviors

On Thu, Nov 14, 2024 at 08:01:34AM -0700, Shuah Khan wrote:
> >      c. restricting their ability to communicate via kernel.org platforms,
> >         such as mailing lists and social media sites
> > 
> > It makes more sense to phrase it this way, because it's really the
> > communication that is the focus of this policy, not general access like git,
> > patchwork, etc.
> > 
> 
> Thank you Konstantin. Correct. The intent is to restrict communication.
> The way you phrased it makes perfect sense. I will make the change.

Thank you!

Acked-by: Konstantin Ryabitsev <konstantin@...uxfoundation.org>

-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ