public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] Proposal: allocate Github issue instead of wiki page to BIP discussion
@ 2017-11-03  9:50 Sjors Provoost
  2017-11-03 18:15 ` Aymeric Vitte
  0 siblings, 1 reply; 2+ messages in thread
From: Sjors Provoost @ 2017-11-03  9:50 UTC (permalink / raw)
  To: Bitcoin Dev

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-11-03 18:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-03  9:50 [bitcoin-dev] Proposal: allocate Github issue instead of wiki page to BIP discussion Sjors Provoost
2017-11-03 18:15 ` Aymeric Vitte

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox