linux-kernel - [PATCH v3 0/3] code of conduct fixes

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-next>] [day] [month] [year] [list]

Message-ID: <1539701820.2805.6.camel@HansenPartnership.com>
Date:   Tue, 16 Oct 2018 07:57:00 -0700
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     ksummit-discuss@...ts.linuxfoundation.org
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: [PATCH v3 0/3] code of conduct fixes

Resend to modify the third patch to add (except where required by law)
and accumulate more tags

---

Previous cover letter:

Resend to show accumulated tags and also to add a third patch listing
the TAB as the reporting point as a few people seem to want.  If it
gets the same level of support, I'll send it in with the other two.

---

Previous cover letter:

We've had several threads discussing potential changes to the code of
conduct but Mauro is the only person to have proposed an actual patch. 
In order to move the debate on, I'm presenting two patches, one to fix
the email problem Mauro identified and the other to strip the
enforcement section pending community discussion as Shuah suggested.

I'll take responsibility for collecting any tags people want to add
(review/ack/sign off, etc) and sending the patch in as a signed pull
request before 4.19 final if they get enough community support.

Note, I've sent both patches in as a series to facilitate review and
discussion, but they are separable if one is looked on with less favour
than the other.

It was also a bit unclear which list to send this to, but I finally
settled on linux-kernel as the catch all and ksummit-discuss since
that's where most of the current discussion is.  I can add other lists
as people suggest them.

James

---

James Bottomley (3):
  code-of-conduct: Fix the ambiguity about collecting email addresses
  code-of-conduct: Strip the enforcement paragraph pending community
    discussion
  code-of-conduct: Add back the TAB as the central reporting point

 Documentation/process/code-of-conduct.rst | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

-- 
2.13.7