From: "W. J. van der Laan" <laanwj@protonmail•com>
To: "David A. Harding" <dave@dtrt•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs
Date: Tue, 27 Apr 2021 09:04:18 +0000 [thread overview]
Message-ID: <773C1Ki5dlSNlxD3HK0eJDKHQ9Ikb5vwuKPZ3dkgEPqUmPGN6DrpLv47LNITHOlu7XWzmIpAmgw24noihYJ5lI5Qhmg7yIlboGQsfAowFCw=@protonmail.com> (raw)
In-Reply-To: <20210426194309.2k5exujz23vjrgwc@ganymede>
On Monday, April 26th, 2021 at 9:43 PM, David A. Harding via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Sun, Apr 25, 2021 at 05:31:50PM -0400, Matt Corallo via bitcoin-dev wrote:
>
> > In general, I think its time we all agree the BIP process has simply failed
> >
> > and move on. Luckily its not really all that critical and proposed protocol
> >
> > documents can be placed nearly anywhere with the same effect.
>
I like the idea of decentralizing the BIPs process. It is a historical artifact that the bips repository is part of the same organization that bitcoin core is part of. But there shouldn't be the perception that standardization is driven by that, or that there is any kind of (non-trivial) gatekeeping.
I understand where this perception is coming from, though. There being 111 PRs open at https://github.com/bitcoin/bips/pulls indicates that there is some kind of bottleneck. I hope adding more BIP editors can mitigate this somewhat.
Though it also happens that the BIP author simply don't care about changes anymore and doesn't respond, in which case the PR lingers without any fault from the BIPs maintainer. So something is to be said of having the BIP repository mirror/aggregate author's own work trees, and changes needing to be proposed there instead of "upstream".
-W
next prev parent reply other threads:[~2021-04-27 9:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 2:09 [bitcoin-dev] Proposed BIP editor: Kalle Alm Luke Dashjr
2021-04-23 3:36 ` Jeremy
2021-04-23 7:49 ` John Newbery
2021-04-23 7:50 ` Pindar Wong
2021-04-23 9:11 ` Eric Martindale
2021-04-23 15:34 ` Antoine Riard
2021-04-24 10:16 ` nopara73
2021-04-25 20:29 ` [bitcoin-dev] Reminder on the Purpose of BIPs Matt Corallo
2021-04-25 21:00 ` Luke Dashjr
2021-04-25 21:14 ` Matt Corallo
2021-04-25 21:22 ` Luke Dashjr
2021-04-25 21:31 ` Matt Corallo
2021-04-26 19:43 ` David A. Harding
2021-04-26 20:04 ` Greg Maxwell
2021-04-27 19:43 ` Melvin Carvalho
2021-04-27 9:04 ` W. J. van der Laan [this message]
2021-04-27 11:49 ` Erik Aronesty
2021-04-27 11:33 ` John Newbery
2021-04-27 12:16 ` Jorge Timón
2021-04-26 15:02 ` [bitcoin-dev] Proposed BIP editor: Kalle Alm Sjors Provoost
2021-04-26 16:56 ` James O'Beirne
2021-04-26 18:13 ` W. J. van der Laan
2021-09-15 9:50 [bitcoin-dev] Reminder on the Purpose of BIPs Prayank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='773C1Ki5dlSNlxD3HK0eJDKHQ9Ikb5vwuKPZ3dkgEPqUmPGN6DrpLv47LNITHOlu7XWzmIpAmgw24noihYJ5lI5Qhmg7yIlboGQsfAowFCw=@protonmail.com' \
--to=laanwj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox