All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: xfs <linux-xfs@vger.kernel.org>, Theodore Ts'o <tytso@mit.edu>,
	Jan Kara <jack@suse.cz>
Subject: Re: xfs office hours meeting minutes
Date: Mon, 19 May 2025 10:52:07 +1000	[thread overview]
Message-ID: <aCqAt3icmqt67ws5@dread.disaster.area> (raw)
In-Reply-To: <20250516233902.GA9705@frogsfrogsfrogs>

On Fri, May 16, 2025 at 04:39:02PM -0700, Darrick J. Wong wrote:
> 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 didn't ask for a transcript of the meeting, nor a detailed
recording of everything that everyone says.

> 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.

However, stuff like LSFMM (and often LPC) has detailed summaries of
each discussion published on the public record by community focussed
organisations like LWN....

> 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.

You're making a big assumption about why I asked this question,
Darrick.

I asked because the time at which the meeting is held is prohibitive
for me to attend, so unless there is some published record, I have
no idea what is happening in the wider XFS community.

Like yourself, I also want to know what everyone is working on, what
knowledge gaps they need filled, where they are getting stuck, what
are the most important problems that need to be solved, etc.

I had assumed, as the person running the meeting, that you would be
keeping notes of these sorts of things for followup purposes. At
minimum, private notes to remind yourself before the next meeting of
what people were struggling with last week. That's really all I was
asking to be published - I certainly don't want or need detailed
everything-he-said-and-she-said recordings of the meetings.

Perhaps that was a bad assumption to make that someone was taking
useful notes, but it never even crossed my mind that you weren't
taking any notes at all during the meeting.

> 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.

Even if the issue is not settled, a summary of the discussion should
be published so everyone knows (or can discover) what has already
been discussed instead of treading the same ground on the mailing
list later on....

> That to me feels like a reasonable
> compromise between the unstructured conversations that occur on the call
> vs. maintaining a public record.

Except for the fact it doesn't provide any of the information I'd
like about what was discussed during the meetings.

-Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2025-05-19  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 23:39 xfs office hours meeting minutes Darrick J. Wong
2025-05-19  0:52 ` Dave Chinner [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=aCqAt3icmqt67ws5@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.