From: Josh Triplett <josh@joshtriplett.org>
To: Joe Perches <joe@perches.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8
Date: Tue, 23 Oct 2018 08:07:50 +0100 [thread overview]
Message-ID: <20181023070750.GB3068@localhost> (raw)
In-Reply-To: <23e41205115d317908c63d37a20ee316b44a8404.camel@perches.com>
On Mon, Oct 22, 2018 at 09:16:20PM -0700, Joe Perches wrote:
> On Mon, 2018-10-22 at 22:10 +0100, Greg Kroah-Hartman wrote:
> > On Sat, Oct 20, 2018 at 01:15:14PM -0700, James Bottomley wrote:
> > > This is the series of patches which has been discussed on both ksummit-
> > > discuss and linux-kernel for the past few weeks. As Shuah said when
> > > kicking off the process, it's designed as a starting point for the next
> > > phase of the discussion, not as the end point, so it's only really a
> > > set of minor updates to further that goal.
> > >
> > > The merger of the three patches to show the combined effect is attached
> > > below. However, Greg recently posted the next phase of the discussion,
> > > so people will be asking what the merger of the series looks like.
> > > Ignoring the non-CoC documents, I think it looks like this
> >
> > Sorry for not responding sooner for this, travel and the meeting today
> > took up my time.
> >
> > Anyway, as we discussed today in the Maintainers summit, let's leave the
> > Code of Conduct text alone for now. It matches what "upstream" has with
> > the exception of removing that one paragraph. If you have issues with
> > the wording in it, please work with upstream to fix the issues there as
> > hundreds of other projects will benefit with your changes if they are
> > really needed.
>
> Given the different development models, that's not
> a very compelling argument.
>
> As James Bottomley has suggested multiple times,
> I'd much rather kernel development use the debian
> code of conduct verbatim than even this modified one.
>
> https://www.debian.org/code_of_conduct
The Debian code of conduct doesn't do nearly as good a job of addressing
issues. (Debian also adopted that code of conduct back when such codes
weren't nearly as well understood or established.) Many people *in*
Debian, including supporters of their current CoC, have an interest in
improving it further and/or adopting a more well-established one.
next prev parent reply other threads:[~2018-10-23 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 20:15 James Bottomley
2018-10-22 21:10 ` Greg Kroah-Hartman
2018-10-23 4:16 ` Joe Perches
2018-10-23 6:05 ` Randy Dunlap
2018-10-23 6:10 ` Joe Perches
2018-10-23 7:07 ` Josh Triplett [this message]
2018-10-23 9:01 ` Mark Brown
2018-10-23 9:09 ` James Bottomley
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=20181023070750.GB3068@localhost \
--to=josh@joshtriplett.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@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