linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Josef Bacik <josef@toxicpanda.com>,
	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, 06 Mar 2020 08:15:10 -0800	[thread overview]
Message-ID: <1583511310.3653.33.camel@HansenPartnership.com> (raw)
In-Reply-To: <b506a373-c127-b92e-9824-16e8267fc910@toxicpanda.com>

On Fri, 2020-03-06 at 09:35 -0500, Josef Bacik wrote:
> Many people have suggested this elsewhere, but I think we really need
> to seriously consider it.  Most of us all go to the Linux Plumbers
> conference.  We could accomplish our main goals with Plumbers without
> having to deal with all of the above problems.

[I'm on the Plumbers PC, but not speaking for them, just making general
observations based on my long history helping to run Plumbers]

Plumbers has basically reached the size where we can't realistically
expand without moving to the bigger venues and changing our evening
events ... it's already been a huge struggle in Lisbon and Halifax
trying to find a Restaurant big enough for the closing party.

The other reason for struggling to keep Plumbers around 500 is that the
value of simply running into people and having an accidental hallway
track, which is seen as a huge benefit of plumbers, starts diminishing.
 In fact, having a working hallway starts to become a problem as well
as we go up in numbers (plus in that survey we keep sending out those
who reply don't want plumbers to grow too much in size).

The other problem is content: you're a 3 day 4 track event and we're a
3 day 6 track event.  We get enough schedule angst from 6 tracks ... 10
would likely become hugely difficult.  If we move to 5 days, we'd have
to shove the Maintainer Summit on the Weekend (you can explain that one
to Linus) but we'd still be in danger of the day 4 burn out people used
to complain about when OLS and KS were co-located.

So, before you suggest Plumbers as the magic answer consider that the
problems you cite below don't magically go away, they just become
someone else's headache.

That's not to say this isn't a good idea, it's just to execute it we'd
have to transform Plumbers and we should have a community conversation
about that involving the current Plumbers PC before deciding it's the
best option.

James


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

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 14:35 [LSFMMBPF TOPIC] Killing LSFMMBPF 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
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:05 ` Matthew Wilcox
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 16:15 ` James Bottomley [this message]
2020-03-06 16:28   ` Christian Brauner
2020-03-06 16:31     ` Josef Bacik
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=1583511310.3653.33.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bpf@vger.kernel.org \
    --cc=josef@toxicpanda.com \
    --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 \
    /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;
as well as URLs for NNTP newsgroup(s).