summaryrefslogtreecommitdiff
path: root/70/86809e2b148ac5fc81adc14bba80f5fd4a98c8
blob: 175aa1ca731eaf608e0cf13f2dbc0754c1c4df3e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1XJi7z-0006EC-LH
	for bitcoin-development@lists.sourceforge.net;
	Tue, 19 Aug 2014 12:03:03 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.213.178 as permitted sender)
	client-ip=209.85.213.178; envelope-from=jgarzik@bitpay.com;
	helo=mail-ig0-f178.google.com; 
Received: from mail-ig0-f178.google.com ([209.85.213.178])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XJi7y-0003nx-Mt
	for bitcoin-development@lists.sourceforge.net;
	Tue, 19 Aug 2014 12:03:03 +0000
Received: by mail-ig0-f178.google.com with SMTP id uq10so9423147igb.17
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 19 Aug 2014 05:02:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to
	:content-type;
	bh=9TJMDp8T5BnLc3aWsVxnuCMShqvPYcyiYf9sL0+4ucU=;
	b=k87HSlEp1Dv1I8vjl0A/h7jMynmndd+u3JabWFN8aWn4Ci7tG31BCh2/zZUf2Gi5iI
	O2OnhoF7ll3pqU7PX4ndh2AYitQ/bz1wMb88oi5Ye/4Dfq1aXp/8Qg62wYi5DV/jHR59
	HEU7MA3cMjRLonrTKK10SpvJ3RHypKFdDj4tXEsd2qCxZ3JEnZn7JZ2ohyGqRo3q3sjQ
	i+HxNdEGHDB16Jrj9CIUm5m+PqtvZB7Dn9z2lf13Wwz7SKEwcestrJy605R93XLa0OeU
	Tn/8Ci3AdaKVK8JHv2vjWl5s3+zm/GOjqtpy4R/NXA/BlIpbr2eflHSQzPVr/bBawx1/
	exqA==
X-Gm-Message-State: ALoCoQk5ryzkpltE/qKxm0A9J0Bp3H/kJLFZ7H+4pqo1eeX2UNSnznYFpOqeswLD90NrpJXo2S03
X-Received: by 10.50.107.7 with SMTP id gy7mr5061622igb.15.1408449777146; Tue,
	19 Aug 2014 05:02:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.78 with HTTP; Tue, 19 Aug 2014 05:02:37 -0700 (PDT)
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 19 Aug 2014 08:02:37 -0400
Message-ID: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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 SPF_PASS               SPF: sender matches SPF record
	-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: 1XJi7y-0003nx-Mt
Subject: [Bitcoin-development] Reconsidering github
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 19 Aug 2014 12:03:03 -0000

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/