From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-51951-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1SXisa-0005lH-A5
	for garchives@archives.gentoo.org; Fri, 25 May 2012 00:59:44 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 702A7E0683;
	Fri, 25 May 2012 00:59:30 +0000 (UTC)
Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53])
	by pigeon.gentoo.org (Postfix) with ESMTP id 894A9E05AF
	for <gentoo-dev@lists.gentoo.org>; Fri, 25 May 2012 00:58:46 +0000 (UTC)
Received: by bkcjk13 with SMTP id jk13so361182bkc.40
        for <gentoo-dev@lists.gentoo.org>; Thu, 24 May 2012 17:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        bh=by2HA/lTWHZ+K5PNHop8oBrKsjE1mGXc/8Gvi89qZKw=;
        b=unzIGzbJpxsVdFzyYsuzSoJ9JabPzcAYlgV04uIRdpc29XTBjigemt5InmJ0RYr+Yk
         ajTABVDZ9ONs7XWPPffG2oVG5G6EdmIzpHz+wbi2on2Y3l9dZdTM+LD3czSXHvPxW65B
         J5LLJLgQc0Gbr9ngycY1txleuT3DktRhZQtV1WkXuOqxEfqUobIrvDttuno5tjqnO2QB
         8vAUeuBD2saMrL1vDLbKoJ3tX0837HpYdW3KsDJTvdIL33nyWTymEq5xgC+OtDmmn/Yy
         fVPTjRvR/j8YWnWbIBlFC4x2e5AwhDtYmU63p/fjMm1KZUXLQoIJI58judpxCfj+2WDP
         cuCQ==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.205.133.212 with SMTP id hz20mr585074bkc.99.1337907525653;
 Thu, 24 May 2012 17:58:45 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.204.190.79 with HTTP; Thu, 24 May 2012 17:58:45 -0700 (PDT)
In-Reply-To: <1520922.mmjlWrWcEL@smorgbox>
References: <4FBCDB3D.1070009@gentoo.org>
	<3485389.iLMx13MNW5@smorgbox>
	<4FBEA181.30204@gentoo.org>
	<1520922.mmjlWrWcEL@smorgbox>
Date: Thu, 24 May 2012 20:58:45 -0400
X-Google-Sender-Auth: 7zl9smuXa1ZrZ3q9P0ym65q4ma8
Message-ID: <CAGfcS_kcPqzKmFSDFAsea8r2F=G9A2jUcjwR0Fin89Pt+sYGoQ@mail.gmail.com>
Subject: Re: [gentoo-dev] Portage Git migration - Handling Pull Requests (Was:
 clean cut or git-cvsserver)
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Aaron W. Swenson" <titanofold@gentoo.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: f4642876-579d-416d-abe4-3b361f799c9d
X-Archives-Hash: 46788ffdec9455dda538b5d74ca0ba3a

On Thu, May 24, 2012 at 6:01 PM, Dan Douglas <ormaaj@gmail.com> wrote:
> But ok it's a good point. Github isn't a good central point of contact. People
> have to use their discression. It's just uncommon these days for a project as
> big as Gentoo to have ultra-centralized corporate-style procedures where
> everything happens exclusively though official channels. And anyway you couldn't
> "enforce" that sort of thing if you tried.
>

++

There is no policy that every commit in cvs needs to be referenced to
a bug, and I doubt we're going to change that.  So, if I call up
another dev on the phone and tell them they have a typo in an ebuild,
and they fix it and commit it, nothing has gone wrong.  That isn't the
most efficient way to work usually, but there is no policy against it.
 In general users should file bugs and not contact devs directly, but
if somebody has a private arrangement otherwise, no harm no foul.

Github is just another overlay.  If in the course of working on the
next kde release the kde team makes 385 changes to their overlay, we
don't make them log and close 385 bugs on b.g.o before they merge in
the files from the overlay.

So, if a team wants to use non-official tools, by all means go ahead.
The QA standards apply to anything hitting the main tree, and must be
followed at that point in time.  We should keep our tools working
well, but if in some case there is a better way of working, or a small
team has some other preference, well, have at it!

Rich