From: Leon Romanovsky <leon@kernel.org>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: James.Bottomley@hansenpartnership.com,
mchehab+samsung@kernel.org, Tim.Bird@sony.com,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Tue, 25 Sep 2018 08:45:35 +0300 [thread overview]
Message-ID: <20180925054534.GZ3519@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20180924135311.GM1719@techsingularity.net>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
On Mon, Sep 24, 2018 at 02:53:11PM +0100, Mel Gorman wrote:
> On Thu, Sep 20, 2018 at 08:04:39AM +0100, David Woodhouse wrote:
> > On Thu, 2018-09-20 at 09:33 +0300, Jani Nikula wrote:
> > > Agreed.
> > >
> > > I think there's much more value in adopting a widely used code of
> > > conduct than writing your own, or even trying to tweak it. If a project
> > > uses the Contributor Covenant, you pretty much know the rules without
> > > actually having to read another document and wonder what this all means.
> > > In this regard, it's really not unlike the GPL for copyleft licenses;
> > > one acronym tells you what you can and can't do.
> > >
> > > With that perspective, I think the changes proposed in this thread do
> > > more harm than good. If people still insist the text should be improved,
> > > I think the proper flow is to file issues or pull requests to
> > > Contributor Covenant upstream [1], and later update to a new version of
> > > the document.
> >
> > I'll note that isn't what Linus did with the GPL.
> >
> > But perhaps there's a possible solution: Instead of editing the text of
> > the covenant, just preface it with a statement that email addresses
> > used on mailing lists are not considered to be private and that it is
> > acceptable (and indeed recommended) to credit individuals who have
> > contributed to reporting and testing by using their email addresses.
>
> It's not just email addresses We generally require people to use their
> real name and not pseudonyms for patches and their Signed-off-by.
From my understanding, it is covered by DCO clause (d).
https://developercertificate.org/
https://wiki.linuxfoundation.org/dco
Thanks
>
> --
> Mel Gorman
> SUSE Labs
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-09-25 5:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 5:55 [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session) Dave Airlie
2018-09-18 13:43 ` Steven Rostedt
2018-09-18 14:34 ` Daniel Vetter
2018-09-18 14:58 ` Geert Uytterhoeven
2018-09-20 9:12 ` Rafael J. Wysocki
2018-09-20 9:53 ` Daniel Vetter
2018-09-20 10:05 ` Daniel Vetter
2018-09-20 15:57 ` Mark Brown
2018-09-18 14:02 ` James Bottomley
2018-09-18 14:41 ` Daniel Vetter
2018-09-18 19:29 ` Mauro Carvalho Chehab
2018-09-18 19:36 ` Josh Triplett
2018-09-18 19:52 ` Mauro Carvalho Chehab
2018-09-18 20:52 ` Takashi Iwai
2018-09-18 21:15 ` Josh Triplett
2018-09-18 23:06 ` Steven Rostedt
2018-09-18 23:38 ` Laurent Pinchart
2018-09-18 19:58 ` Arnaldo Carvalho de Melo
2018-09-19 11:28 ` James Bottomley
2018-09-19 11:37 ` Mauro Carvalho Chehab
2018-09-19 12:03 ` Mauro Carvalho Chehab
2018-09-19 14:16 ` James Bottomley
2018-09-19 16:06 ` Mauro Carvalho Chehab
2018-09-19 19:55 ` Mauro Carvalho Chehab
2018-09-19 20:10 ` Luck, Tony
2018-09-19 23:28 ` Mauro Carvalho Chehab
2018-09-19 23:45 ` Tim.Bird
2018-09-19 20:23 ` Dave Airlie
2018-09-20 0:01 ` Mauro Carvalho Chehab
2018-09-20 0:22 ` Tim.Bird
2018-09-20 6:33 ` Jani Nikula
2018-09-20 7:01 ` Josh Triplett
2018-09-20 7:11 ` Daniel Vetter
2018-09-20 7:04 ` David Woodhouse
2018-09-24 13:53 ` Mel Gorman
2018-09-25 5:45 ` Leon Romanovsky [this message]
2018-09-20 10:19 ` Laurent Pinchart
2018-09-20 10:23 ` Mauro Carvalho Chehab
2018-09-20 12:31 ` Jani Nikula
2018-09-20 13:04 ` Mauro Carvalho Chehab
2018-09-20 13:49 ` Tim.Bird
2018-09-20 13:55 ` Laurent Pinchart
2018-09-20 19:14 ` Tim.Bird
2018-09-20 19:55 ` Laurent Pinchart
2018-09-20 20:11 ` Dmitry Torokhov
2018-09-20 20:14 ` Jonathan Corbet
2018-09-20 20:52 ` Mauro Carvalho Chehab
2018-09-20 2:44 ` Joe Perches
2018-09-20 11:11 ` Laurent Pinchart
2018-09-20 13:35 ` Joe Perches
2018-09-20 3:38 ` Stephen Hemminger
2018-09-20 12:28 ` Eric W. Biederman
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=20180925054534.GZ3519@mtr-leonro.mtl.com \
--to=leon@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Tim.Bird@sony.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab+samsung@kernel.org \
--cc=mgorman@techsingularity.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).