Delivery-date: Tue, 10 Dec 2024 15:05:09 -0800
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: <147b5bf7-dab0-4180-8ce6-270431e2c5c4@murch.one>
Date: Tue, 10 Dec 2024 17:37:55 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [bitcoindev] Time for an update to BIP2?
From: Murch <murch@murch.one>
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>
 <82a37738-a17b-4a8c-9651-9e241118a363@murch.one>
Content-Language: en-US
In-Reply-To: <82a37738-a17b-4a8c-9651-9e241118a363@murch.one>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="------------OGV2mrrf5Ef08bxyBFB30d1b"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------OGV2mrrf5Ef08bxyBFB30d1b
Content-Type: multipart/mixed; boundary="------------FpY0g05tQq7sRBoebLHeibLh";
 protected-headers="v1"
From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Message-ID: <147b5bf7-dab0-4180-8ce6-270431e2c5c4@murch.one>
Subject: Re: [bitcoindev] Time for an update to BIP2?
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>
 <82a37738-a17b-4a8c-9651-9e241118a363@murch.one>
In-Reply-To: <82a37738-a17b-4a8c-9651-9e241118a363@murch.one>

--------------FpY0g05tQq7sRBoebLHeibLh
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable

Hey y=E2=80=99all,

After going through the review comments following my prior email from=20
September and reworking several sections, I finished an initial draft of=20
a proposal how to update the BIP Process.

The main changes compared to BIP2 are:

- Sunset the comments system
- Rework the workflow
- Use only four Status values (Draft, Complete, Deployed, and Closed)=20
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 Changelog to record changes to BIPs=20
after they have been recommended for adoption
- Update the 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
- Introduce the Shepherd role as stand-in for Authors

Due to the length of the proposal, please find the full text in this=20
pull request:

   https://github.com/bitcoin/bips/pull/1712

I am looking forward to your review and comments.

Best,
Murch


On 2024-09-18 14:25, Murch wrote:
> Hey y=E2=80=99all,
>=20
> Continuing the conversation about an update to the BIP process, I have=20
> clobbered together a draft proposal.
>=20
> 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=
 the=20
> discussion earlier this year, the BIP Process Wishlist, and issues=20
> surfaced by sighting the open pull requests.
>=20
> The main changes compared to BIP=E2=80=AF2 are:
>=20
> - 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
>=20
> 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.
>=20
> Please especially take note of the description of the repository=E2=80=99=
s scope.
>=20
> You can find the draft here:
> https://github.com/murchandamus/bips/pull/2
>=20
> I may also open a pull request to the main BIPs repository later this=20
> week assuming this draft is well-received.
>=20
> 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 visit https://groups.google.com/d/msgid/bitcoindev/=
147b5bf7-dab0-4180-8ce6-270431e2c5c4%40murch.one.

--------------FpY0g05tQq7sRBoebLHeibLh--

--------------OGV2mrrf5Ef08bxyBFB30d1b
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEENfStpiPrn+OjvH72e6A1yluQFxMFAmdYwsMACgkQe6A1yluQ
FxOb3xAAnaotVns8VCc3tAx/Z+BeyWrrILNWN5VBhaNnjHFRvNIJzamRK5su4zX2
4cuXeN3lhD2riB4WIvqDUFJ5yFXRTP9FAQV6pfTSjVKIjTwyT5wWYhJtUZTaJYIQ
aDSBaUYeD2xA+A9gj7n+7J9WDMJrai3NSWwixwybKpL11sVYNMWM3QeOAQM4nuqj
+eX9HjUsq9eD2D21y9TxhEo1uO8TLW5CvgqIZ3lg4jYP716brUu168sh6516DYHh
1qWEepB+q+SMYAuxsXcR8xKpabiZvu0DhytUCFS2cZIveN4zczx6Ddi+SMYk1gZn
K/hnHf4jdOPpg3Y957/m21dcYQq9Nb6e4trMyGn0o1KQ2wcMLLUwPCHr7On5DwZC
Kh7TT7ipVos2Iei5ulv940wb3ao8EV175q1/9H6dPcRC7qIU52iIaDX+2mBJjFid
n72Mh/A7w7AJjkzuj0hUt/qEGbWcDX4zy6Iifz6OVkJVKw9/pVbkJLYEiWgc2NUQ
Q3N8kZWT1PpIojrCEEt7XUTIywLr5Vvon35SVRTnGz+svWo7Lkj9AvfRHYytxkF5
836ZoHkOXCrrt+CGNSBv/u4IlIv9hAP6v98HJdmzhO15Eyme6qcpGl9fyoO3Aa+2
UD9dZlGkSYjNHr+8wOhQg843HduliDIGhmTNt4Sf3qSbXMcCwnw=
=XxMM
-----END PGP SIGNATURE-----

--------------OGV2mrrf5Ef08bxyBFB30d1b--