<div dir="ltr">I believe a better solution would to use a gitlab clone such as gitlab, which sits on top of the git repo, and allows for custom code around the BIP process. Potentially one could even build Bitcoin into such a BIP system. If somebody wants to support a BIP he donates Bitcoins to that proposal. Somebody who actually implements the BIP can receive some percent of the bounty (while some percent goes to the Bitcoin foundation). Via such a platform one could create assurance contracts to kickstart BIP developments or Bitcoin extensions (public infrastructure which is not part of the core, such as opensourced exchanges).</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 21, 2013 at 9:47 PM, Luke-Jr <span dir="ltr"><<a href="mailto:luke@dashjr.org" target="_blank">luke@dashjr.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman wrote:<br>
> 1) Should the protocol specification page also be codified into BIP(s)?<br>
<br>
</div>Probably wouldn't hurt, but it'd likely need a rewrite in a more modular and<br>
formal form.<br>
<div class="im"><br>
> 2) Should the current wiki pages be taken down / forwarded to the git repo<br>
> or be auto updated from the git repo?<br>
<br>
</div>Since it's the same format, I'd keep it up there, maybe with a link to the git<br>
repo on the main BIP index wiki page.<br>
<div class="im"><br>
> 3) Even though the information in BIP 50 is valuable, should it really be<br>
> considered a BIP?<br>
<br>
</div>It's a hardforking protocol change, so IMO yes.<br>
<div class="im"><br>
------------------------------------------------------------------------------<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from<br>
the latest Intel processors and coprocessors. See abstracts and register ><br>
</div><a href="http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk</a><br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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>