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
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <odinn.cyberguerrilla@riseup.net>) id 1Z4QS7-0008QU-J5
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 09:13:11 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of riseup.net
designates 198.252.153.129 as permitted sender)
client-ip=198.252.153.129;
envelope-from=odinn.cyberguerrilla@riseup.net;
helo=mx1.riseup.net;
Received: from mx1.riseup.net ([198.252.153.129])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Z4QS6-0003hy-0b
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 09:13:11 +0000
Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.riseup.net",
Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
by mx1.riseup.net (Postfix) with ESMTPS id 1AAA641E7A
for <bitcoin-development@lists.sourceforge.net>;
Mon, 15 Jun 2015 09:13:04 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
(Authenticated sender: odinn.cyberguerrilla)
with ESMTPSA id D5C3A4271C
Message-ID: <557E971F.3010908@riseup.net>
Date: Mon, 15 Jun 2015 02:13:03 -0700
From: odinn <odinn.cyberguerrilla@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com> <CAJHLa0OOnYMuA-8qfHafw5D0zGw_U06PZaAKS2j=Av_KUhgt-A@mail.gmail.com>
<CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>
In-Reply-To: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.98.7 at mx1
X-Virus-Status: Clean
X-Spam-Score: -1.9 (-)
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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [198.252.153.129 listed in list.dnswl.org]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
0.2 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z4QS6-0003hy-0b
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a
Neutral Competent Entity
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: Mon, 15 Jun 2015 09:13:11 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What about Gittorrent?
http://blog.printf.net/articles/2015/05/29/announcing-gittorrent-a-decen
tralized-github/
On 06/14/2015 08:19 PM, Warren Togami Jr. wrote:
> On Sun, Jun 14, 2015 at 5:15 AM, Jeff Garzik <jgarzik@bitpay.com
> <mailto:jgarzik@bitpay.com>> wrote:
>
> * ACK on moving away from SourceForge mailing lists - though only
> once a community-welcomed replacement is up and running
>
> * ACK on using LF as a mailing infrastructure provider
>
> * Research secure mailing list models, for bitcoin-security. The
> list is not ultra high security - we all use PGP for that - but it
> would perhaps be nice to find some spiffy cryptosystem where
> mailing list participants individually hold keys & therefore
> access.
>
>
> While I agree this is a good idea, this should not be a
> precondition for moving the public bitcoin-dev list. The security
> team needs to separately research/write tools needed for this.
>
> <jgarzik> warren, wanna just go ahead and create
> bitcoin-development @ LF?
>
>
> *More Feedback?* As for going ahead, perhaps we should wait to
> hear from more of the other technical leaders?
>
> *_More Questions_*
>
> *List Name?* Would people prefer "bitcoin-development" for he new
> list name instead of a shorter name like "bitcoin-dev"? I
> personally like the shorter name, but either is fine.
> https://lists.linuxfoundation.org/mailman/listinfo currently has
> "sidechains-dev", and "lightning-dev" is moving there sometime
> soon.
>
> *Proposed Cut-Off Date?* Then we also need to agree on a date to
> cut off the old list. Their sysadmin said we could have the new
> list auto-post from the old list for a short while. I wonder how
> well that works ... if that will result in double posting if people
> write to the new and CC the old list. Needs a little research how
> well it would behave to have both lists operating during a
> transition period. I think we should announce a cut-off date when
> posts to the old list is shut off, July 15th, one month from now.
> Thoughts?
>
> *Moderators?* Mailman on the new server allows having separate
> logins for admins and moderators. I think the admins of the old SF
> project are gavin, jgarzik and sipa... they are kind of busy.
> Perhaps we should identify known trusted community members who can
> help with moderation. Usually this is dealing with "held" messages
> that are flagged by the spam filter
>
> Warren Togami
>
>
> ----------------------------------------------------------------------
- --------
>
>
>
>
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVfpcfAAoJEGxwq/inSG8CEdsH+weboFo8SCbwgoe68oZLl6Et
r4JtzZRu8jtw5x6AYcpVMBvUo3CHtbYCWREidBhvSU+TlOUjnxZRU5CjLpjHcc61
QV2hIGD1RUdrcj93PBsnNrvuXkLVHd09sKXCIvldY1d1GqTqy9sVY1skExd7zY2h
LmJhLdmNw7I+gLP/r8Ivl7aDqrpzHXr7pnbFXZZ0hxhthncxXTefi/IV+kAt3ptL
qfSRYGPyyUXWLfXF/XW+/DH+scZm+Iu/SSoSa6xnEo4MgY4HzZM2Uy+9Te9aO6wd
xvdpMetZV5A9Ljr8Ww72DPDkvUprk7u55OMgZZ4Fps53PnqwpNOjt3phIUH4iVE=
=6Fxw
-----END PGP SIGNATURE-----
|
