code of conduct fixes
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest3 patches 14 repliesIn review
- v23 patches 18 repliesSuperseded
- v12 patches 57 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | code-of-conduct: Fix the ambiguity about collecting email addressesDocumentation/ | +1 | 13 replies | |
| 2/3 | code-of-conduct: Strip the enforcement paragraph pending community discussionDocumentation/ | +0 | 0 replies | |
| 3/3 | code-of-conduct: Add back the TAB as the central reporting pointDocumentation/ | +11 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Geert Uytterhoeven | Shuah Khan | Guenter Roeck | Alan Cox | Mauro Carvalho Chehab | Eric W. Biederman | Kees Cook | Konrad Rzeszutek Wilk |
|---|---|---|---|---|---|---|---|---|
| 1/3 | A-b | A-b | A-b | R-b | R-b | A-b | A-b | |
| 2/3 | A-b | A-b | A-b | R-b | ||||
| 3/3 | A-b | A-b | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 8 reviewers.
Cover letter [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(-)
Signature · 1 line
2.13.7