From: Dave Airlie <airlied@gmail.com>
To: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] vague topic for maintainers summit
Date: Mon, 9 Sep 2019 20:17:50 +1000 [thread overview]
Message-ID: <CAPM=9tx7toB7Bsif6RDo51HNxcGbbHDPHD7DjmF9i+zs-J0HRQ@mail.gmail.com> (raw)
This topic occured to me on one of the planes I've spent time on this
weekend, so it's kinda vague and handwavy.
Methods for constructively saying No to large companies.
I feel it would be best suited for something like maintainer summit as
people can speak freely without causing employer issues.
The idea would be to exchange ideas and discuss how to address large
bodies of code or stacks that are misdesigned or have major issues
that aren't suitable for stable inclusion, or are big additions to
current drivers/layers, being submitted by large corporations with the
expectations that we would land it because they designed it like that.
I'm not sure if other maintainers face this sort of thing as regularly
as I do, but just wondered if there was value in discussing it.
Dave.
next reply other threads:[~2019-09-09 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 10:17 Dave Airlie [this message]
2019-09-09 10:44 ` [Ksummit-discuss] vague topic for maintainers summit James Bottomley
2019-09-09 11:53 ` Mark Brown
2019-09-09 12:01 ` James Bottomley
2019-09-09 12:18 ` Mark Brown
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='CAPM=9tx7toB7Bsif6RDo51HNxcGbbHDPHD7DjmF9i+zs-J0HRQ@mail.gmail.com' \
--to=airlied@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).