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
|
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 <zgenjix@yahoo.com>) id 1Sr3uz-0004BB-7p
for bitcoin-development@lists.sourceforge.net;
Tue, 17 Jul 2012 09:18:09 +0000
X-ACL-Warn:
Received: from nm29.bullet.mail.ne1.yahoo.com ([98.138.90.92])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1Sr3ut-0006UT-DG for bitcoin-development@lists.sourceforge.net;
Tue, 17 Jul 2012 09:18:09 +0000
Received: from [98.138.90.51] by nm29.bullet.mail.ne1.yahoo.com with NNFMP;
17 Jul 2012 09:17:57 -0000
Received: from [98.138.89.167] by tm4.bullet.mail.ne1.yahoo.com with NNFMP;
17 Jul 2012 09:17:57 -0000
Received: from [127.0.0.1] by omp1023.mail.ne1.yahoo.com with NNFMP;
17 Jul 2012 09:17:57 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 769349.41419.bm@omp1023.mail.ne1.yahoo.com
Received: (qmail 4592 invoked by uid 60001); 17 Jul 2012 09:17:57 -0000
X-YMail-OSG: TFmqtCsVM1nTvOXK4p9oRM9VaoXpXUHn3R7QPh5OM3ttWG.
Pr831J52eR1JPU.gNybDct1hesylrTzTWHEmewD1R1qgZmMUBpl33cgPEzqg
1U3RjeBoXvw24.kcxZ_xeyVXavDOPauNdK4sfw1uiZcRwOA9ZawTlSa.Mpv7
BmjQsHWfv2J2VlNb0Iav6I6sDB6qbejaKLaMPVmEyzdiHTiY2t3lgZJWs4Xm
sqv7AHRrFLZcvZ4m.D8pj5g_Bwb1SwafPNn5y0FTxDKTuC_s28mniy8LWJG_
3DujgKSxYbVlvaXn.Ykm5B.UUhd.BbK3YtGmS6Gi3jWnJjHA4C.4qCY6tjzC
EqjY0854RXwwSM6Zn8IKs5K0Jv8h_B_erqWYgH4hbUu43vE7Cd4dJ0BIH_Oa
DVAlbwtVR2CkKi7gH5xmENCcnIU9BSV50umAhtb0uj52z5J8mrVkSW_tqxbV
mi.fl2IopvRB9LtJf4e3uldpoPaYpyGvX13OINgwKFao6yyj0_Mlxcu4qbw8
bUn_m_cDNY5LAUInD7LYbWwHlfMJ4I5g-
Received: from [178.5.23.109] by web121006.mail.ne1.yahoo.com via HTTP;
Tue, 17 Jul 2012 02:17:57 PDT
X-Mailer: YahooMailWebService/0.8.120.356233
References: <1342374776.83467.YahooMailNeo@web121004.mail.ne1.yahoo.com>
<CA+8xBpd1TZg45Tp5hDzLRGsgJ3bh2=CSxgqjN2WaBPv0i6MxVA@mail.gmail.com>
<201207170009.51016.luke@dashjr.org>
Message-ID: <1342516677.79507.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Tue, 17 Jul 2012 02:17:57 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <201207170009.51016.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.90.92 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.0 T_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 FSL_FREEMAIL_2 FSL_FREEMAIL_2
0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1
X-Headers-End: 1Sr3ut-0006UT-DG
Subject: Re: [Bitcoin-development] bitcoin.org - remove hackathon
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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: Tue, 17 Jul 2012 09:18:09 -0000
OK, pull request seems good.=0A=0AFYI we lost money on last year's conferen=
ce, and are hoping to break even this year. The only people to make profit =
will be nefario and anyone else we give a share in it (people who help real=
ise it). Otherwise money made goes towards next year's conference and payin=
g for things to make a better conference (like Gavin wanted to attend but c=
ouldn't afford a ticket). It is not a commercial event, and I've been pushi=
ng to keep the sponsorship and community parts highly separated. Like I rea=
lly do not wish to sell a speaker slot, but if I have to (to pay the bills)=
then it will be obvious due to scheduling and disclaimers that speakers ar=
e sponsors.=0A=0A=0A=0A----- Original Message -----=0AFrom: Luke-Jr <luke@d=
ashjr.org>=0ATo: bitcoin-development@lists.sourceforge.net=0ACc: Jeff Garzi=
k <jgarzik@exmulti.com>; Amir Taaki <zgenjix@yahoo.com>=0ASent: Tuesday, Ju=
ly 17, 2012 2:09 AM=0ASubject: Re: [Bitcoin-development] bitcoin.org - remo=
ve hackathon=0A=0AOn Monday, July 16, 2012 11:47:02 PM Jeff Garzik wrote:=
=0A> Vladimir does raise a fair point, though.=A0 Hackathon seems appropria=
te=0A> for bitcoin.org as it is focused on dev-related activities.=A0 (full=
=0A> disclosure: speaking at bitcoin2012.com)=A0 The conference might or=0A=
> might not be.=A0 The conference does seem community focused, so I don't=
=0A> object to it being on bitcoin.org...=A0 But if consensus prefers=0A> o=
therwise, that's OK too.=0A=0AIMO, bitcoin.org is more community-focussed a=
nyway.=0AHow often do devs use the site, compared to GitHub etc?=0A=0ASomeo=
ne else made a pullreq for Bitcoin Magazine; I suggest(ed) that=0Afor-profi=
t organizations should be asked to pitch in some way or another.=0AWho shou=
ld organize that, I don't know. If Bitcoin Consultancy/Amir is behind =0Ath=
e conference, I suggest their/his development contributions should be =0Asu=
fficient in that respect.=0A=0A> PS.=A0 This seems like material for pull r=
equests, which is preferred=0A> over mailing list email + git push.=A0 When=
working on the satoshi=0A> client, we all ACK each other's pull req for an=
ything beyond the=0A> trivial.=0A=0AI concur, this should be discussed in a=
pullreq.=0A
|
