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
|
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 <wtogami@gmail.com>) id 1Z4Kvc-0004cL-Bk
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 03:19:16 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.47 as permitted sender)
client-ip=209.85.220.47; envelope-from=wtogami@gmail.com;
helo=mail-pa0-f47.google.com;
Received: from mail-pa0-f47.google.com ([209.85.220.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4Kvb-0001RT-1a
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 03:19:16 +0000
Received: by pabqy3 with SMTP id qy3so56390227pab.3
for <bitcoin-development@lists.sourceforge.net>;
Sun, 14 Jun 2015 20:19:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.68.98.65 with SMTP id eg1mr43891106pbb.72.1434338349373;
Sun, 14 Jun 2015 20:19:09 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Sun, 14 Jun 2015 20:19:09 -0700 (PDT)
In-Reply-To: <CAJHLa0OOnYMuA-8qfHafw5D0zGw_U06PZaAKS2j=Av_KUhgt-A@mail.gmail.com>
References: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
<CAJHLa0OOnYMuA-8qfHafw5D0zGw_U06PZaAKS2j=Av_KUhgt-A@mail.gmail.com>
Date: Sun, 14 Jun 2015 17:19:09 -1000
Message-ID: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7b676f28cd6265051885eb8c
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
(wtogami[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: 1Z4Kvb-0001RT-1a
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 03:19:16 -0000
--047d7b676f28cd6265051885eb8c
Content-Type: text/plain; charset=UTF-8
On Sun, Jun 14, 2015 at 5:15 AM, Jeff Garzik <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
--047d7b676f28cd6265051885eb8c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Jun 14, 2015 at 5:15 AM, Jeff Garzik <span dir=3D"ltr"><<a href=3D"m=
ailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>></spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex"><div dir=3D"ltr"><div>* ACK on moving away fr=
om SourceForge mailing lists - though only once a community-welcomed replac=
ement is up and running</div><div><br></div>* ACK on using LF as a mailing =
infrastructure provider<div><br></div><div>* Research secure mailing list m=
odels, for bitcoin-security.=C2=A0 The list is not ultra high security - we=
all use PGP for that - but it would perhaps be nice to find some spiffy cr=
yptosystem where mailing list participants individually hold keys & the=
refore access.</div><div><br></div></div></blockquote><div><br></div><div>W=
hile I agree this is a good idea, this should not be a precondition for mov=
ing the public bitcoin-dev list.=C2=A0 The security team needs to separatel=
y research/write tools needed for this.</div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
"><jgarzik> warren, wanna just go ahead and create bitcoin-developmen=
t @ LF?=C2=A0</blockquote><div><br></div><div><div><b>More Feedback?</b>=C2=
=A0=C2=A0As for going ahead, perhaps we should wait to hear from more of th=
e other technical leaders?</div></div><div><br></div><div><b><u>More Questi=
ons</u></b></div><div><br></div><div><b>List Name?</b> =C2=A0Would people p=
refer "bitcoin-development" for he new list name instead of a sho=
rter name like "bitcoin-dev"?=C2=A0 I personally like the shorter=
name, but either is fine. =C2=A0<a href=3D"https://lists.linuxfoundation.o=
rg/mailman/listinfo">https://lists.linuxfoundation.org/mailman/listinfo</a>=
currently has "sidechains-dev", and "lightning-dev" is=
moving there sometime soon.</div><div><br></div><div><b>Proposed Cut-Off D=
ate?</b> =C2=A0Then we also need to agree on a date to cut off the old list=
.=C2=A0 Their sysadmin said we could have the new list auto-post from the o=
ld list for a short while.=C2=A0 I wonder how well that works ... if that w=
ill result in double posting if people write to the new and CC the old list=
.=C2=A0 Needs a little research how well it would behave to have both lists=
operating during a transition period.=C2=A0 I think we should announce a c=
ut-off date when posts to the old list is shut off, July 15th, one month fr=
om now.=C2=A0 Thoughts?<br></div><div><br></div><div><b>Moderators?</b> =C2=
=A0Mailman on the new server allows having separate logins for admins and m=
oderators.=C2=A0 I think the admins of the old SF project are gavin, jgarzi=
k and sipa... they are kind of busy.=C2=A0 Perhaps we should identify known=
trusted community members who can help with moderation.=C2=A0 Usually this=
is dealing with "held" messages that are flagged by the spam fil=
ter</div><div><br></div><div>Warren Togami</div></div></div></div>
--047d7b676f28cd6265051885eb8c--
|
