From: Aymeric Vitte <vitteaymeric@gmail•com>
To: Sjors Provoost <sjors@sprovoost•nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: allocate Github issue instead of wiki page to BIP discussion
Date: Fri, 3 Nov 2017 19:15:10 +0100 [thread overview]
Message-ID: <551f3289-48cf-a819-5d45-59249498e8c1@gmail.com> (raw)
In-Reply-To: <FBA2AA31-D63C-479C-B890-A14E6F08B3A4@sprovoost.nl>
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
+10k
Indeed, as any project Github issues should be enabled for BIPs,
wondering too since some time why this is not the case, and then if an
issue is worth discussing here it can be redirected to the list
Le 03/11/2017 à 10:50, Sjors Provoost via bitcoin-dev a écrit :
> 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
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
[-- Attachment #2: Type: text/html, Size: 3732 bytes --]
prev parent reply other threads:[~2017-11-03 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 9:50 Sjors Provoost
2017-11-03 18:15 ` Aymeric Vitte [this message]
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=551f3289-48cf-a819-5d45-59249498e8c1@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sjors@sprovoost$(echo .)nl \
/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