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 E315B1381F3 for ; Fri, 21 Jun 2013 19:08:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D08FDE0B45; Fri, 21 Jun 2013 19:07:50 +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 D5135E0B32 for ; Fri, 21 Jun 2013 19:07:49 +0000 (UTC) Received: from grubbs.orbis-terrarum.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 0D03C33BE43 for ; Fri, 21 Jun 2013 19:07:49 +0000 (UTC) Received: (qmail 9600 invoked by uid 10000); 21 Jun 2013 19:07:48 -0000 Date: Fri, 21 Jun 2013 19:07:48 +0000 From: "Robin H. Johnson" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Message-ID: References: <20130621150411.6e951202@gentoo.org> 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: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130621150411.6e951202@gentoo.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: cd9ec1bb-5c01-48d4-a28e-5775176b653f X-Archives-Hash: 6263fd0b943c50893eea5abd7bcf0760 On Fri, Jun 21, 2013 at 03:04:11PM -0400, Alexis Ballier wrote: > > - How should developers, herds & teams communicate how welcome they > > are to NMU changes on their packages? > The way I've been doing this is: > - packages I maintain through herd -> go ahead and be responsible. > - 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) That's fine for packages in a herd, but doesn't scale, and doesn't handle packages without a herd. > > - How do we encourage responsible ownership of changes that cause > > breakage? [1] > That's something I'd like to get enlightened on. The, probably too > emotional, algorithm that doesn't scale I've been applying has been: Your portion is also if you are the one that found it. You might not be the person that finds it. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robbat2@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85