From: "'Matthew Zipkin' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [meta] moving conceptual discussion for policy changes
Date: Wed, 30 Apr 2025 14:30:26 +0000 [thread overview]
Message-ID: <ni6KOcP4nfh6qeB7hEprfzZJuOtBTK6g7rv1L3IRa2TIXq3XUX-7MWGPCHbBATaxOdgbzEQsZmJhId5a4BkGmRabCxSsN24JGEiR4r67D9Y=@pm.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
The comment brigade on the OPRETURN pull requests has gotten out of hand and I think we should consider adding a new process step for policy changes. The problem is that many users are not participating in the mailing list discussion and so the first time they hear about a policy change is on twitter, where it may feel like it is too late to do anything about it, and users feel disenfranchised. The result is a brigade of comments that are fast, poorly thought out, uninformed, and repetitive.
[https://github.com/bitcoin/bitcoin/pull/32359](https://github.com/bitcoin/bitcoin/pull/32359#issuecomment-2839926151)
https://github.com/bitcoin/bitcoin/pull/32381
meta: https://github.com/bitcoin-core/meta/discussions/18
It might still be possible to try this for OPRETURN policy or if not, I'd really like to try this the next time a policy change or other controversial code change comes up -- anything where "concept ACK" is not a sufficient technical pull request review comment:
What I think we need is a second step between the mailing list and the pull request. GitHub "discussions" are probably the best format for this, either in bitcoin-core/meta or bitcoin/bitcoin.
Taking a hint from Russ' comment in /meta#18, the discussion could be opened with position statements listing all the pro's and con's and most importantly, FAQs and busting myths like "bigger opreturns make it harder to run a full node".
The discussion should actually probably have a click bait title, so the link burns through twitter like wildfire. The whole point is to attract community members to a source of INFORMATION.
And then, after a weekend when the social media storm has rolled over, a nice quiet mature pull request review might be possible.
--
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 email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/ni6KOcP4nfh6qeB7hEprfzZJuOtBTK6g7rv1L3IRa2TIXq3XUX-7MWGPCHbBATaxOdgbzEQsZmJhId5a4BkGmRabCxSsN24JGEiR4r67D9Y%3D%40pm.me.
[-- Attachment #2: Type: text/html, Size: 5574 bytes --]
next reply other threads:[~2025-04-30 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 14:30 'Matthew Zipkin' via Bitcoin Development Mailing List [this message]
2025-04-30 15:49 ` Sjors Provoost
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='ni6KOcP4nfh6qeB7hEprfzZJuOtBTK6g7rv1L3IRa2TIXq3XUX-7MWGPCHbBATaxOdgbzEQsZmJhId5a4BkGmRabCxSsN24JGEiR4r67D9Y=@pm.me' \
--to=bitcoindev@googlegroups.com \
--cc=pinheadmz@pm$(echo .)me \
/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