Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id CB031CB1 for ; Fri, 3 Nov 2017 18:15:14 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D23DDE1 for ; Fri, 3 Nov 2017 18:15:13 +0000 (UTC) Received: by mail-wm0-f48.google.com with SMTP id z3so3268111wme.5 for ; Fri, 03 Nov 2017 11:15:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=2xV1Tl2xefezRKjpGqTQCMifXPtYzXLQvhSCVYNwCVw=; b=oce0a/3xgoXCWiSkxin49h4rq5Cm5Y2DLdMAtq5IwX3bMS4v7YTf3Ctp/JfuIQANWf iksFtdo2kP4RTGmDQoV4dMaiDf0+WqZZuvW/16q9Y7CNMVeDrh+FM8rotEnkVvFMie9R /BobmZONJ+VSSSOkVBQRkRjdPoYWcyAr7/FjXhvaVO0a0YjwFM5CWp+q58L4qlKr4rdJ YA8rlq83TiJHAUf5uwJ0Yil3mgOUr2mXhonKw/GKZbJK6CacRzENh2Rvssk638Ym2xmy dK8UH04EFfOOAL7CDAlNb946qL+HeZzbF7TWDm81hk+w83ipQyeUt5pzElStHFJ4f6Ec oKdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=2xV1Tl2xefezRKjpGqTQCMifXPtYzXLQvhSCVYNwCVw=; b=aEZLa1mxxPJS87oSCthDNW6LbwYLmTHngVZETriNkFR8N55sBb6AGFJ1iUfdRNlkga nAp7nwUWWAFWWKjZ5vr/PrEHhm7HqdDUpIaJJ6i7d5kB2a3vqCGnXKgYICA9ExdBhK+w BzSX3utaN/wouozKZbexYxrc+OrPSc6AqY7TIbZX3r+21ez84WRS7B6LfXf8lOkEqV15 wWIUn7sBMiFS3m6NoXUl9qdv26IYzGuQrdFNmueu8zJ/43Vmnl1M9KXlkBfJhJTNCXWh SmDW1Su6ulT2WhPIfQs6q3nl+WFn2+gLed+dlGll5U6JNJprSQfKG8ldvcXWVseahBoR nfCg== X-Gm-Message-State: AMCzsaUtaIZzKjLPMZGDKs0Y8yP2+UQKOY9zqQubrax4ddTJlVjI5azh 1RnPjMrX6CxOOg9hwag81jWhcA== X-Google-Smtp-Source: ABhQp+TAtGrMAmyoOyWCCg7QpfysDLMMeJ72pvZ21YgL37UwwWRFVxWoiDEhdZwE4Fa4a7vGHZjPlA== X-Received: by 10.80.212.8 with SMTP id t8mr9992951edh.89.1509732912242; Fri, 03 Nov 2017 11:15:12 -0700 (PDT) Received: from ?IPv6:2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17? ([2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17]) by smtp.googlemail.com with ESMTPSA id k51sm6798337ede.42.2017.11.03.11.15.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Nov 2017 11:15:11 -0700 (PDT) To: Sjors Provoost , Bitcoin Protocol Discussion References: From: Aymeric Vitte Message-ID: <551f3289-48cf-a819-5d45-59249498e8c1@gmail.com> Date: Fri, 3 Nov 2017 19:15:10 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------FC221FEEC47D004330820DF6" Content-Language: fr X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Proposal: allocate Github issue instead of wiki page to BIP discussion X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2017 18:15:14 -0000 This is a multi-part message in MIME format. --------------FC221FEEC47D004330820DF6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit +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 --------------FC221FEEC47D004330820DF6 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit

+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
--------------FC221FEEC47D004330820DF6--