From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Fri, 21 Jun 2013 20:17:38 -0400 [thread overview]
Message-ID: <201306212017.38571.vapier@gentoo.org> (raw)
In-Reply-To: <robbat2-20130621T235922-795874263Z@orbis-terrarum.net>
[-- Attachment #1: Type: Text/Plain, Size: 1316 bytes --]
On Friday 21 June 2013 20:06:31 Robin H. Johnson wrote:
> 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.
add a new field to metadata.xml that declares the state. make it an enum:
ANYTHING_GOES (the default)
REQUIRES_HERD
REQUIRES_MAINTAINER
> 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?
have gerrit check metadata.xml and see if the policy declared in there lines
up with the gerrit approvals attained. blam, done.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-22 0:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 18:50 [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Robin H. Johnson
2013-06-21 19:04 ` Alexis Ballier
2013-06-21 19:07 ` Robin H. Johnson
2013-06-21 19:31 ` Alexis Ballier
2013-06-22 1:11 ` Tom Wijsman
2013-06-21 20:31 ` Michael Weber
2013-06-21 20:41 ` Michael Weber
2013-06-22 1:21 ` Tom Wijsman
2013-06-21 23:40 ` Mike Frysinger
2013-06-22 0:06 ` Robin H. Johnson
2013-06-22 0:17 ` Mike Frysinger [this message]
2013-06-22 0:26 ` Robin H. Johnson
2013-06-22 1:06 ` Mike Frysinger
2013-06-22 1:42 ` Robin H. Johnson
2013-06-22 3:28 ` Rick "Zero_Chaos" Farina
2013-06-22 9:00 ` Ulrich Mueller
2013-06-22 9:05 ` hasufell
2013-06-22 9:38 ` [gentoo-dev] Herds (was: Soliciting input for a non-maintainer update (NMU) GLEP) Ulrich Mueller
2013-06-22 9:48 ` [gentoo-dev] Herds hasufell
2013-06-22 9:46 ` [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Ulrich Mueller
2013-06-22 10:43 ` Rich Freeman
2013-06-22 9:01 ` hasufell
2013-06-22 10:20 ` Michael Weber
2013-06-22 10:39 ` Rich Freeman
2013-06-22 10:52 ` Tom Wijsman
2013-06-22 17:59 ` Mike Frysinger
2013-06-22 9:16 ` Markos Chandras
2013-06-22 10:19 ` Tom Wijsman
2013-06-22 13:42 ` [gentoo-dev] " Michael Palimaka
2013-06-22 15:13 ` [gentoo-dev] " hasufell
2013-06-22 16:56 ` Robin H. Johnson
2013-06-22 10:11 ` Pacho Ramos
2013-06-23 3:01 ` Rick "Zero_Chaos" Farina
2013-06-27 18:18 ` hasufell
2013-06-27 19:29 ` Rick "Zero_Chaos" Farina
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=201306212017.38571.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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