From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs <linux-xfs@vger.kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Jan Kara <jack@suse.cz>
Subject: xfs office hours meeting minutes
Date: Fri, 16 May 2025 16:39:02 -0700 [thread overview]
Message-ID: <20250516233902.GA9705@frogsfrogsfrogs> (raw)
Hi everyone,
For background, Dave asked this on IRC on Tuesday:
[15:03] <dchinner> djwong: can you publish updated minutes for what is
discussed during the office hours meeting?
After a couple of days of doing some research and thinking about this,
I've decided that the answer is no, I cannot simultaneously facilitate
the meeting /and/ produce a detailed minute-by-minute record of what was
discussed. I welcome someone volunteering to function as a scribe,
though I'll note that for most of the other community meetings (e.g.
LSFMM, LPC, etc) minutes are not produced.
Like the ext4 community call, the weekly hour is spent on asking fairly
mundane procedure questions of the release managers, people asking
questions when they get stuck, a roundtable of what everyone's working
on, and discussion of ideas. This last thing is what I gather is the
sticking point -- people are allergic to backroom settlement of
conflicts that everyone is then bound to live with.
For those situations, I prefer to roughly follow the practice of ext4
community call. To my observation, that practice is that if we think
we've settled a question, then a summary of that discussion will be sent
to the list for broader examination. That to me feels like a reasonable
compromise between the unstructured conversations that occur on the call
vs. maintaining a public record.
Also, for people who have been attending the calls, I have numerous
conflicts for the next month or two, so the next office hours will be:
May 20
June 10
July 1
(and back to weekly starting July 1)
--D
next reply other threads:[~2025-05-16 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 23:39 Darrick J. Wong [this message]
2025-05-19 0:52 ` xfs office hours meeting minutes Dave Chinner
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=20250516233902.GA9705@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-xfs@vger.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