summaryrefslogtreecommitdiff
path: root/8c/dfdfc4de9dc9255130e1d328d983ccc04099e2
blob: 89f1ffa9cf15ca1430cc1dc26d46106ae296e3c5 (plain)
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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <luke@dashjr.org>) id 1SqvMh-00039W-54
	for bitcoin-development@lists.sourceforge.net;
	Tue, 17 Jul 2012 00:10:11 +0000
X-ACL-Warn: 
Received: from zinan.dashjr.org ([173.242.112.54])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1SqvMe-0007YR-1h for bitcoin-development@lists.sourceforge.net;
	Tue, 17 Jul 2012 00:10:11 +0000
Received: from ishibashi.localnet (unknown [97.96.85.141])
	(Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id CE8F1560530;
	Tue, 17 Jul 2012 00:10:02 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Tue, 17 Jul 2012 00:09:48 +0000
User-Agent: KMail/1.13.7 (Linux/3.4.4-gentoo-nestfix; KDE/4.8.3; x86_64; ; )
References: <1342374776.83467.YahooMailNeo@web121004.mail.ne1.yahoo.com>
	<CA+8xBpd1TZg45Tp5hDzLRGsgJ3bh2=CSxgqjN2WaBPv0i6MxVA@mail.gmail.com>
In-Reply-To: <CA+8xBpd1TZg45Tp5hDzLRGsgJ3bh2=CSxgqjN2WaBPv0i6MxVA@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201207170009.51016.luke@dashjr.org>
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1SqvMe-0007YR-1h
Subject: Re: [Bitcoin-development] bitcoin.org - remove hackathon
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: Tue, 17 Jul 2012 00:10:11 -0000

On Monday, July 16, 2012 11:47:02 PM Jeff Garzik wrote:
> Vladimir does raise a fair point, though.  Hackathon seems appropriate
> for bitcoin.org as it is focused on dev-related activities.  (full
> disclosure: speaking at bitcoin2012.com)  The conference might or
> might not be.  The conference does seem community focused, so I don't
> object to it being on bitcoin.org...  But if consensus prefers
> otherwise, that's OK too.

IMO, bitcoin.org is more community-focussed anyway.
How often do devs use the site, compared to GitHub etc?

Someone else made a pullreq for Bitcoin Magazine; I suggest(ed) that
for-profit organizations should be asked to pitch in some way or another.
Who should organize that, I don't know. If Bitcoin Consultancy/Amir is behind 
the conference, I suggest their/his development contributions should be 
sufficient in that respect.

> PS.  This seems like material for pull requests, which is preferred
> over mailing list email + git push.  When working on the satoshi
> client, we all ACK each other's pull req for anything beyond the
> trivial.

I concur, this should be discussed in a pullreq.