From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Josef Bacik <josef@toxicpanda.com>, lsf-pc@lists.linuxfoundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-nvme@lists.infradead.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [REMINDER] LSF/MM/BPF: 2022: Call for Proposals
Date: Fri, 25 Feb 2022 07:52:08 -0500 [thread overview]
Message-ID: <c97132f444ddb45dcbd4561df0a0c045dbcc2192.camel@HansenPartnership.com> (raw)
In-Reply-To: <YherWymi1E/hP/sS@localhost.localdomain>
On Thu, 2022-02-24 at 10:59 -0500, Josef Bacik wrote:
> A few updates
>
> - The COVID related restrictions can be found here
>
>
> https://events.linuxfoundation.org/lsfmm/attend/health-and-safety/
>
> - We are working on a virtual component, however it will likely not
> be interactive, likely just a live stream and then an IRC channel to
> ask questions through.
We've been experimenting with hybrid over at plumbers. Our last
experiment at LSS in Seattle managed to get us a successful interactive
two way A/V stream for a live Q and A using Big Blue Button. We
collaborated with E3 on this (The standard LF A/V provider for OSS) so
most likely they'll be who you have in Palm Springs. We were planning
to go for another trial at OSS in Austin, but if you'd like to be our
Guinea Pig, we can put all our infrastructure at your disposal.
Note, your hotel uplink may not support doing this for all four tracks:
we estimate the uplink bandwidth requirement at around 10M per track
dedicated, but we could try it on a single track.
Regards,
James
prev parent reply other threads:[~2022-02-25 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 15:59 [REMINDER] LSF/MM/BPF: 2022: Call for Proposals Josef Bacik
2022-02-25 12:52 ` James Bottomley [this message]
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=c97132f444ddb45dcbd4561df0a0c045dbcc2192.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-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@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).