From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Joe Perches <joe@perches.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] New CoC and Brendan Eich
Date: Fri, 05 Oct 2018 13:55:08 +0300 [thread overview]
Message-ID: <30174536.pKSdSEBCyq@avalon> (raw)
In-Reply-To: <f50648a51c98e50748e75d4cc4017214e4e37a9d.camel@perches.com>
Hi Joe,
On Friday, 5 October 2018 13:45:01 EEST Joe Perches wrote:
> On Fri, 2018-10-05 at 12:57 +0300, Laurent Pinchart wrote:
> > Only when the necessary discussions will have taken place, and a decision
> > on how to address the concerns taken, should we then decide whether to
> > fork or contribute upstream.
>
> It's not necessarily am either/or, nor is it
> up to this downstream to decide for upstream.
>
> Upstream may or may not want to change to what
> this community decides is best for itself.
We agree on this, I should have been more precised and said that we could then
device to submit proposals upstream if we deem them to be applicable, but
there's certainly no guarantee that upstream would accept them.
I also want to note that, while I believe our community should decide what is
best for itself, there have been lots of work done on codes of conducts in the
past, and it would seem equally erroneous to me to ignore that and think we
can do better by ourselves with very little experience in the area. Discussing
proposed changes with upstream has the potential to bring interesting
feedback, even if upstream isn't interested in accepting the change proposals.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-10-05 10:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 16:23 jonsmirl
2018-10-04 18:33 ` Laurent Pinchart
2018-10-04 19:05 ` jonsmirl
2018-10-04 19:21 ` Rodrigo Vivi
2018-10-04 19:53 ` jonsmirl
2018-10-05 7:21 ` Geert Uytterhoeven
2018-10-08 21:35 ` Mauro Carvalho Chehab
2018-10-08 23:20 ` Rodrigo Vivi
2018-10-09 10:07 ` Mauro Carvalho Chehab
2018-10-09 15:59 ` Rodrigo Vivi
2018-10-09 16:52 ` Chris Mason
2018-10-09 22:03 ` Dan Williams
2018-10-10 6:47 ` Geert Uytterhoeven
2018-10-10 13:57 ` Mauro Carvalho Chehab
2018-10-10 17:21 ` Josh Triplett
2018-10-10 18:28 ` Mauro Carvalho Chehab
2018-10-10 19:56 ` Josh Triplett
2018-10-10 20:12 ` Mauro Carvalho Chehab
2018-10-10 20:17 ` Josh Triplett
2018-10-04 19:34 ` Laurent Pinchart
2018-10-04 20:39 ` Al Viro
2018-10-04 20:56 ` Jonathan Corbet
2018-10-04 21:27 ` Thomas Gleixner
2018-10-04 22:04 ` Jonathan Corbet
2018-10-05 16:03 ` Theodore Y. Ts'o
2018-10-04 22:05 ` Tim.Bird
2018-10-05 6:23 ` Christoph Hellwig
2018-10-05 7:12 ` Geert Uytterhoeven
2018-10-05 7:50 ` Josh Triplett
2018-10-05 9:20 ` Jani Nikula
2018-10-05 9:57 ` Laurent Pinchart
2018-10-05 10:45 ` Joe Perches
2018-10-05 10:55 ` Laurent Pinchart [this message]
2018-10-05 12:59 ` Jani Nikula
2018-10-05 13:09 ` Laurent Pinchart
2018-10-05 15:17 ` James Bottomley
2018-10-05 18:28 ` Josh Triplett
2018-10-05 18:39 ` James Bottomley
2018-10-04 20:57 ` Josh Triplett
2018-10-05 7:16 ` Geert Uytterhoeven
2018-10-05 7:51 ` Josh Triplett
2018-10-05 8:00 ` Geert Uytterhoeven
2018-10-05 8:44 ` Josh Triplett
2018-10-05 15:26 ` 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=30174536.pKSdSEBCyq@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linuxfoundation.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