From: Richard Weinberger <richard@nod.at>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Marek Vasut <marex@denx.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
nicolas.ferre@atmel.com,
Boris Brezillon <boris.brezillon@free-electrons.com>,
LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Subject: Re: [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR subsystem
Date: Tue, 18 Oct 2016 21:02:27 +0200 [thread overview]
Message-ID: <09ac9f8a-d6a0-97a8-c73a-ffb53bc1a4c8@nod.at> (raw)
In-Reply-To: <20161018184651.GA71760@google.com>
Brian,
On 18.10.2016 20:46, Brian Norris wrote:
>>> I totally agree with you so if Marek and you volunteer as well, your help
>>> will be precious!
>>
>> Well, my SPI-NOR fu is not strong. And UBI/UBIFS keeps me busy.
>> But if Brian likes the idea of having a MTD maintainer team I'll offer my help.
>
> I think a MTD maintainer team would be good to try, and I think it might
> help to resolve my above complaint; a maintainer team could help to make
> sure that everything can be coordinated in one tree + pull request,
> without adding too many extra points of failure (e.g., so we don't have
> awesome SPI NOR and NAND trees get bogged down by a slow MTD pull).
>
> Random thoughts:
>
> Does it make sense to still use infradead.org? We'd need to add a few
> users there.
What else do you have in mind? kernel.org?
As long all users with commit access are member of the kernel.org web of
trust any host should be fine.
> Trust? I have met most of you in person, but not all, and I don't have
> signed keys from all of you. I don't know what the best way to get a
> group-writeable repo with credentials for all of you that we can trust.
> (FWIW, neither Artem nor David met me, but they saw it fit to grant me
> infradead.org access ;) )
I'd go with the kernel.org web of trust.
> Coordination: how do we avoid stepping on each other's toes? We'd have
> to definitely 100% kill 'git push -f' and 'git rebase'. Also, would
> patchwork help or hurt us here? I think Boris and I have been sort of
> using it, but it's still got a pretty good backlog (partly real --
> i.e., the cause for this thread; and partly artificial, due to
> accounting).
patchwork should be a good start. We could also try the tip scripts used
by the x86 maintainer team.
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/tree/.tip?h=tip
> What to do about mtd-utils.git? That's been languishing a bit, and it
> has no release schedule. Maybe we want a plan for that too.
I'd volunteer to nurse it together with David Oberhollenzer.
In fact, David is currently preparing a v2 pre-release of mtd-utils.
https://github.com/sigma-star/mtd-utils/commits/wip_v2-rc1
We reworked a lot of code and added new tools.
Thanks,
//richard
next prev parent reply other threads:[~2016-10-18 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:58 Cyrille Pitchen
2016-10-18 15:17 ` Marek Vasut
2016-10-18 15:30 ` Richard Weinberger
2016-10-18 15:55 ` Cyrille Pitchen
2016-10-18 16:15 ` Richard Weinberger
2016-10-18 16:37 ` Marek Vasut
2016-10-18 18:46 ` Brian Norris
2016-10-18 19:02 ` Richard Weinberger [this message]
2016-10-18 19:15 ` Boris Brezillon
2016-10-18 21:10 ` David Oberhollenzer
2016-10-18 22:04 ` Marek Vasut
2016-10-18 19:31 ` Marek Vasut
2016-10-18 19:41 ` Boris Brezillon
2016-10-18 19:51 ` Marek Vasut
2016-10-19 6:41 ` Artem Bityutskiy
2016-10-18 19:59 ` Moritz Fischer
2016-10-18 20:18 ` Richard Weinberger
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=09ac9f8a-d6a0-97a8-c73a-ffb53bc1a4c8@nod.at \
--to=richard@nod.at \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=nicolas.ferre@atmel.com \
/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
all inboxes | Powered by JetHome®