linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Chris Mason <clm@fb.com>, 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] long live LFSMMBPF
Date: Fri, 06 Mar 2020 11:41:45 -0800	[thread overview]
Message-ID: <1583523705.3653.94.camel@HansenPartnership.com> (raw)
In-Reply-To: <76B62C4B-6ECB-482B-BF7D-95F42E43E7EB@fb.com>

On Fri, 2020-03-06 at 14:27 -0500, Chris Mason wrote:
> On 6 Mar 2020, at 9:35, Josef Bacik wrote:
[...]
> > 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.
> 
> We’ve talked about working closely with KS, Plumbers and the 
> Linuxfoundation to make a big picture map of the content and
> frequency  for these confs.

And, lest anyone think we all operate in isolation, we do get together
periodically to discuss venues, selection and combination.  The last
big in-person meeting on this topic was at Plumbers in Vancouver in
2019, where we had Plumbers, KS/MS, LSF/MM and the LF conference people
all represented.

>   I’m sure Angela is having a busy few weeks, but lets work with her
> to schedule this and talk it through.  OSS is a good fit  in terms of
> being flexible enough to fit us in, hopefully we can make  that work.

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.

James



  reply	other threads:[~2020-03-06 19:41 UTC|newest]

Thread overview: 30+ 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: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 [this message]
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=1583523705.3653.94.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bpf@vger.kernel.org \
    --cc=clm@fb.com \
    --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).