Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP

["Robin H. Johnson" <robbat2@gentoo.org>]

On Fri, Jun 21, 2013 at 07:40:03PM -0400, Mike Frysinger wrote:
> On Friday 21 June 2013 14:50:54 Robin H. Johnson wrote:
> > From what I've read on the list recently, there's a lot of demand for
> > non-maintainer updates to ebuilds. Esp. with the upcoming Git migration,
> > I predict there will be a much larger influx of changes from users.
> seems like we're somewhat approaching it the wrong way around. 
[Snip giant suggestions re gerrit/review-systems]

I'm not going into review systems here at all, I'm simply trying to have
a policy of what changes are welcomed/blocked WITHOUT interaction from
the listed maintainer(s) of a given package/herd.

If they have to ask me to review a trivial patch, I've already failed
them. I don't want ANY gatekeeping, I want them to go and commit it
already.

Then extending THAT to Gerrit, who is responsible/allowed to hit that
web interface submit button? I don't want it to have to be me either for
most of my packages. If some developer reviews a trivial change (either
by another dev or a user) and thinks it's ok, then it should probably go
in the tree. Why does it need to involve me at all, other than I'm the
listed maintainer for the package.

If it's some major patch or a big feature addition, then it probably
needs more serious eyeballs (eg complex patches to qmail [very fragile],
unix socket patch to openssh [rejected upstream]).

I think both NMU & Gerrit need to happen (as well as 'git pull' of
changes from users).

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85