Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=g.rowe.froot@gmail.com;
	helo=mail-vc0-f175.google.com; 
MIME-Version: 1.0
Sender: g.rowe.froot@gmail.com
In-Reply-To: <CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
References: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
	<201312051427.44179.luke@dashjr.org>
	<CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
Date: Thu, 5 Dec 2013 20:49:56 +0000
Message-ID: <CAKm8k+2=kSeDALJJLF9hPfuyDyHN+G9Dx6cQRPGgcKRVOW-4aA@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013a29081d5add04eccfacf4
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git
	repository
Precedence: list

--089e013a29081d5add04eccfacf4
Content-Type: text/plain; charset=UTF-8

Personally, I would be more inclined to submit and work on a BIP if it was
in GitHub. It's a regular home from home for me now.


On 5 December 2013 14:43, Jeff Garzik <jgarzik@bitpay.com> wrote:

> This entire discussion is recycled.  Please review the previous
> discussion, before asking the same questions over again.
>
> Properly done, there are FEWER hurdles.  In the previous discussion,
> there was outlined a process whereby the BIPS Editor would receive an
> email, and could take it from there.  No wiki login or bitcoin payment
> required.  More advanced users may submit pull requests.
>
> Compared with a hash-sealed git repo as primary source, the wiki is
> second class.
>
>
> On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <luke@dashjr.org> wrote:
> > On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
> >> Hello all,
> >>
> >> A while ago after discussion on the mailing list a repository was set
> up to
> >> store the BIP documents, as this is deemed a more secure solution than
> >> having them on the wiki:
> >>
> >> https://github.com/bitcoin/bips
> >>
> >> To prevent confusion the next step should probably be to replace the
> BIPs
> >> on the wiki with links to the github documents, with a notice that
> changes
> >> should be proposed on github or mailed to the BIP editor (gmaxwell).
> >>
> >> Agreed?
> >
> > 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.
> >
> > Luke
> >
> >
> ------------------------------------------------------------------------------
> > Sponsored by Intel(R) XDK
> > Develop, test and display web and hybrid apps with a single code base.
> > Download it for free now!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--089e013a29081d5add04eccfacf4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Personally, I would be more inclined to submit and work on=
 a BIP if it was in GitHub. It&#39;s a regular home from home for me now.<b=
r></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 5 =
December 2013 14:43, Jeff Garzik <span dir=3D"ltr">&lt;<a href=3D"mailto:jg=
arzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt;</span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">This entire discussion is recycled. =C2=A0Pl=
ease review the previous<br>
discussion, before asking the same questions over again.<br>
<br>
Properly done, there are FEWER hurdles. =C2=A0In the previous discussion,<b=
r>
there was outlined a process whereby the BIPS Editor would receive an<br>
email, and could take it from there. =C2=A0No wiki login or bitcoin payment=
<br>
required. =C2=A0More advanced users may submit pull requests.<br>
<br>
Compared with a hash-sealed git repo as primary source, the wiki is<br>
second class.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr &lt;<a href=3D"mailto:luke@dashjr.o=
rg">luke@dashjr.org</a>&gt; wrote:<br>
&gt; On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:<br>
&gt;&gt; Hello all,<br>
&gt;&gt;<br>
&gt;&gt; A while ago after discussion on the mailing list a repository was =
set up to<br>
&gt;&gt; store the BIP documents, as this is deemed a more secure solution =
than<br>
&gt;&gt; having them on the wiki:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://github.com/bitcoin/bips" target=3D"_blank">http=
s://github.com/bitcoin/bips</a><br>
&gt;&gt;<br>
&gt;&gt; To prevent confusion the next step should probably be to replace t=
he BIPs<br>
&gt;&gt; on the wiki with links to the github documents, with a notice that=
 changes<br>
&gt;&gt; should be proposed on github or mailed to the BIP editor (gmaxwell=
).<br>
&gt;&gt;<br>
&gt;&gt; Agreed?<br>
&gt;<br>
&gt; I think this would stifle active BIP draft editing. We&#39;re already =
having a<br>
&gt; hard time getting some developers to write BIPs for their proposals - =
I don&#39;t<br>
&gt; think we should be putting up bigger hurdles.<br>
&gt;<br>
&gt; Luke<br>
&gt;<br>
&gt; ----------------------------------------------------------------------=
--------<br>
&gt; Sponsored by Intel(R) XDK<br>
&gt; Develop, test and display web and hybrid apps with a single code base.=
<br>
&gt; Download it for free now!<br>
&gt; <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D111408631&a=
mp;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.ne=
t/gampad/clk?id=3D111408631&amp;iu=3D/4140/ostg.clktrk</a><br>
&gt; _______________________________________________<br>
&gt; Bitcoin-development mailing list<br>
&gt; <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
&gt; <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Sponsored by Intel(R) XDK<br>
Develop, test and display web and hybrid apps with a single code base.<br>
Download it for free now!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D111408631&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D111408631&amp;iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>

--089e013a29081d5add04eccfacf4--