>> I can only speak for myself here but I am not particularly concerned about
>> this perception of authority.
> This perception affects Bitcoin.
Personally I would rather have an optimal process that provides
clarity and helps us build better software than be sensitive to
inaccurate perceptions
> A mailing list post is static and a BIP will go normally go through multiple
> edits and revisions so you do need to take advantage of the Git version
> control system. It gets quite unwieldy to attempt to do that via a mailing
> list with every minor suggested edit getting sent to all subscri
Hey Prayank
Thanks for the suggestions.
> bitcoin-dev mailing list link can be considered a BIP and saved in a BIP
> directory. Anyone can create such directories. So BIP is nothing but a
> proposal shared on bitcoin-dev mailing list.
A mailing list post is static and a BIP will go normally go
Hi Michael,
Thanks for sharing the details about the meeting.
Wishlist has some interesting points. I would like to suggest few things:
1.BIP process:
A. Plan and document a proposal
B. Open PR in https://github.com/bitcoin/bips and edit everything properly
C. BIP is assigned a number and
With a new BIP editor (Kalle Alm) in place and Taproot activation
locked in it is probably/possibly as good time as any to revisit the
BIP process and see if we can bolster it, improve it or at least
inform why certain things operate the way they do.
Hence two IRC meetings are being organized, one
