Delivery-date: Wed, 18 Sep 2024 11:30:22 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of murch@murch.one designates 2a00:d0c0:200:0:1c7b:a6ff:fee0:8ea4 as permitted sender) client-ip=2a00:d0c0:200:0:1c7b:a6ff:fee0:8ea4;
Message-ID: <82a37738-a17b-4a8c-9651-9e241118a363@murch.one>
Date: Wed, 18 Sep 2024 14:25:47 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [bitcoindev] Time for an update to BIP2?
To: bitcoindev@googlegroups.com
References: <e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.com>
 <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
 <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
 <d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com>
 <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
 <f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcorallo.com>
 <ZgWRu32FXzqqg69V@console>
 <9ebd08b0-7680-4896-aad3-1c225b764bcb@mattcorallo.com>
 <59fa94cea6f70e02b1ce0da07ae230670730171c.camel@timruffing.de>
 <4pVUOTuyyAbTJB_rTGNWS_TuR39NS5OoJvaSCyqjezAg265kPnCjXvqohFmWQ5ITb7XFZCJie-uV1AG3pVCI5H54dDuFP4OyomC9yiWDot0=@wuille.net>
 <Zg4z7P+MKzEfCkdM@erisian.com.au>
 <0bc47189-f9a6-400b-823c-442974c848d5@murch.one>
Content-Language: en-US
From: Murch <murch@murch.one>
In-Reply-To: <0bc47189-f9a6-400b-823c-442974c848d5@murch.one>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

Hey y=E2=80=99all,

Continuing the conversation about an update to the BIP process, I have=20
clobbered together a draft proposal.

It aims to make determinations on all the topics that were covered by=20
BIP=E2=80=AF2, but tries to address many of the pain points brought up in t=
he=20
discussion earlier this year, the BIP Process Wishlist, and issues=20
surfaced by sighting the open pull requests.

The main changes compared to BIP=E2=80=AF2 are:

- Sunset the comments system
- Rework the workflow
- Use only four Status values (Preliminary, Ready, Active, and=20
Abandoned) instead of nine, clarify the meaning of statuses
- Replace the "Standards Track" BIP type with the "Specification" BIP=20
type, and update definitions for all BIP types
- Declare Process BIPs to be living documents
- Discourage adoption tracking in the BIPs repository
- Introduce Revision header and Change Log to record changes to BIPs=20
after they have been recommended for adoption
- Update description of repository=E2=80=99s scope
- Reduce BIP Editor role to checking editorial and formal criteria,=20
reassigning judgment calls to authors and audience

I=E2=80=99m open to reconsider most aspects of this proposal, provided=20
convincing arguments and tenable alternatives. Please consider relevant=20
rationale provided in the footnotes when suggesting changes.

Please especially take note of the description of the repository=E2=80=99s =
scope.

You can find the draft here:
https://github.com/murchandamus/bips/pull/2

I may also open a pull request to the main BIPs repository later this=20
week assuming this draft is well-received.

Best,
Murch

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/82a37738-a17b-4a8c-9651-9e241118a363%40murch.one.