📅 Original date posted:2014-10-15
📝 Original message:Hello,
I'm trying to create a bit of process around the
https://github.com/bitcoin/bips repository.
A) Currently a lot of pulls are open for various BIPs and it is not
clear who should comment on them, or who decides on changes to be
merged.
Currently all BIP changes have to go through the Bitcoin Core team,
which is a narrow bottleneck and makes little sense when you think
about it. But I don't want to go back to the wiki state in which
everyone can make arbitrary changes to any BIP - we need to distribute
the process somehow.
I'd like to propose to make the author (or someone they delegate to)
the primary contact for each BIP. They should comment on changes, and
either accept or reject them. If they accept them, the change will be
merged.
Of course this means that there is a responsibility for the author to
adhere to BIP 1. For example if your BIP is final, don't allow any
technical changes. To do small clarifications, spelling or adding
implementations or examples is OK, but changing or adding to a
protocol is not - this needs a new BIP. Changing your BIP status
without community consensus is also not OK.
B) I also think it makes sense to move the BIP discussion (both about
the BIP process and individual BIPs) to a separate mailing list.
bitcoin-development currently has a dual function: discussion of
Bitcoin Core implementation concerns, as well as global changes to
Bitcoin (in the form of BIPs).
This makes the list too busy for some people, but it is critical that
everyone writing a Bitcoin node or client is up-to-date with proposals
and can comment on them.
Wladimir
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:26:29
in reply to nevent1q…2d2g
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:26:29Event JSON
{
"id": "c111271b24d07b39f08118c11c655b4702627163a8e84d95c2c37b3ac640cad8",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151589,
"kind": 1,
"tags": [
[
"e",
"8e8ffc86b671332d74dc30a93d73d86bf0648414fedbd225ac787a9a2713f3b5",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2014-10-15\n📝 Original message:Hello,\n\nI'm trying to create a bit of process around the\nhttps://github.com/bitcoin/bips repository.\n\nA) Currently a lot of pulls are open for various BIPs and it is not\nclear who should comment on them, or who decides on changes to be\nmerged.\n\nCurrently all BIP changes have to go through the Bitcoin Core team,\nwhich is a narrow bottleneck and makes little sense when you think\nabout it. But I don't want to go back to the wiki state in which\neveryone can make arbitrary changes to any BIP - we need to distribute\nthe process somehow.\n\nI'd like to propose to make the author (or someone they delegate to)\nthe primary contact for each BIP. They should comment on changes, and\neither accept or reject them. If they accept them, the change will be\nmerged.\n\nOf course this means that there is a responsibility for the author to\nadhere to BIP 1. For example if your BIP is final, don't allow any\ntechnical changes. To do small clarifications, spelling or adding\nimplementations or examples is OK, but changing or adding to a\nprotocol is not - this needs a new BIP. Changing your BIP status\nwithout community consensus is also not OK.\n\nB) I also think it makes sense to move the BIP discussion (both about\nthe BIP process and individual BIPs) to a separate mailing list.\n\nbitcoin-development currently has a dual function: discussion of\nBitcoin Core implementation concerns, as well as global changes to\nBitcoin (in the form of BIPs).\n\nThis makes the list too busy for some people, but it is critical that\neveryone writing a Bitcoin node or client is up-to-date with proposals\nand can comment on them.\n\nWladimir",
"sig": "df0177f3d964c475c6c40363ec63840c43090bbac8e9a59878c58c63540841c9366451b040b8cf32eb4ba044d17f0fcf6194495524dd65010cc0bf58e6ac7a8b"
}