public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org - remove hackathon
Date: Tue, 17 Jul 2012 00:09:48 +0000	[thread overview]
Message-ID: <201207170009.51016.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpd1TZg45Tp5hDzLRGsgJ3bh2=CSxgqjN2WaBPv0i6MxVA@mail.gmail.com>

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.



  reply	other threads:[~2012-07-17  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 17:52 Amir Taaki
2012-07-15 19:15 ` Vladimir Marchenko
2012-07-16 23:47 ` Jeff Garzik
2012-07-17  0:09   ` Luke-Jr [this message]
2012-07-17  9:17     ` Amir Taaki
2012-07-17  9:25       ` Andreas Petersson
2012-07-17  9:54         ` Amir Taaki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201207170009.51016.luke@dashjr.org \
    --to=luke@dashjr$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox