Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.180 as permitted sender)
	client-ip=74.125.82.180; envelope-from=jgarzik@bitpay.com;
	helo=mail-we0-f180.google.com; 
MIME-Version: 1.0
In-Reply-To: <l43i8u$k98$1@ger.gmane.org>
References: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
	<CAJHLa0OJz4yoKb_j1yVYjHc8rFStrFJonTyKKjvcPBOFfqDxMA@mail.gmail.com>
	<l43i8u$k98$1@ger.gmane.org>
Date: Mon, 21 Oct 2013 12:14:16 -0400
Message-ID: <CAJHLa0Nu1CKoOr-wJAC39B18xwrsoana_d+7+QwP+x5Fx-hRSg@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
Precedence: list

On Mon, Oct 21, 2013 at 11:46 AM, Andreas Schildbach
<andreas@schildbach.de> wrote:
> I accept the nomination as a backup (-:

Cool.

> So the duty of the editor is merging pull requests and/or proxying
> between email and git for those who do not use git?

Correct.  And assigning BIP numbers.  Ideally a boring administrative
position.  :)

The main tensions will be in gauging whether there is sufficient
consensus and review to boost a draft into BIP/proposed status, and
then promoting a numbered BIP to the final/accepted status.

-- 
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc.      https://bitpay.com/