From: Amir Goldstein <amir73il@gmail.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: lsf-pc@lists.linux-foundation.org, kdevops@lists.linux.dev,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-cxl@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: kdevops BoF at LSFMM
Date: Wed, 8 May 2024 10:45:33 +0300 [thread overview]
Message-ID: <CAOQ4uxigKrtZwS4Y0CFow0YWEbusecv2ub=Zm2uqsvdCpDRu1w@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6XyLS1TaAcgzSWa=1pgezRjFoy8nuVtSWSfB8Qsdsx_xQ@mail.gmail.com>
On Tue, May 7, 2024 at 9:44 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> Dear LPC session leads,
>
> We'd like to gather together and talk about current ongoing
> developments / changes on kdevops at LSFMM. Those interested in
> automation on complex workflows with kdevops are also welcomed. This
> is best addressed informally, but since I see an open slot for at
> 10:30am for Tuesday, figured I'd check to see if we can snatch it.
The empty slot is there for flexibility of the schedule and also
wouldn't storage/MM people be interested in kdevops?
I've placed you session instead of the FS lightning talks on Tuesday
after Leah's FS testing session.
There are enough slots for FS lightning talks.
There are several empty slots throughout the agenda left for
flexibility, including the one you mentioned on Tue morning.
kdevops session is for a very specialized group of developers,
so if that group is assembled and decides to use an earlier slot
we can do that on the spot.
> BoFs for filesystems are scheduled towards the end of the conference
> on Wednesday it seems, so ideally this would just take place then, but
> the last BoF for XFS at Linux Plumbers took... 4 hours, and if such
> filesystem BoFs take place I suspect each FS developer would also want
> to attend their own respective FS BoF...
I certainly hope that FS maintainers will use this gathering to have
their own respective BoFs.
If anyone would like to lead an FS BoF in the FS track room,
please let me know and I will place it on the agenda.
Thanks,
Amir.
next prev parent reply other threads:[~2024-05-08 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 18:44 kdevops BoF at LSFMM Luis Chamberlain
2024-05-07 18:56 ` Chuck Lever III
2024-05-08 7:45 ` Amir Goldstein [this message]
2024-05-08 15:57 ` Luis Chamberlain
2024-05-13 1:58 ` Matthew Wilcox
2024-05-08 17:45 ` Steve French
2024-05-08 17:54 ` Chuck Lever III
2024-05-12 20:20 ` Luis Chamberlain
2024-05-13 13:17 ` Theodore Ts'o
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='CAOQ4uxigKrtZwS4Y0CFow0YWEbusecv2ub=Zm2uqsvdCpDRu1w@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).