From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 49AB7E7D for ; Mon, 9 Sep 2019 10:18:03 +0000 (UTC) Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A6EA381A for ; Mon, 9 Sep 2019 10:18:02 +0000 (UTC) Received: by mail-lj1-f181.google.com with SMTP id h2so5645927ljk.1 for ; Mon, 09 Sep 2019 03:18:02 -0700 (PDT) MIME-Version: 1.0 From: Dave Airlie Date: Mon, 9 Sep 2019 20:17:50 +1000 Message-ID: To: ksummit Content-Type: text/plain; charset="UTF-8" Subject: [Ksummit-discuss] vague topic for maintainers summit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.