[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181008163243.72825e05@coco.lan>
Date: Mon, 8 Oct 2018 16:32:43 -0300
From: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To: Dave Airlie <airlied@...il.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
James Bottomley <James.Bottomley@...senpartnership.com>,
LKML <linux-kernel@...r.kernel.org>,
ksummit <ksummit-discuss@...ts.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the
ambiguity about collecting email addresses
Em Mon, 8 Oct 2018 09:37:59 +1000
Dave Airlie <airlied@...il.com> escreveu:
> On Mon, 8 Oct 2018 at 08:56, Al Viro <viro@...iv.linux.org.uk> wrote:
> >
> > On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote:
> >
> > > This isn't a legally binding license or anything, but departing from
> > > the upstream wording makes it tricker to merge new upstream versions
> > > if they are considered appropriate.
> >
> > Nicely done, that - gotta love the passive voice use. Considered appropriate
> > *by* *whom*?
>
> Good question, do we have a CoC maintainer? Is Linus it, Greg, TAB?
>
> Maybe step one is to find the person who can make changes to the
> kernel CoC (has anyone checked if Linus or Greg will merge this).
If we add it to the MAINTAINERS file (with makes perfect sense to me),
I would like to have a R: entry there, in order to be notified when
people propose changes to it. My personal understanding is that it may
have legal value under the legislation of the Country I live, and I'd
like to understand changes there that might affect my workflow.
Thanks,
Mauro
Powered by blists - more mailing lists