summaryrefslogtreecommitdiff
path: root/f0/a2c66c57577839327cd2e0cd111ff223340b88
blob: 1dca64672f5775ae3bb6540447337083c3569777 (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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
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 <davispuh@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com>
References: <CAJHLa0NXAYh9HzazN6gArUV8y7J8_G0oqkZqPBgibpW0wRNxKQ@mail.gmail.com>
Date: Tue, 19 Aug 2014 15:28:01 +0300
Message-ID: <CAOE4rSx_LoECPp4gsVgvXRGGNEHRoTqRyKorUcPfkYy9RXsgdQ@mail.gmail.com>
From: =?UTF-8?B?RMSBdmlzIE1vc8SBbnM=?= <davispuh@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <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:28:08 -0000

--001a113452564c3dd20500fa9eb6
Content-Type: text/plain; charset=UTF-8

There's actually a pretty good alternative - GitLab
<https://about.gitlab.com/> it's open source, self-hosted and provides
similar features to GitHub


2014-08-19 15:02 GMT+03:00 Jeff Garzik <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-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

<div dir=3D"ltr">There&#39;s actually a pretty good alternative - <a href=
=3D"https://about.gitlab.com/" target=3D"_blank">GitLab</a> it&#39;s open s=
ource, self-hosted and provides similar features to GitHub<div class=3D"gma=
il_extra">
<br><br><div class=3D"gmail_quote">2014-08-19 15:02 GMT+03:00 Jeff Garzik <=
span dir=3D"ltr">&lt;<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank=
">jgarzik@bitpay.com</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"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=3D"http://www.linux.com/news/featured-blogs/203-konstantin-rya=
bitsev/784544-linux-kernel-git-repositories-add-2-factor-authentication" ta=
rget=3D"_blank">http://www.linux.com/news/featured-blogs/203-konstantin-rya=
bitsev/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=3D"http://bitcoin.org" target=3D"_blank">bitcoin.org</a> somewhere,=
 and simply mirroring that to github for each<br>
push.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc.=C2=A0 =C2=A0 =C2=A0 <a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</font></span></blockquote></div><br></div></div>

--001a113452564c3dd20500fa9eb6--