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 377E21381F3 for ; Thu, 6 Dec 2012 11:03:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 23DE921C019; Thu, 6 Dec 2012 11:03:28 +0000 (UTC) Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 877DAE049A for ; Thu, 6 Dec 2012 11:02:56 +0000 (UTC) Received: by mail-vb0-f52.google.com with SMTP id ez10so3746018vbb.11 for ; Thu, 06 Dec 2012 03:02:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=+mrc57hdgi0CKhf5A2bzxpt2BzZMT8WyxzGUXat1amA=; b=D364msED57S+MIGcbLixc32aU3lkMDwq9vXI98AvfY/wImCauvuHVpms9GTH7r7JXj l/NB0Kyp+F6nt39MG6pFibK5LUABR+YxOMK0pFUpA6Qzj+fVgOIS4YrdyotOUe7mb8Ju llLhyFR+VMLKLJsYUzMaLRwRTJZVktA4qzswKwp69bh0l7VAKM+phJk1fwam24ZCHVJy xYabaUMtYXUErWUNHW27IXlkGqj793WYJDIjs2JQctOK4uIutn3HciDXc9DF0lM28rbY GBVS2mVDRd0U4+YTEEFK2x0aCnCRsxGwq1S3MO3zHcRh8qDLnqiIcE7d9bRXb5K+6L/3 G78g== 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 Received: by 10.220.209.74 with SMTP id gf10mr614853vcb.10.1354791775649; Thu, 06 Dec 2012 03:02:55 -0800 (PST) Sender: yngwin@gmail.com Received: by 10.58.4.169 with HTTP; Thu, 6 Dec 2012 03:02:55 -0800 (PST) In-Reply-To: References: <50BB71DD.4080308@gentoo.org> <50BDAFE2.6000702@gentoo.org> <50BE1E3E.9070406@gentoo.org> <50BE2D95.1000201@flameeyes.eu> <50BE32B9.6010205@gentoo.org> Date: Thu, 6 Dec 2012 19:02:55 +0800 X-Google-Sender-Auth: xyukEi67rBs8LgKpCGvM3weCR3k Message-ID: Subject: Re: Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) From: Ben de Groot To: gentoo-dev Content-Type: multipart/alternative; boundary=bcaec54fb410883d8404d02d0adb X-Archives-Salt: 8e28ce29-f54d-4312-b52f-c851e7d13073 X-Archives-Hash: 9254f68095684c6aa51c93900d9c1c6c --bcaec54fb410883d8404d02d0adb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 5 December 2012 02:51, Markos Chandras wrote: > On 4 December 2012 17:28, Rick "Zero_Chaos" Farina > wrote: > > On 12/04/2012 12:06 PM, Diego Elio Petten=C3=B2 wrote: > >> Or maybe we can just agree that common sense rules all, and we always > >> set the proxied maintainer as assignee, and the proxy maintainer as CC= .. > > > > > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml?style=3Dprin= table > > > > This page exists, but doesn't really mention anything about proper bug > > assignment. I know a lot of you have been doing this a very long time > > and there is a 'standard' way of doing things, but for us new guys if > > there is no documentation there is no policy. > > Bug-wranglers are supposed to do that by default. When you see a > non-gentoo developer in metadata.xml, the default action is to assume > his is > the real maintainer and the bugs should be assigned to him. Such > guidance should be documented in the bug-wranglers project page and > not on the > proxy-maintainers one. > > Actually, as I have been arguing elsewhere, scattering policies over multiple documents is not helpful. So this should be documented in devmanual. --=20 Cheers, Ben | yngwin Gentoo developer Gentoo Qt project lead, Gentoo Wiki admin --bcaec54fb410883d8404d02d0adb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 5 Dece= mber 2012 02:51, Markos Chandras <hwoarang@gentoo.org> wro= te:
On 4 December 2012 17:28, = Rick "Zero_Chaos" Farina <zerochaos@gentoo.org> wrote:
> On 12/04/2012 12:06 PM, Diego Elio Petten=C3=B2 wrote:
>> Or maybe we can just agree that common sense rules all, and we alw= ays
>> set the proxied maintainer as assignee, and the proxy maintainer a= s CC..
>
> http://www.gentoo.org/proj/en/qa/pro= xy-maintainers/index.xml?style=3Dprintable
>
> This page exists, but doesn't really mention anything about proper= bug
> assignment. I know a lot of you have been doing this a very long time<= br> > and there is a 'standard' way of doing things, but for us new = guys if
> there is no documentation there is no policy.

Bug-wranglers are supposed to do that by default. When you see a
non-gentoo developer in metadata.xml, the default action is to assume
his is
the real maintainer and the bugs should be assigned to him. Such
guidance should be documented in the bug-wranglers project page and
not on the
proxy-maintainers one.


Actually, as I have been arguing elsew= here, scattering policies over multiple documents is not helpful. So this s= hould be documented in devmanual.

--
Cheers,

Ben | yngwin
Gentoo developer
Gentoo Qt project lead, Gentoo Wiki= admin
--bcaec54fb410883d8404d02d0adb--