<div dir="ltr">There&#39;s actually a pretty good alternative - <a href="https://about.gitlab.com/" target="_blank">GitLab</a> it&#39;s open source, self-hosted and provides similar features to GitHub<div class="gmail_extra">
<br><br><div class="gmail_quote">2014-08-19 15:02 GMT+03:00 Jeff Garzik <span dir="ltr">&lt;<a href="mailto:jgarzik@bitpay.com" target="_blank">jgarzik@bitpay.com</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It would be nice if the issues and git repo for Bitcoin Core were not<br>
on such a centralized service as github, nice and convenient as it is.<br>
<br>
To that end, I note that Linux does its own git repo, and now requires<br>
2FA: <a href="http://www.linux.com/news/featured-blogs/203-konstantin-ryabitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication" target="_blank">http://www.linux.com/news/featured-blogs/203-konstantin-ryabitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication</a><br>

<br>
As a first step, one possibility is putting the primary repo on<br>
<a href="http://bitcoin.org" target="_blank">bitcoin.org</a> somewhere, and simply mirroring that to github for each<br>
push.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<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>
<br>
------------------------------------------------------------------------------<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>
</font></span></blockquote></div><br></div></div>