From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: XFS Developers' Meeting @ LSFMM?
Date: Thu, 19 Apr 2018 22:57:21 +0200 [thread overview]
Message-ID: <20180419205721.GA15670@wotan.suse.de> (raw)
In-Reply-To: <CAOQ4uxgmq0qiS=rvNnJ39_UJw1yVM4etW3MnnpF3M6mSiyORMQ@mail.gmail.com>
On Thu, Apr 19, 2018 at 11:49:38AM +0300, Amir Goldstein wrote:
> On Thu, Apr 19, 2018 at 5:02 AM, Darrick J. Wong
> <darrick.wong@oracle.com> wrote:
> > Hi all,
> >
> > (Hey LSF PC committee, could we have a community group meeting slot,
> > please? Probably no more than 45 minutes to an hour.)
> >
> > For those of you who will be at LSFMM next week, I was thinking about
> > having a short meeting for all XFS developers at some point during the
> > three days that we'll all (mostly) be there.
> >
> > Here's a rough agenda for such a meeting:
> >
> > 0. Meet & greet, PGP keysigning[2]
> > 1. How are the maintainers doing? How are everybody feeling?
> > 2. What to do about the review backlog...
> > 3. How to help grow new people
> > 4. Roadmap for the next year!
>
> 5. Wanted! stable maintainer for XFS.
I second this topic 5 as of interest.
> >
> > How's that sound? I welcome all topic suggestions beyond the five here.
> > I don't have a good idea for a timeslot yet, other than perhaps one of
> > the empty FS slots on the schedule? Or during lunch or before dinner if
> > they can't make room?
> >
> > Anyway, if you're interested, please reply to this thread.
>
> I'd love to join.
Ditto.
Luis
next prev parent reply other threads:[~2018-04-19 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 2:02 XFS Developers' Meeting @ LSFMM? Darrick J. Wong
2018-04-19 4:24 ` Allison Henderson
2018-04-19 8:49 ` Amir Goldstein
2018-04-19 20:57 ` Luis R. Rodriguez [this message]
2018-04-21 7:38 ` Christoph Hellwig
2018-04-19 14:45 ` [Lsf-pc] " Rik van Riel
2018-04-21 15:36 ` 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=20180419205721.GA15670@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 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.