From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Luis Chamberlain <mcgrof@kernel.org>, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: 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] LSFMMBPF 2020 COVID-19 status update
Date: Sat, 07 Mar 2020 11:12:18 -0800 [thread overview]
Message-ID: <1583608338.20291.28.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200307185420.GG2236@42.do-not-panic.com>
On Sat, 2020-03-07 at 18:54 +0000, Luis Chamberlain wrote:
> On Fri, Mar 06, 2020 at 10:56:11AM -0500, Theodore Y. Ts'o wrote:
> > Should we have LSF/MM/BPF in 2020 and COVID-19?
[...]
> If we have to learn from efforts required to continue on with the in
> light of the risks, we can look at what SCALE 18 is doing, taking
> place right now in Pasadena [1], their page lists a list of proactive
> measures required on their part to help alleviate fears and just good
> best practices at this point in time.
I agree Scale18x is the poster child for following WHO advice to the
letter, but there are crucial differences:
1. Scale18x has a lot of local attendees, so the conference can go
ahead somewhat easily with local content and local attendees. We
have no-one for LSF/MM/BPF in Palm Springs.
2. Scale18x did have some issues with non-local content because of
corporate travel bans. The whole of LSF/MM/BPF is non-local content
and would thus be significantly disrupted.
The big problem with 2. is that a lot of corporate policies at the
moment are unconsidered blanket bans. Even corporations who do
consider better might still be stricter than the WHO advice. So my
company, IBM, is saying events >1000 cancel and events <1000 use your
own discretion provided they're promising to obey all the health
guidelines. If I'd been presenting at Scale18x I'd have had to cancel,
even though under our guidelines I can still go to LSF/MM/BPF
> The landscape seems positive, if we want, to move forward in Palm
> Springs then.
For a counter example, just look at the LF Member summit which was due
to happen just after Scale18x:
https://events.linuxfoundation.org/lf-member-summit/
and that's a smaller event than Scale18x. Remember too that the LF
runs LSF/MM so if they decide to cancel, there's not much the
organizing committee can do about it.
James
next prev parent reply other threads:[~2020-03-07 19:12 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 [this message]
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=1583608338.20291.28.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 \
--cc=mcgrof@kernel.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