From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 391AF1381F3 for ; Fri, 21 Jun 2013 23:40:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13BA8E0B97; Fri, 21 Jun 2013 23:40:01 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 25A5EE0B46 for ; Fri, 21 Jun 2013 23:40:00 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 4D65D33E5E3 for ; Fri, 21 Jun 2013 23:39:59 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.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 User-Agent: KMail/1.13.7 (Linux/3.8.3; KDE/4.6.5; x86_64; ; ) References: In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3825080.l7mYKXfWBz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201306211940.03851.vapier@gentoo.org> X-Archives-Salt: 64ba46d1-70ab-4d6c-a1eb-ea479ebdef29 X-Archives-Hash: 6c673e45e3994c4f6b123043e6fbeef8 --nextPart3825080.l7mYKXfWBz Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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= =20 sucks -- bugzilla is not the proper medium for gating ebuild contributions.= =20 something like gerrit would make things flow a lot more smoothly imo. i've= =20 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=20 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= =20 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=20 the web interface (gerrit also has a ssh command line interface for doing=20 things). would be easy to add a `repoman upload` that'd take care of makin= g=20 the commit, regenerating things (Manifest/etc...), and then uploading it to= =20 gerrit. =2Dmike --nextPart3825080.l7mYKXfWBz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJRxORTAAoJEEFjO5/oN/WBDkwP/1JesQBY74+Z48dC9jhaukgO izlqef+JsbyHu5xAPSxYFGD2s0fGYrmX/l/cJWN5K6SkKnN4N5JI6VDLd1ciN5zD U5QfEHuJ+mhFdrKvrmNZJXezpWugihSH2uQYrMmr6X7ORB0eA+RoNWjZPokU1n2a 7ugSevS2HaNBjRtYUNToCqlrf8DG13A0bkib/fN2pyaFR0jvny0tbR1znztuZJu8 LpuHctcRn9bZSlWwNRPy8XyDGgVbpA9e8KeToOiLZZY3cR+JVixHRZseWEOW+WZw 1ZU5ocV+IZbpnyfVPMwvpwMlOEbFdcktsioDbHE2Cfq2aBwxPrVcANMegP/jH1uv O05LpkM91AaMzwo1knD0Wn8m47RUWuhUWscXrhbmYzuzOdgOLrQ1J5Xl2Cedtxhq uImE5evG40KWeuzQRkfJ0I7JF6L1bf5ye/xrbF0Slug9SNB0kM3z6mStCV2X9FPE TXFCR/NS5LT/8giHrG1dlXQhV7HO6jfqK1jTCss9lO0hcS5jdOjuPHy0MuvUTMCj oOfBRbr1zmnsanIFTUD8/a+9EoeyHOaTtEV0S5l2Vr7ORbRw1A12xKM64Q2zsamY oTCGDJh5a7PYGYtwJqGojzK+5WuudZpL8e9Fxksn124ORfg1u+H0IB+46u/qYW6q bwDueMIAFF83DcRWe8lc =eJAb -----END PGP SIGNATURE----- --nextPart3825080.l7mYKXfWBz--