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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <wtogami@gmail.com>) id 1Z514R-0004c2-00
for bitcoin-development@lists.sourceforge.net;
Wed, 17 Jun 2015 00:19:11 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.174 as permitted sender)
client-ip=209.85.192.174; envelope-from=wtogami@gmail.com;
helo=mail-pd0-f174.google.com;
Received: from mail-pd0-f174.google.com ([209.85.192.174])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z514P-0006gi-TY
for bitcoin-development@lists.sourceforge.net;
Wed, 17 Jun 2015 00:19:10 +0000
Received: by pdjm12 with SMTP id m12so25071906pdj.3
for <bitcoin-development@lists.sourceforge.net>;
Tue, 16 Jun 2015 17:19:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.161.102 with SMTP id xr6mr5422136pab.8.1434500344232;
Tue, 16 Jun 2015 17:19:04 -0700 (PDT)
Received: by 10.70.93.72 with HTTP; Tue, 16 Jun 2015 17:19:04 -0700 (PDT)
In-Reply-To: <CAEz79PrjoD3fvwqmr2+O+8myeQCV_4ZuX4q9zCkQdN=i=ovuMA@mail.gmail.com>
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>
Date: Tue, 16 Jun 2015 14:19:04 -1000
Message-ID: <CAEz79PphLdxOSVrL0r45mYF+XLFzWwB=-KAT-rb=GLb+tMp6+w@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7b6d812072c69b0518aba3f7
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: 1Z514P-0006gi-TY
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: Wed, 17 Jun 2015 00:19:11 -0000
--047d7b6d812072c69b0518aba3f7
Content-Type: text/plain; charset=UTF-8
On Sun, Jun 14, 2015 at 5:19 PM, Warren Togami Jr. <wtogami@gmail.com>
wrote:
>
> *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.
>
We're going ahead with "bitcoin-dev". A request for creation is now
pending.
>
> *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?
>
Off-list I heard a suggestion to make the cut-off date as short as one week
after the new list is announced and people are given the option to
subscribe. Could people please post feelings about this?
It seems most everyone agreed not to auto-subscribe everyone onto the new
list as that tends to be upsetting.
There is clarity if subscribing the old list to the new list is a good
idea. Is anyone familiar with Mailman, is it smart enough to somehow
prevent double-posts if someone writes to both the old and new address?
Warren Togami
--047d7b6d812072c69b0518aba3f7
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:19 PM, Warren Togami Jr. <span dir=3D"ltr"><<a hre=
f=3D"mailto:wtogami@gmail.com" target=3D"_blank">wtogami@gmail.com</a>><=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div><div><b>List Nam=
e?</b> =C2=A0Would people prefer "bitcoin-development" for he new=
list name instead of a shorter name like "bitcoin-dev"?=C2=A0 I =
personally like the shorter name, but either is fine. =C2=A0<a href=3D"http=
s://lists.linuxfoundation.org/mailman/listinfo" target=3D"_blank">https://l=
ists.linuxfoundation.org/mailman/listinfo</a> currently has "sidechain=
s-dev", and "lightning-dev" is moving there sometime soon.</=
div></div></div></div></blockquote><div><br></div><div>We're going ahea=
d with "bitcoin-dev".=C2=A0 A request for creation is now pending=
.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><di=
v class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div><div><b>P=
roposed Cut-Off Date?</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 aut=
o-post from the old list for a short while.=C2=A0 I wonder how well that wo=
rks ... if that will result in double posting if people write to the new an=
d CC the old list.=C2=A0 Needs a little research how well it would behave t=
o have both lists operating during a transition period.=C2=A0 I think we sh=
ould announce a cut-off date when posts to the old list is shut off, July 1=
5th, one month from now.=C2=A0 Thoughts?<br></div></div></div></div></block=
quote><div><br></div><div>Off-list I heard a suggestion to make the cut-off=
date as short as one week after the new list is announced and people are g=
iven the option to subscribe.=C2=A0 Could people please post feelings about=
this?</div><div><br></div><div>It seems most everyone agreed not to auto-s=
ubscribe everyone onto the new list as that tends to be upsetting.</div><di=
v><br></div><div>There is clarity if subscribing the old list to the new li=
st is a good idea.=C2=A0 Is anyone familiar with Mailman, is it smart enoug=
h to somehow prevent double-posts if someone writes to both the old and new=
address?=C2=A0</div><div><br></div><div>Warren Togami</div></div></div></d=
iv>
--047d7b6d812072c69b0518aba3f7--
|
