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 3D1D1932 for ; Wed, 24 Aug 2016 18:24:28 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id C8231272 for ; Wed, 24 Aug 2016 18:24:27 +0000 (UTC) Message-ID: <1472063065.2545.12.camel@HansenPartnership.com> From: James Bottomley To: Greg KH , David Woodhouse Date: Wed, 24 Aug 2016 14:24:25 -0400 In-Reply-To: <20160824174724.GE30853@kroah.com> References: <20160824130832.GA28564@kroah.com> <1472052583.61594.577.camel@infradead.org> <20160824174724.GE30853@kroah.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] GPL defense issues List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , We're getting off into the weeds on this. The question is whether there's an interest among the attendees of KS in hearing about this type of thing. Based on the feedback from Christoph's session last year and some of the replies to this thread, I'd say there is. There is an argument that we shouldn't do this because it expands our exposure to legal jeopardy ... if you want to argue on that tack, I'm listening. Dragging up employers not liking it is a red herring: last year's session was organised very late and some employer's did veto their developers attending (like yours), but the resolution was simple: you didn't stay in the room. Anyone whose employer orders them to stay away can do the same. We can make sure to have the same warnings we had last year, so I don't really see the employer angle being an objection to holding a GPL session at KS. One of the good things about last years session was that I think we did get an embryo of a process to actually share this type of information responsibly with the kernel community and that enabled more information to be discussed reliably. James