Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp7204356ybf; Fri, 6 Mar 2020 12:26:37 -0800 (PST) X-Google-Smtp-Source: ADFU+vsvwcLgqUoAigpdOe5Iqf5amfUtyRup5BVKy5RywgjL8nhrexzMP2K4vG9FCU/rnOXIGPow X-Received: by 2002:aca:5303:: with SMTP id h3mr3858403oib.74.1583526397381; Fri, 06 Mar 2020 12:26:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583526397; cv=none; d=google.com; s=arc-20160816; b=dfh+R9MkQUFmytBDRTHvTo8U/vuFyeSkkxuGhlRuKhjAuu8OV0fDanwV3LzufBy74F kZbqv8hLgNUjs7YM5A9qVyddMIP+o1vAob41abexChnD413MuwdbmbAj9C7Da5iee/FF 3L5694MsgX+n+Mrcvuhtn1GzxZw570jve7an6NnRP8Ph9Q7+Q35T4QE5V+ge72B7kkLv veAS9AzwyRudX23tMtmSLc/lbTpM+dke9in3ud6Jo38Efbpi0Cn39i1b2i63Hcvvu9MB 1vzLJcby9FxL5TbRS5l5E7MKQIA7qAFytd4FLNAVI2dAKnwbhkkXwKQcL22eGds4V1V5 mCEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=zdBQPAlhEfieaOONKDkDkKLE0s2QhMU+De7/qk+QJ8w=; b=1EqSFJ4whQAzZm106OwuI9nWn423Ges0BqJvFHj+K+T8NrMttix0+932Bb/dBcQDfw hL1LsgDBHmWToOI6EzlyflMLWBNpI2s2VpCguaXeHXpQB4o6r3hIcNjG5JOjoWl75i5g OPUTfvG9XYpl/uNLB/6fCB8YhYSKC1poXMiRDF7AIHXv9Po3GFxBC60OvArcldks7SJd iZkHJJ8EVqF+I21EBlu18+Fzv5AYG6eRxwCazLKMyvONoRcyxcMKvPA1EBTaE8V4tlxA akSIUi+5nQKgZ1U7cCyyoRS0loHY1eKAlsgG6JIV7kWStNXaexJmKhQ6lsH+mf1BBBrx 5M3A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m1si2046721otn.271.2020.03.06.12.26.22; Fri, 06 Mar 2020 12:26:37 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726245AbgCFU0H (ORCPT + 99 others); Fri, 6 Mar 2020 15:26:07 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:47118 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725873AbgCFU0H (ORCPT ); Fri, 6 Mar 2020 15:26:07 -0500 Received: from callcc.thunk.org (guestnat-104-133-0-105.corp.google.com [104.133.0.105] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 026KPXT6005112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 6 Mar 2020 15:25:34 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 113E242045B; Fri, 6 Mar 2020 15:25:33 -0500 (EST) Date: Fri, 6 Mar 2020 15:25:32 -0500 From: "Theodore Y. Ts'o" To: James Bottomley Cc: Chris Mason , Josef Bacik , lsf-pc , Linux FS Devel , linux-mm@kvack.org, linux-xfs@vger.kernel.org, Btrfs BTRFS , bpf@vger.kernel.org, linux-ext4@vger.kernel.org, linux-block@vger.kernel.org Subject: Re: [LSFMMBPF TOPIC] long live LFSMMBPF Message-ID: <20200306202532.GC12490@mit.edu> References: <76B62C4B-6ECB-482B-BF7D-95F42E43E7EB@fb.com> <1583523705.3653.94.camel@HansenPartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1583523705.3653.94.camel@HansenPartnership.com> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Fri, Mar 06, 2020 at 11:41:45AM -0800, James Bottomley wrote: > And, for everyone who gave us feedback in the Plumbers surveys that co- > locating with a big conference is *not* what you want because of > various problems like hallway track disruptions due to other conference > traffic and simply the difficulty of finding people, the current model > under consideration is one conference organization (the LF) but two > separate venues, sort of like OpenStack used to do for their big > conference and design summit to minimize disruption and increase > developer focus. Ths is what I tried to push last year, which was to colocate LSF/MM and KS/MS in Austin, at the same time as OSS 2020, but in a separate hotel so we didn't have to deal with the cast of thousands which go to OSS. I also liked it because OSS 2020 is in June, so it would have been from a spacing perspective it would have been an easy way to start moving MS/KS from the second half of the year into first half of the year. But some folks pointed out (not without reason), that Palm Springs was a lot more fun than Austin, and OSS still has a somewhat bad reputation of having some really trashy talks, and so even in separate venue, there were people who really didn't like the idea. Because of this, when the LF (in December 2019) suggested moving the MS/KS to Austin as part of OSS, I didn't think we would have critical mass to overcome the reputation of talks like "#OSSummit: Seven Properties of Highly Secure IoT." and so I told Angela, "No, we really can't do this without something like LSF/MM to make sure we have critical mass for a second Linux systems conference." - Ted