public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 19:40:03 -0400	[thread overview]
Message-ID: <201306211940.03851.vapier@gentoo.org> (raw)
In-Reply-To: <robbat2-20130621T182855-619828737Z@orbis-terrarum.net>

[-- Attachment #1: Type: Text/Plain, Size: 1526 bytes --]

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.  our tooling 
sucks -- bugzilla is not the proper medium for gating ebuild contributions.  
something like gerrit would make things flow a lot more smoothly imo.  i've 
been doing more workflow along the lines of:
 - dev/user posts patch to bugzilla
 - click "edit attachment as comment"
 - do patch review like a standard mailing list
 - dev/user posts updated patch
 - for a dev, i'll usually finish with "feel free to commit".  for a user, i'll 
commit it at some point (same for devs if i happen to be digging around).

if i do the commit, it's a pita:
 - ssh to a system that has commit access (assuming i'm in a location where 
this is possible, otherwise it'll have to wait)
 - open up the bug in a browser
 - find & download the attached patch
 - apply it and sort out any conflicts
 - run `repoman commit`
 - update the bug

with gerrit and git, this process could be turned into me clicking "submit" in 
the web interface (gerrit also has a ssh command line interface for doing 
things).  would be easy to add a `repoman upload` that'd take care of making 
the commit, regenerating things (Manifest/etc...), and then uploading it to 
gerrit.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-06-21 23:40 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 [this message]
2013-06-22  0:06   ` Robin H. Johnson
2013-06-22  0:17     ` Mike Frysinger
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=201306211940.03851.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