linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
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 11:29:28 -0400	[thread overview]
Message-ID: <20200306152928.GL31668@ziepe.ca> (raw)
In-Reply-To: <b506a373-c127-b92e-9824-16e8267fc910@toxicpanda.com>

On Fri, Mar 06, 2020 at 09:35:41AM -0500, Josef Bacik wrote:

> 1) The invitation process.  This goes away.  The people/companies that want
> to discuss things with the rest of us can all get to plumbers the normal
> way.  We get new blood that we may miss through the invitation process
> because they can simply register for Plumbers on their own.

At last year at plumbers there were many people who could not get
tickets, it has been full the last few years, I think.

IMHO LPC is about at the size now where it is almost as large as it
can be in a mid-sized hotel setting..

> 4) Planning becomes much simpler.  I've organized miniconf's at plumbers
> before, it is far simpler than LSFMMBPF.  You only have to worry about one
> thing, is this presentation useful.  I no longer have to worry about am I
> inviting the right people, do we have enough money to cover the space.  Is
> there enough space for everybody?  Etc.

LPC does a great job at making miniconfs 'easy' - really fantastic
actually. I really appreciate how great a job they do on getting video
out and trying hard to mic everything so the freewheeling discussions
are audible to everyone.

Maybe something to think about is to keep the LSFMMBPF time slot but
instead of building a conference from scratch, copy LPC - same venue,
contracts, format, etc, etc. Ie two LPC style conferences a year, but
without having to plan two completely different sites from scratch.

IIRC when LPC was in Vancouver the LF used the same venue for several
conferences, I wonder how that worked out?

Jason

  reply	other threads:[~2020-03-06 15:29 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 [this message]
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
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=20200306152928.GL31668@ziepe.ca \
    --to=jgg@ziepe.ca \
    --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).