From: Prayank <prayank@tutanota•de>
To: Michael Folkson <michaelfolkson@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Wednesday’s second BIP process meeting
Date: Wed, 6 Oct 2021 06:02:55 +0200 (CEST) [thread overview]
Message-ID: <MlIlAqo--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]
Good morning Michael,
Thanks for sharing the summary about BIP process meeting.
> However, zero filters creates a Ethereum style bewildering number of BIPs of varying quality that all need to be stored and maintained. The option of being able to store a BIP in any repo doesn’t appear to offer material upside (michaelfolkson). It still needs to get a BIP number from the BIP editors and if the alternative repo is deleted or the BIP champion becomes unresponsive there is the problem of changing the location of where the BIP is stored. It is much easier to monitor a single repo rather than an infinite number of repos that contain BIPs.
1.I want to avoid mentioning projects that are not decentralized however the thing you mentioned is a feature not a bug. Neither anyone needs "quality" certificates from anyone nor approval. People are free to propose anything as improvement for Bitcoin. What gets implemented is a different thing. Also BIP number doesn't make something legit, BIPs can have any names. Example: If I ever create draft a proposal to improve Bitcoin, it will be in my own repository and with a unique name.
2.I am surprised that few influential developers that wanted to improve BIP process earlier by making it more decentralized were not present in either meeting. Also no follow up here on mailing list. So decentralization was only required when you had some issues with Luke Dashjr? Few things are so obvious that even a newbie who starts researching about Bitcoin from today can observe such things.
I tried my best to ask more people to participate in the meeting by tweeting, requested Christopher to attend the meeting and share his thoughts. Thanks everyone who was part of this meeting.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 2268 bytes --]
next reply other threads:[~2021-10-06 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 4:02 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-03 18:22 Michael Folkson
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=MlIlAqo--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@gmail$(echo .)com \
/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