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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 529451584
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 20:25:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
[209.85.212.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 93763FB
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 20:25:11 +0000 (UTC)
Received: by wiclk2 with SMTP id lk2so44521287wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Sep 2015 13:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=HDmwv1LXwb2mRj2RgvrFb/YhxWyvMB/dwTiolZxjzgE=;
b=FGebDDn0/f4q0FYkEZvCqEFwChhZXCLOB8TOwPpYGMEowmorW1qmSTNKySy50gIV+O
JZVlX0JIrLjPbwVlv4UAwTQ8DqmrCJeKkuOsGNWtfB7UeDWX1sLkbxZTzDEfk78PjWsA
QxaJ1Mbapl7yzNcV+om6dvC5t40zU4+E2OSTMAcOrlcq/saDOLAS0gsJu+XsIAP8kabB
Hm7XfGXctCJHOA9g+r0fjj/jjLjlgRpoeldcnNg5uR4E8iu9HBgvkY3ZshAxjFb6253z
cX1DqeQtWwLkC8bRPDxnw4q3aIOdw1X8+Ou1c3KSRORMLdJecGTWbz6c/pjwwk85HNAc
N3iw==
X-Received: by 10.180.79.34 with SMTP id g2mr160185wix.28.1442607910334; Fri,
18 Sep 2015 13:25:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.21.200 with HTTP; Fri, 18 Sep 2015 13:24:50 -0700 (PDT)
In-Reply-To: <55FC70A5.9080603@mattcorallo.com>
References: <20150918010709.GB5251@amethyst.visucore.com>
<55FC70A5.9080603@mattcorallo.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Fri, 18 Sep 2015 21:24:50 +0100
Message-ID: <CADJgMzsuBrXT1qOAScu+fv_A7Du1XrFoix8nSO14qXj2YD4KtQ@mail.gmail.com>
To: Matt Corallo <lf-lists@mattcorallo.com>
Content-Type: multipart/alternative; boundary=f46d041825d80bb4d605200b547b
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail.com>, Cory Fields <cory@coryfields.com>
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2015 20:25:12 -0000
--f46d041825d80bb4d605200b547b
Content-Type: text/plain; charset=UTF-8
Google calendar is localised, so it doesn't matter. The problem with
quoting UTC anyway it the meeting times are going to change for those that
observe DST. It would be much better to quote an actual timezone of an
actual area so it will remain constant, like 1700 CEST, or 0900AM PDT for
example. Otherwise when the clocks change, what was a convenient meeting
time will become inconvenient for some.
On Fri, Sep 18, 2015 at 9:14 PM, Matt Corallo via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Generally in favor, but for practical purposes can we select a timezone
> that is available in Google Calendar? It appears it does not directly
> support UTC...
>
> On 09/18/15 01:07, Wladimir J. van der Laan via bitcoin-dev wrote:
> > Hello,
> >
> > At Monday's code sprint we had a good idea to schedule a regular
> developer meeting in #bitcoin-dev.
> >
> > Attendance is of course voluntary, but it may be good to have a time
> that many people are expected to be present and current issues can be
> discussed.
> >
> > Any preference for days/times?
> >
> > What about e.g. every week 15:00-16:00 UTC on Thursday?
> >
> > Wladimir
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--f46d041825d80bb4d605200b547b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Google calendar is localised, so it doesn't matter. Th=
e problem with quoting UTC anyway it the meeting times are going to change =
for those that observe DST. It would be much better to quote an actual time=
zone of an actual area so it will remain constant, like 1700 CEST, or 0900A=
M PDT for example. Otherwise when the clocks change, what was a convenient =
meeting time will become inconvenient for some.</div><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On Fri, Sep 18, 2015 at 9:14 PM, Matt C=
orallo via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@=
lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundat=
ion.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Generally i=
n favor, but for practical purposes can we select a timezone<br>
that is available in Google Calendar? It appears it does not directly<br>
support UTC...<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 09/18/15 01:07, Wladimir J. van der Laan via bitcoin-dev wrote:<br>
> Hello,<br>
><br>
> At Monday's code sprint we had a good idea to schedule a regular d=
eveloper meeting in #bitcoin-dev.<br>
><br>
> Attendance is of course voluntary, but it may be good to have a time t=
hat many people are expected to be present and current issues can be discus=
sed.<br>
><br>
> Any preference for days/times?<br>
><br>
> What about e.g. every week 15:00-16:00 UTC on Thursday?<br>
><br>
> Wladimir<br>
> _______________________________________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>
--f46d041825d80bb4d605200b547b--
|
