From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Voa4s-0002G2-3J for bitcoin-development@lists.sourceforge.net; Thu, 05 Dec 2013 14:38:54 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.45 as permitted sender) client-ip=209.85.214.45; envelope-from=laanwj@gmail.com; helo=mail-bk0-f45.google.com; Received: from mail-bk0-f45.google.com ([209.85.214.45]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Voa4q-0007QC-AX for bitcoin-development@lists.sourceforge.net; Thu, 05 Dec 2013 14:38:54 +0000 Received: by mail-bk0-f45.google.com with SMTP id mx13so7155094bkb.18 for ; Thu, 05 Dec 2013 06:38:45 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.205.10.132 with SMTP id pa4mr55713889bkb.15.1386254325777; Thu, 05 Dec 2013 06:38:45 -0800 (PST) Received: by 10.204.69.197 with HTTP; Thu, 5 Dec 2013 06:38:45 -0800 (PST) In-Reply-To: <201312051427.44179.luke@dashjr.org> References: <201312051427.44179.luke@dashjr.org> Date: Thu, 5 Dec 2013 15:38:45 +0100 Message-ID: From: Wladimir To: Luke-Jr Content-Type: multipart/alternative; boundary=20cf30223b13a82f4104ecca7c0f X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: dashjr.org] 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Voa4q-0007QC-AX Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 14:38:54 -0000 --20cf30223b13a82f4104ecca7c0f Content-Type: text/plain; charset=UTF-8 On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr wrote: > On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote: > > I think this would stifle active BIP draft editing. We're already having a > hard time getting some developers to write BIPs for their proposals - I > don't > think we should be putting up bigger hurdles. > How is github a hurdle? It's easy enough to create a fork and submit back the changes as a pull request. In the case of text documents, this can be completely done through the web interface. If anything creating a github account is a smaller hurdle than having to pay to create a wiki account and wait for it to be activated. Aside: my proposal is for the BIPs that are already accepted, and should not be edited without dicussion. If people want to put their drafts in the wiki that's a different story. Regards, Wladimir --20cf30223b13a82f4104ecca7c0f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Dec 5, 2013 at 3:27 PM, Luke-Jr <luke@dashjr.org> wrote:
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
=C2=A0
I think this w= ould stifle active BIP draft editing. We're already having a
hard time getting some developers to write BIPs for their proposals - I don= 't
think we should be putting up bigger hurdles.

How is github a hurdle?

It's easy enough to cr= eate a fork and submit back the changes as a pull request.

In the case of text documents, this can be completely done through the= web interface.

If anything creating a github account is = a smaller hurdle than having to pay to create a wiki account and wait for i= t to be activated.

Aside: my proposal is for the BIPs that are already accepted= , and should not be edited without dicussion. If people want to put their d= rafts in the wiki that's a different story.

Regards,<= br>
Wladimir
--20cf30223b13a82f4104ecca7c0f--