From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XJiWG-000673-1M for bitcoin-development@lists.sourceforge.net; Tue, 19 Aug 2014 12:28:08 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.171 as permitted sender) client-ip=209.85.216.171; envelope-from=davispuh@gmail.com; helo=mail-qc0-f171.google.com; Received: from mail-qc0-f171.google.com ([209.85.216.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XJiWE-0007JR-SM for bitcoin-development@lists.sourceforge.net; Tue, 19 Aug 2014 12:28:07 +0000 Received: by mail-qc0-f171.google.com with SMTP id r5so6093584qcx.16 for ; Tue, 19 Aug 2014 05:28:01 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.229.84.133 with SMTP id j5mr66325902qcl.14.1408451281171; Tue, 19 Aug 2014 05:28:01 -0700 (PDT) Received: by 10.229.37.137 with HTTP; Tue, 19 Aug 2014 05:28:01 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Aug 2014 15:28:01 +0300 Message-ID: From: =?UTF-8?B?RMSBdmlzIE1vc8SBbnM=?= Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a113452564c3dd20500fa9eb6 X-Spam-Score: 0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (davispuh[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XJiWE-0007JR-SM Subject: Re: [Bitcoin-development] Reconsidering github X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 12:28:08 -0000 --001a113452564c3dd20500fa9eb6 Content-Type: text/plain; charset=UTF-8 There's actually a pretty good alternative - GitLab it's open source, self-hosted and provides similar features to GitHub 2014-08-19 15:02 GMT+03:00 Jeff Garzik : > It would be nice if the issues and git repo for Bitcoin Core were not > on such a centralized service as github, nice and convenient as it is. > > To that end, I note that Linux does its own git repo, and now requires > 2FA: > http://www.linux.com/news/featured-blogs/203-konstantin-ryabitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication > > As a first step, one possibility is putting the primary repo on > bitcoin.org somewhere, and simply mirroring that to github for each > push. > > -- > Jeff Garzik > Bitcoin core developer and open source evangelist > BitPay, Inc. https://bitpay.com/ > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --001a113452564c3dd20500fa9eb6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There's actually a pretty good alternative - GitLab it's open s= ource, self-hosted and provides similar features to GitHub


2014-08-19 15:02 GMT+03:00 Jeff Garzik <= span dir=3D"ltr"><jgarzik@bitpay.com>:
It would be nice if the issues and git repo for Bitcoin Core were not
on such a centralized service as github, nice and convenient as it is.

To that end, I note that Linux does its own git repo, and now requires
2FA: http://www.linux.com/news/featured-blogs/203-konstantin-rya= bitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication=

As a first step, one possibility is putting the primary repo on
bitcoin.org somewhere,= and simply mirroring that to github for each
push.

--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.=C2=A0 =C2=A0 =C2=A0 https://bitpay.com/

---------------------------------------------------------------------------= ---
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a113452564c3dd20500fa9eb6--