From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Luis Chamberlain <mcgrof@kernel.org>,
lsf-pc@lists.linux-foundation.org,
xfs <linux-xfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Chandan Babu R <chandan.babu@oracle.com>, Jan Kara <jack@suse.cz>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: [Lsf-pc] XFS BoF at LSFMM
Date: Thu, 9 May 2024 10:47:45 -0700 [thread overview]
Message-ID: <20240509174745.GO360919@frogsfrogsfrogs> (raw)
In-Reply-To: <CAOQ4uxiX=O8NhonBv2Yt6nu4ZiqTLBUZg+M5r0T-ZO5LC=a2dQ@mail.gmail.com>
On Thu, May 09, 2024 at 08:29:19PM +0300, Amir Goldstein wrote:
> On Thu, May 9, 2024 at 6:55 PM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > [adds ritesh to cc]
> >
> > On Thu, May 09, 2024 at 08:23:25AM +0300, Amir Goldstein wrote:
> > > On Thu, May 9, 2024 at 8:06 AM Christoph Hellwig <hch@infradead.org> wrote:
> > > >
> > > > On Thu, May 09, 2024 at 08:01:39AM +0300, Amir Goldstein wrote:
> > > > >
> > > > > FYI, I counted more than 10 attendees that are active contributors or
> > > > > have contributed to xfs in one way or another.
> > > > > That's roughly a third of the FS track.
> > > >
> > > > FYI, I'm flying out at 4:15pm on Wednesday, and while I try to keep my
> > > > time at the airport short I'd still be gone by 3:30.
> > >
> > > I've penciled XFS BoF at 2:30
> >
> > Ritesh and Ted and Jan and I were chatting during the ext4 concall just
> > now. Could we have a 30 minute iomap bof at 2:30pm followed by the XFS
> > bof after that? That would give us some time to chat with hch about
> > iomap (and xfs) direction before he has to leave.
> >
> > Alternately, we could announce a lunchtime discussion group on Monday
> > following Ritesh's presentation about iomap. That could fit everyone's
> > schedule better? Also everyone's braincaches will likely be warmer.
> >
>
> Seems to me that there will be a wider interest in iomap BoF
> Not sure what you mean by lunchtime discussion.
Monday 90-minute lunch is posted as being in "Grand ballroom C", so I
would tell everyone to come find the table(s) I'm sitting at for a
discussion over lunch. We can move out to a hallway after everyone's
done eating.
> We can move Willy's GFP_NOFS talk to 15:30 and have the iomap BoF
> after Ritesh's session.
<shrug> If you like, though I don't think it's totally necessary. But
you might have a better idea of what the venue is like than I do, so
I'll let you make that call. :)
> > > >
> > > > But that will only matter if you make the BOF and actual BOF and not the
> > > > usual televised crap that happens at LSFMM.
> > > >
> > >
> > > What happens in XFS BoF is entirely up to the session lead and attendees
> > > to decide.
> > >
> > > There is video in the room, if that is what you meant so that remote attendees
> > > that could not make it in person can be included.
> > >
> > > We did not hand out free virtual invites to anyone who asked to attend.
> > > Those were sent very selectively.
> > >
> > > Any session lead can request to opt-out from publishing the video of the
> > > session publicly or to audit the video before it is published.
> > > This was the same last year and this year this was explicitly mentioned
> > > in the invitation:
> > >
> > > "Please note: As with previous years there will be an A/V team on-
> > > site in order to facilitate conferencing and help with virtual
> > > participants. In order to leave room for off-the-record discussions
> > > the storage track completely opts out of recordings. For all other
> > > tracks, please coordinate with your track leads (mentioned below)
> > > whether a session should explicitly opt-out. This can also be
> > > coordinated on-site during or after the workshop. The track leads
> > > then take care that the given session recording will not be
> > > published."
> > >
> > > I will take a note to keep XFS BoF off the record if that is what you
> > > want and if the other xfs developers do not object.
> >
> > Survey: How many people want to attend the xfs bof virtually?
> >
> > I'd be ok with an OTR discussion with no video, though I reserve the
> > right to change my mind if the score becomes chair: 2 djwong: 0. :P
>
> The middle ground is to allow video for the selective virtual attendees
> (and trust them not to record and publish) and not publish the video
> on LSMFF site.
I didn't know that was also an option; I'll keep that in mind.
--D
> Thanks,
> Amir.
>
next prev parent reply other threads:[~2024-05-09 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 19:41 XFS BoF at LSFMM Luis Chamberlain
2024-05-09 5:01 ` [Lsf-pc] " Amir Goldstein
2024-05-09 5:05 ` Christoph Hellwig
2024-05-09 5:23 ` Amir Goldstein
2024-05-09 15:55 ` Darrick J. Wong
2024-05-09 15:59 ` Christoph Hellwig
2024-05-09 17:29 ` Amir Goldstein
2024-05-09 17:47 ` Darrick J. Wong [this message]
2024-05-13 13:48 ` Theodore Ts'o
2024-05-13 22:33 ` Darrick J. Wong
2024-05-09 9:09 ` Ritesh Harjani
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=20240509174745.GO360919@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ritesh.list@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).