linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Cc: Dave Chinner <david@fromorbit.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Brian Foster <bfoster@redhat.com>,
	Allison Collins <allison.henderson@oracle.com>,
	Amir Goldstein <amir73il@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Chandan Rajendra <chandan@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	djwong@kernel.org, Jan Kara <jack@suse.cz>
Subject: Virtual XFS Developer Meetings
Date: Wed, 22 Apr 2020 15:25:16 -0700	[thread overview]
Message-ID: <20200422222516.GP6749@magnolia> (raw)

Hi everyone,

I propose that we hold our own virtual XFS developer summit.  Physical
proximity is way too risky for the forseeable future, so let's make do
with online discussions and conferencing.  LSFMM 2020 was officially
cancelled a short time ago.

Unlike in-person events, we cannot pin everyone into a single time zone
for an extended meeting, and we can't have a hallway BOF.  On the plus
side, we can finally invite /everyone/ to the table!  Let's use this
email thread to make a list of topics for future discussions.  I can
think of a few topic categories to start:

 1. Development process problems that people would like to address.
 2. Matching patch authors with patch reviewers.
 3. Old features that we ought to retire.
 4. New feature development roadmap.
 5. Anything else that people think is important.

Once we have a list of specific topics matched with people who are
interested in that topic, I think it best to start each of those
conversations in separate threads on linux-xfs where everyone can see
them.  If the participants feel that they'd get more out of an
interactive session, we have plenty of options for doing that:

The first option of course is the IRC channel (#xfs on freenode) from
which it is easy to paste the irc logs into linux-xfs for archiving and
further public comment.

For actual video conferencing, we also have tools such as Jitsi,
BigBlueButton, BlueJeans, and Zoom.  I'm willing to sit in on video
meetings to take notes for linux-xfs and/or post the recordings online.
As a side note for anyone wanting to take advantage of videochats --
I'd prefer to keep this to one hourlong meeting per day.

Please remember this is not an edict passed on from high to shake up
everything; it is merely this maintainer suggesting that we explore
other tactics for building things together.  In the end, everything that
goes into making decisions still must be communicated via linux-xfs, and
patches still have to earn Reviewed-by tags.  We do, however, have
flexibility in how we get there.

Here are some topics that have been mentioned to me at least in passing
over the last few months.  I'll start the first five topics since
they're the ones I was going to put on the agenda for an XFS meeting at
LSFMM until that all blew away.

 - Refactoring the Review Process (me, Eric, Dave)

 - Deferred inode inactivation and nonblocking inode reclaim (me, Amir)

 - 64bit timestamps (me, Amir)

 - Atomic extent swaps (me)

 - Online fsck (me)

 - Deprecating the v4 format (Dave)

 - Parent Pointers (Amir)

 - Range Locks (Amir)

 - DAX bashing session (Dan)

 - Widening the inode fork extent counters (Chandan)

 - Dirty buffer region bitmap tracking (Chandan)

 - Add your pet item here! :)

Thoughts, suggestions, and flames appreciated!

--D

             reply	other threads:[~2020-04-22 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 22:25 Darrick J. Wong [this message]
2020-04-22 23:48 ` [XFS SUMMIT] Virtual XFS Developer Meetings Darrick J. Wong

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=20200422222516.GP6749@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=allison.henderson@oracle.com \
    --cc=amir73il@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=chandan@linux.ibm.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-xfs@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sandeen@redhat.com \
    --cc=willy@infradead.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).