linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Allison Henderson <allison.henderson@oracle.com>,
	Brian Foster <bfoster@redhat.com>,
	Catherine Hoang <catherine.hoang@oracle.com>,
	Dave Chinner <david@fromorbit.com>,
	Eryu Guan <guaneryu@gmail.com>,
	Gao Xiang <hsiangkao@linux.alibaba.com>,
	Christoph Hellwig <hch@infradead.org>,
	Chandan Babu R <chandanrlinux@gmail.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Matthew Wilcox <willy@infradead.org>,
	Bill O'Donnell <billodo@redhat.com>,
	Shiyang Ruan <ruansy.fnst@fujitsu.com>,
	xfs <linux-xfs@vger.kernel.org>
Subject: Re: XFS Sprints
Date: Thu, 16 Sep 2021 11:50:04 +0200	[thread overview]
Message-ID: <20210916095004.elamntoqfmv2gv7w@andromeda.lan> (raw)
In-Reply-To: <20210916023652.GA34820@magnolia>

Hi Darrick.

On Wed, Sep 15, 2021 at 07:36:52PM -0700, Darrick J. Wong wrote:
> Hi again,
> 
> The other problem I sense we're having is implied sole ownership of
> patchesets being developed.  Reviewers make comments, but then it seems
> like it's totally on the developer (as the applicant) to make all those
> changes.  It's ... frustrating to watch new code stall because reviewers
> ask for cleanups and code restructuring that are outside of the original
> scope of the series as a condition for adding a Reviewed-by tag... but
> then they don't work on those cleanups.

Not to mention cases when reviews come 'too late'. A V2 is submitted right
before a new comment on V1, and that creates a V3,4,5....
> 
> At that point, what's a developer to do?  Try to get someone else's
> attention and start the review process all over again?  Try to get
> another maintainer's attention and have them do it?  This last thing is
> hard if you're already a maintainer, because doing that slows /everyone/
> down.
> 
> So the question I have is: Can we do community sprints?  Let's get
> together (on the lists, or irc, wherever) the week after -rc2 drops to
> figure out who thinks they're close to submitting patchsets, decide
> which one or two big patchsets we as a group want to try to land this
> cycle, and then let's /all/ collaborate on making it happen.  If you
> think a cleanup would be a big help for someone else's patchset, write
> those changes and make that part happen.

Despite the fact I particularly don't like the term 'sprint' :) I believe
gathering together from time to time to discuss next steps, is much appreciated.
My experience with the past few years is mostly what you described, everything
is scattered and it's hard to know what to prioritize. At a first I was mostly
thinking it was due my TZ constrains, which usually brings me 'late to the
party' (if I arrive at all :). But with your email, it seems there are more
things in play.
Lately I've been trying to help mostly on reviews, but again, it's usually hard
to know what to review first, so, most of time I feel like randomly picking
stuff on the list to review, unless somebody asks for help reviewing something
specific. So, from a reviewing PoV, this can help a lot what should be reviewed
first.
Also, probably now mostly regarding my TZ, I'm usually oblivious regarding
what's happening, so, I sometimes have a hard time to figure out where I can
give a hand when I have some spare time, maybe these 'meetings' (or whatever
we'll call it) will also help in this case.

Regarding on 'where', may I suggest a single email thread per -rc (or week,
month, whatever)? I'm just being selfish here though, so I don't need to be
on irc late night or early morning :) But if email doesn't work, I'll do what I
can to attend the meetings.

Cheers.

-- 
Carlos


  reply	other threads:[~2021-09-16  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  2:36 Darrick J. Wong
2021-09-16  9:50 ` Carlos Maiolino [this message]
2021-09-16 12:24 ` [External] : " Chandan Babu R
2021-09-16 13:18   ` Carlos Maiolino
2021-09-22 14:01 ` Eric Sandeen

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=20210916095004.elamntoqfmv2gv7w@andromeda.lan \
    --to=cmaiolino@redhat.com \
    --cc=allison.henderson@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=billodo@redhat.com \
    --cc=catherine.hoang@oracle.com \
    --cc=chandanrlinux@gmail.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=hch@infradead.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=sandeen@redhat.com \
    --cc=willy@infradead.org \
    --subject='Re: XFS Sprints' \
    /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

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