bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Josef Bacik <josef@toxicpanda.com>
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 08:05:48 -0800	[thread overview]
Message-ID: <20200306160548.GB25710@bombadil.infradead.org> (raw)
In-Reply-To: <b506a373-c127-b92e-9824-16e8267fc910@toxicpanda.com>

On Fri, Mar 06, 2020 at 09:35:41AM -0500, Josef Bacik wrote:
> [a lot of stuff I agree with]

> 4) Presentations.  90% of the conference is 1-2 people standing at the front
> of the room, talking to a room of 20-100 people, with only a few people in
> the audience who cares.  We do our best to curate the presentations so we're
> not wasting peoples time, but in the end I don't care what David Howells is
> doing with mount, I trust him to do the right thing and he really just needs
> to trap Viro in a room to work it out, he doesn't need all of us.

... and allow the other 3-5 people who're interested or affected the
opportunity to sit in.  Like a mailing list, but higher bandwidth.

> So what do I propose?  I propose we kill LSFMMBPF.

I come not to bury LSFMMBPF but to reform it.

As Jason noted, Plumbers is already oversubscribed.  I think having two
Plumbers conferences per year (one spring, one autumn), preferably on
two different continents, would make a lot of sense.

Here's my proposal, and obviously I'm not seeking _permission_ to do
this, but constructive feedback would be useful.

1. Engage an event organiser to manage the whole thing.  I have a friend
who recently took up event organising as her full-time job, and I've
started talking to her about this.  It's a rather different skill-set
from writing kernel patches.

2. Charge attendees $300 for a 3-day conference.  This seems to be the
going rate (eg BSDCan, PGCon).  This allows the conference to be self-
funding without sponsors, and any sponsorship can go towards evening
events, food, travel bursaries, etc.

3. Delegate organising the sessions to the track chairs.  Maybe get rid
of shared sessions altogether -- while there are plenty of times where
"I need fs and mm people in the room", it's rarely "I need everybody in
the room", and scheduling BOFs opposite such a general session would be
a good use of peoples time.


  parent reply	other threads:[~2020-03-06 16:05 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 [this message]
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
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=20200306160548.GB25710@bombadil.infradead.org \
    --to=willy@infradead.org \
    --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).