From: Sjors Provoost <sjors@sprovoost•nl>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Proposal: allocate Github issue instead of wiki page to BIP discussion
Date: Fri, 3 Nov 2017 10:50:15 +0100 [thread overview]
Message-ID: <FBA2AA31-D63C-479C-B890-A14E6F08B3A4@sprovoost.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
I often find myself wanting to leave relatively small comments on BIP's that are IMO not worth bothering this list.
By default each BIP has a wiki page for discussion, e.g. https://github.com/bitcoin/bips/wiki/Comments:BIP-0150
This is linked to from the Comments-URI field in the BIP.
In order to leave a comment, you have to edit the wiki page. This process seems a bit clunky.
I think it would be better to use Github issues, with one Github issue for each BIP.
One concern might be that the ease of use of Github issues would move discussion away from this list. The issue could be temporarily locked to prevent that. The issue description could contain a standard text explaining what should be discussed there and what would be more appropriate to post on the mailinglist.
Another concern might be confusing between PR's which create and update a BIP, and the discussion issue.
If people think this a good idea, would the next step be to propose a change to the process here?
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#BIP_comments
Or would this be a new BIP?
Sjors
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-11-03 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 9:50 Sjors Provoost [this message]
2017-11-03 18:15 ` Aymeric Vitte
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=FBA2AA31-D63C-479C-B890-A14E6F08B3A4@sprovoost.nl \
--to=sjors@sprovoost$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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