<div dir="ltr">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.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 5 December 2013 14:43, Jeff Garzik <span dir="ltr"><<a href="mailto:jgarzik@bitpay.com" target="_blank">jgarzik@bitpay.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This entire discussion is recycled. Please review the previous<br>
discussion, before asking the same questions over again.<br>
<br>
Properly done, there are FEWER hurdles. In the previous discussion,<br>
there was outlined a process whereby the BIPS Editor would receive an<br>
email, and could take it from there. No wiki login or bitcoin payment<br>
required. More 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="HOEnZb"><div class="h5"><br>
<br>
On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <<a href="mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br>
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:<br>
>> Hello all,<br>
>><br>
>> A while ago after discussion on the mailing list a repository was set up to<br>
>> store the BIP documents, as this is deemed a more secure solution than<br>
>> having them on the wiki:<br>
>><br>
>> <a href="https://github.com/bitcoin/bips" target="_blank">https://github.com/bitcoin/bips</a><br>
>><br>
>> To prevent confusion the next step should probably be to replace the BIPs<br>
>> on the wiki with links to the github documents, with a notice that changes<br>
>> should be proposed on github or mailed to the BIP editor (gmaxwell).<br>
>><br>
>> Agreed?<br>
><br>
> I think this would stifle active BIP draft editing. We're already having a<br>
> hard time getting some developers to write BIPs for their proposals - I don't<br>
> think we should be putting up bigger hurdles.<br>
><br>
> Luke<br>
><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="http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. <a href="https://bitpay.com/" target="_blank">https://bitpay.com/</a><br>
</font></span><div class="HOEnZb"><div class="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="http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div>