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 025AAB43 for ; Thu, 20 Apr 2017 08:53:10 +0000 (UTC) Received: from galahad.ideasonboard.com (galahad.ideasonboard.com [185.26.127.97]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DE243144 for ; Thu, 20 Apr 2017 08:53:08 +0000 (UTC) From: Laurent Pinchart To: Julia Lawall Date: Thu, 20 Apr 2017 11:54:09 +0300 Message-ID: <1648500.9LFy3DivI0@avalon> In-Reply-To: References: <20170419201429.GA17383@cloud> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: ksummit , Dave Airlie , Greg Kroah-Hartman , David Miller , Doug Ledford , Ingo Molnar Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Julia, On Thursday 20 Apr 2017 07:44:14 Julia Lawall wrote: > > I'd definitely like to see an "issues that affect casual/occasional > > contributors" discussion; it wouldn't really fit the maintainer summit, > > but I like James' suggestion of doing it as part of the attached > > LinuxCon. > > I would be happy to help with the organization of such a thing. Given Daniel Vetter's point that no single conference will cover a wide enough audience, I've been thinking of trying to gather feedback from a larger audience beforehand that could be be used as material for a LinuxCon EU kernel track round table session. If that idea gets traction, help will definitely be more than welcome. > > In terms of framing, though, I'd suggest keeping it focused on "what > > issues have you personally encountered or directly observed", rather > > than "what random process ideas do you have". The latter would go > > downhill very quickly; the former seems much more likely to produce > > productive feedback on real problems. (It's less important that they > > come with potential solutions than that the relevant problems get > > recorded for subsequent consideration.) > > > > Will the maintainer summit occur *after* the overlapped conference, or > > *before*? If after, then it'd be plausible to have a "let's talk about > > what we heard" session in the maintainer summit. -- Regards, Laurent Pinchart