gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] NEW POLICIES (draft)


From: Andrew Suffield
Subject: Re: [Gnu-arch-users] NEW POLICIES (draft)
Date: Sun, 3 Oct 2004 01:54:21 +0100
User-agent: Mutt/1.5.6+20040907i

On Sat, Oct 02, 2004 at 05:28:00PM -0700, Thomas Lord wrote:
>     > Only
>     > the bug database itself is connected here; a vote-driven branch should
>     > be regarded merely as a convinient source from which you can construct
>     > the branches you described (convinience being inversely proportional
>     > to the amount of stuff that passes without going through the
>     > vote-driven branch, and that's intrinsic to the problem). It doesn't
>     > actually appear anywhere in the stuff you covered.
> 
> 
> Ideally, 3rd parties should be able to construct at least casual
> contributions and ideally long-term contributions as described in the
> standard, yet have those processed by the voting system.   It's the
> path from entry to the voting system to inclusion in mainline that
> needs some attention.

Entry point is (has to be) a completely formed merge request in the
bug goo database; anything else is far too much work, and it's not a
particularly onerous requirement; by design you can stuff any
arbitrary thing produced by a front-end process in here with minimal
effort.

Exit path is not my problem; you can pure-merge from the managed
branch (rubber-stamping the group's work), ignore it completely
(discarding the group's work), or any point in between.

I can't think of anything else that matters here.

-- 
  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' :  http://www.debian.org/ |
 `. `'                          |
   `-             -><-          |

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]