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 D2B6CA73 for ; Tue, 4 Sep 2018 17:42:44 +0000 (UTC) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8CEB27E0 for ; Tue, 4 Sep 2018 17:42:44 +0000 (UTC) Date: Tue, 4 Sep 2018 10:42:43 -0700 From: Rodrigo Vivi To: ksummit-discuss@lists.linuxfoundation.org Message-ID: <20180904174242.GF2316@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] Challenges in Upstream vs. Embargoed Development in Intel Graphics. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi there, I've submitted a proposal for plumber's referred track. There, I want to talk about tools and challenges we have on embargo development vs upstream one and how to get focus on upstream first and upstream always mentality. The name of plumbers proposal talk is: "Unveiling Intel Graphics Internal Development" I'm not sure if the talk will get accepted, but anyway I'd like to have the chance to talk to other maintainers to exchange views on different ways of maintaining this kind of embargo development including challenges, tools, processes, and rules. So I'm interested in hallway tracks of Maintainer / Kernel Summit, or maybe a bof session if there's interest. Please let me know if there's interested or if further information and/or clarification is needed. Thanks in advance, Rodrigo.