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
|
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 <bitcoin-list@bluematt.me>) id 1RhpMo-0006gN-KZ
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Jan 2012 21:24:26 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bluematt.me
designates 173.246.101.161 as permitted sender)
client-ip=173.246.101.161;
envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RhpMn-0005lb-91 for bitcoin-development@lists.sourceforge.net;
Mon, 02 Jan 2012 21:24:26 +0000
Received: from [192.168.3.106] (66-87-119-204.pools.spcsdns.net
[66.87.119.204])
by mail.bluematt.me (Postfix) with ESMTPSA id 3912B3F8
for <bitcoin-development@lists.sourceforge.net>;
Mon, 2 Jan 2012 22:17:35 +0100 (CET)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <1325520286.43835.YahooMailNeo@web121005.mail.ne1.yahoo.com>
References: <1325520286.43835.YahooMailNeo@web121005.mail.ne1.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 02 Jan 2012 13:24:12 -0800
Message-ID: <1325539452.3500.1.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.8 (--)
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 SPF_PASS SPF: sender matches SPF record
-1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RhpMn-0005lb-91
Subject: Re: [Bitcoin-development] Meeting 21:00 UTC #bitcoin-dev Freenode
IRC
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, 02 Jan 2012 21:24:26 -0000
Because many made the mistake and it isnt specified in this email, this
meeting is tomorrow (not 30 minutes ago).
On Mon, 2012-01-02 at 08:04 -0800, Amir Taaki wrote:
> This meeting is to discuss the new OP_EVAL changes coming to bitcoin.
>
> A good summary of the past discussion so far by justmoon can be found:
> http://privatepaste.com/4088b049af
>
> Hopefully this can become a weekly thing. For now this is to discuss and inform about the coming changes to bitcoin.
>
> ----------
>
> Where: Freenode IRC #bitcoin-dev
> When: 21:00 UTC (16:00 New York time) until 22:00*
> What: OP_EVAL
>
> Bitcoin is starting decentralising as any healthy free thinking community
> should. Projects are thiving and the economy is growing. New ideas are
> being realised and will edge out old models disruptively.
>
> My hope is that we don't all become fractured. By having weekly regular
> meetings, projects can harmonise in lock step. Concepts and algorithms can
> be proposed and debated. You'd be surprised what having a scheduled regular
> platform can achieve. A soap-box on an island in central waters.
>
> For me, I don't have time to wade through IRC discussions, forum posts and
> mailing lists. At least if the important things are discussed in one place
> it makes bitcoin development and the system more accessible.
>
> Before meeting:
>
> - A wiki page is created for in advance of a weekly meeting.
> - Announced on forums/mailing lists.
> - Throughout the week talking points are added to the meeting page.
>
> After:
>
> - Log of discussion is posted online.
> - I will type an accessible summary for the community at large on
> http://bitcoinmedia.com/
> - Next weekly meeting is scheduled.
>
> Amir Taaki
>
> *We can go over this hour, but this is to stop meetings dwindling off topic
> into banal banter and stay focused.
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
