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; 
MIME-Version: 1.0
In-Reply-To: <201312051427.44179.luke@dashjr.org>
References: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
	<201312051427.44179.luke@dashjr.org>
Date: Thu, 5 Dec 2013 15:38:45 +0100
Message-ID: <CA+s+GJC5LB_9n9ktCby=st-2-y-6x2jQ27D9UOo6WzWrD2CQZQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=20cf30223b13a82f4104ecca7c0f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git
	repository
Precedence: list

--20cf30223b13a82f4104ecca7c0f
Content-Type: text/plain; charset=UTF-8

On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr <luke@dashjr.org> 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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Dec 5, 2013 at 3:27 PM, Luke-Jr <span dir=3D"ltr">&lt;<a href=3D"mailto=
:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:<br>
</blockquote><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think this w=
ould stifle active BIP draft editing. We&#39;re already having a<br>
hard time getting some developers to write BIPs for their proposals - I don=
&#39;t<br>
think we should be putting up bigger hurdles.<br></blockquote><div><br></di=
v><div>How is github a hurdle?<br><br></div><div>It&#39;s easy enough to cr=
eate a fork and submit back the changes as a pull request.<br><br></div>
<div>In the case of text documents, this can be completely done through the=
 web interface.<br><br></div><div>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.<br>
<br></div><div>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&#39;s a different story.<br></div><div><br>Regards,<=
br>
</div><div>Wladimir<br></div></div></div></div>

--20cf30223b13a82f4104ecca7c0f--