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 1C3E71381F3 for ; Sat, 22 Jun 2013 01:14:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5DF70E09BA; Sat, 22 Jun 2013 01:14:28 +0000 (UTC) Received: from jacques.telenet-ops.be (jacques.telenet-ops.be [195.130.132.50]) by pigeon.gentoo.org (Postfix) with ESMTP id 37F9BE087F for ; Sat, 22 Jun 2013 01:14:27 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by jacques.telenet-ops.be with bizsmtp id rDES1l00C2khLEN0JDESfH; Sat, 22 Jun 2013 03:14:26 +0200 Date: Sat, 22 Jun 2013 03:11:42 +0200 From: Tom Wijsman To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Message-ID: <20130622031142.73d56d9e@TOMWIJ-GENTOO> In-Reply-To: <20130621150411.6e951202@gentoo.org> References: <20130621150411.6e951202@gentoo.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.18; x86_64-pc-linux-gnu) 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; micalg=PGP-SHA1; boundary="Sig_/aa8wNMxl6Ix+gc+Q2R5wPkl"; protocol="application/pgp-signature" X-Archives-Salt: 12243610-8ab0-496f-9d69-1844da28d374 X-Archives-Hash: c3477a2cfab8db690a0f9ad3d597e8b2 --Sig_/aa8wNMxl6Ix+gc+Q2R5wPkl Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 21 Jun 2013 15:04:11 -0400 Alexis Ballier wrote: > > I'm open to all input, but here's some initial questions I'd like to > > hear your answers to: > > - How should developers, herds & teams communicate how welcome they > > are to NMU changes on their packages? >=20 > The way I've been doing this is: > - packages I maintain through herd -> go ahead and be responsible. sys-kernel/gentoo-sources only lists the kernel herd; while I don't think anyone else is unwelcome, I don't see NMU changes as something that would happen to it. Since the ebuild could be called optimal, changes to it would likely make it perform in an unexpected way. More general, I think there are some packages here that have this kind of nature; for another instance, the java packages require some additional knowledge for which Gentoo Developers have to go go through a quiz. I believe users and proxy maintainers not to be aware of this, therefore again the changes might sometimes be problematic.=20 > - if I add myself explicitly in metadata.xml this means I prefer at > least reviewing every change that gets in (with some exceptions for > trivial changes, like e.g. qt moving category) I think this should apply to a herd as well, unless otherwise noted. > [...] > > - How do we encourage responsible ownership of changes that cause > > breakage? [1] Since it is listed in the ChangeLog, I think it implies the ownership. --=20 With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D --Sig_/aa8wNMxl6Ix+gc+Q2R5wPkl Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJRxPnOAAoJEJWyH81tNOV9cGAH/jJoA6KqBNZGhXHc9extyJdj H19PUXW76Zq81NRMxU0dOIIqHhm7cGYLuvXszHYCHbBMeGxZdcqnEiSXy6fxEPpW PRBhFDGj9BvPVPR2D7CAmgrhd5hD3mg+8Hki26W+/yrwgQLNWPGWk90Ex116snX1 k22YXk7z2dVMqlPo5yWVbAAz3jU3qpOgOKKX74MJf9fI/vbASspBlyfGV7kNz36+ OxAgAfyPTve6eQirYWb14UtFL9ycqlIiO2KjDQ0GTJfRIHPUq7DV+V1hvM/O+0He bFN2wpFJlhItZ7pTUpxMGHpkxNsxcoxBOF/44f1197M+Xz/y96Xq8EUZu46hFZI= =Ph7+ -----END PGP SIGNATURE----- --Sig_/aa8wNMxl6Ix+gc+Q2R5wPkl--