From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VYGYg-0005Dt-N6 for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 14:34:14 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.169 as permitted sender) client-ip=209.85.212.169; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f169.google.com; Received: from mail-wi0-f169.google.com ([209.85.212.169]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VYGYe-0007LO-Ud for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 14:34:14 +0000 Received: by mail-wi0-f169.google.com with SMTP id cb5so5283638wib.0 for ; Mon, 21 Oct 2013 07:34:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=gPqWICeOj1BoDr49YDW4K8G4pbQGyWZfZO545KNw1mY=; b=hyYpebC+QevyFdEpQhsEV8xX43igFrmrO7elyiZsKJE7H4pHi1IsAXHKvm38GxbhIz KX5CykQElm1eHOM3OOPyYffVBlxm7cNM6H0Zw1v23yzZelor7g4y1RgHvRw5cERBBW6L LMvP4qGiDsr1Lja/rxX5Eiost5WerxcUfNv8jHoyhN2WjgNMJoO8KezA7cX3NBu8kVC+ P2T9e4cclvNx1TE70X6tXQDfCfyliKnQlayWHy2BZtrah3c8RrBekXkve56XPjmvxxln RpeNlE2iXGsP2301KBp5l5vFs3DfI64Xr6+JT82KVEGJd/cyHqbvkhMCmIGNN8FdpPKV ah2A== X-Gm-Message-State: ALoCoQlABY0Z1CCZQyiPA32dEWOd4gAmmeoYW0Vspmm8ScNXjbGxZzwEa0zsbArX+uYaZHTkoJdm MIME-Version: 1.0 X-Received: by 10.180.198.79 with SMTP id ja15mr10074269wic.36.1382366046739; Mon, 21 Oct 2013 07:34:06 -0700 (PDT) Received: by 10.194.164.164 with HTTP; Mon, 21 Oct 2013 07:34:06 -0700 (PDT) In-Reply-To: References: Date: Mon, 21 Oct 2013 10:34:06 -0400 Message-ID: From: Jeff Garzik To: Bitcoin Dev Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitpay.com] X-Headers-End: 1VYGYe-0007LO-Ud Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 14:34:14 -0000 Continuing. (grumble gmail grumble) As with the IETF, there will be a great many drafts that do not make it to BIPS status. That is normal, and a sign of a healthy process. I'll volunteer as the BIPS editor. There needs to be some backups with commit access to bips.git, in case the BIPS editor is hit by a bus or goes crazy or on vacation. This can be some core devs, but I would like at least one or two folks who are not Satoshi-client devs on the list. Maybe Andreas, Michael G, Alan R, and others working on non-Satoshi clients. -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/