linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: lsf-pc <lsf-pc@lists.linuxfoundation.org>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	linux-mm@kvack.org, linux-xfs@vger.kernel.org,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	bpf@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: [LSFMMBPF TOPIC] Killing LSFMMBPF
Date: Fri, 6 Mar 2020 11:08:36 -0500	[thread overview]
Message-ID: <72708005-0810-1957-1e58-5b70779ab6db@toxicpanda.com> (raw)
In-Reply-To: <20200306155611.GA167883@mit.edu>

On 3/6/20 10:56 AM, Theodore Y. Ts'o wrote:
> On Fri, Mar 06, 2020 at 09:35:41AM -0500, Josef Bacik wrote:
>> This has been a topic that I've been thinking about a lot recently, mostly
>> because of the giant amount of work that has been organizing LSFMMBPF.  I
>> was going to wait until afterwards to bring it up, hoping that maybe it was
>> just me being done with the whole process and that time would give me a
>> different perspective, but recent discussions has made it clear I'm not the
>> only one.....
> 
> I suggest that we try to decouple the question of should we have
> LSF/MM/BPF in 2020 and COVID-19, with the question of what should
> LSF/MM/BPF (perhaps in some transfigured form) should look like in
> 2021 and in the future.
> 

Yes this is purely about 2021 and the future, not 2020.

> A lot of the the concerns expressed in this e-mails are ones that I
> have been concerned about, especially:
> 
>> 2) There are so many of us....
> 
>> 3) Half the people I want to talk to aren't even in the room.  This may be a
>> uniquely file system track problem, but most of my work is in btrfs, and I
>> want to talk to my fellow btrfs developers....
> 
>> 4) Presentations....
> 
> These *exactly* mirror the dynamic that we saw with the Kernel Summit,
> and how we've migrated to a the Maintainer's Summit with a Kernel
> centric track which is currently colocated with Plumbers.
> 
> I think it is still useful to have something where we reach consensus
> on multi-subsystem contentious changes.  But I think those topics
> could probably fit within a day or maybe a half day.  Does that sound
> familiar?  That's essentially what we now have with the Maintainer'st
> Summit.
> 
> The problem with Plumbers is that it's really, really full.  Not
> having invitations doesn't magically go away; Plumbers last year had
> to deal with long waitlist, and strugglinig to make sure that all of
> the critical people who need be present so that the various Miniconfs
> could be successful.

Ah ok, I haven't done plumbers in a few years, I knew they would get full but I 
didn't think it was that bad.

> 
> This is why I've been pushing so hard for a second Linux systems
> focused event in the first half of the year.  I think if we colocate
> the set of topics which are currently in LSF/MM, the more file system
> specific presentations, the ext4/xfs/btrfs mini-summits/working
> sessions, and the maintainer's summit / kernel summit, we would have
> critical mass.  And I am sure there will be *plenty* of topics left
> over for Plumbers.
>

I'd be down for this.  Would you leave the thing open so anybody can register, 
or would you still have an invitation system?  I really, really despise the 
invitation system just because it's inherently self limiting.  However I do want 
to make sure we are getting relevant people in the room, and not making it this 
"oh shit, I forgot to register, and now the conference is full" sort of 
situations.  Thanks,

Josef


  reply	other threads:[~2020-03-06 16:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 14:35 Josef Bacik
2020-03-06 15:29 ` Jason Gunthorpe
2020-03-06 15:30 ` [Lsf-pc] " Amir Goldstein
2020-03-06 15:55 ` Josef Bacik
2020-03-06 15:56 ` Theodore Y. Ts'o
2020-03-06 16:08   ` Josef Bacik [this message]
2020-03-06 19:48     ` Theodore Y. Ts'o
2020-03-06 18:30   ` Rik van Riel
2020-03-07 18:54   ` [LSFMMBPF TOPIC] LSFMMBPF 2020 COVID-19 status update Luis Chamberlain
2020-03-07 19:00     ` Josef Bacik
2020-03-07 19:12     ` James Bottomley
2020-03-06 16:04 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Nikolay Borisov
2020-03-06 16:15 ` James Bottomley
2020-03-06 16:28   ` Christian Brauner
2020-03-06 16:31     ` Josef Bacik
     [not found] ` <20200306160548.GB25710@bombadil.infradead.org>
2020-03-06 17:04   ` Al Viro
2020-03-06 17:37   ` James Bottomley
2020-03-06 18:06     ` Jason Gunthorpe
2020-03-06 19:07       ` Martin K. Petersen
2020-03-06 19:15         ` James Bottomley
2020-03-06 19:20           ` Martin K. Petersen
2020-03-06 18:23     ` Matthew Wilcox
2020-03-06 19:25       ` James Bottomley
2020-03-06 19:27 ` [LSFMMBPF TOPIC] long live LFSMMBPF Chris Mason
2020-03-06 19:41   ` James Bottomley
2020-03-06 19:56     ` Chris Mason
2020-03-06 20:25     ` Theodore Y. Ts'o
2020-03-07  3:14 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Steve French
2020-03-10 13:13 ` Michal Hocko
2020-03-10 13:40   ` Josef Bacik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72708005-0810-1957-1e58-5b70779ab6db@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lsf-pc@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox