From: Andreas Petersson <andreas@petersson.at>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] bitcoin.org - remove hackathon
Date: Tue, 17 Jul 2012 11:25:17 +0200 [thread overview]
Message-ID: <50052F7D.10103@petersson.at> (raw)
In-Reply-To: <1342516677.79507.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Am 17.07.2012 11:17, schrieb Amir Taaki:
> Like I really 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 are sponsors.
>
>
Personally, i really don't mind sponsored speakers. If they have
somewhat relevant topics they keep the event from becoming a "circlejerk".
for example i would really like to hear about payments innovation
outside bitcoin.
next prev parent reply other threads:[~2012-07-17 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 17:52 [Bitcoin-development] bitcoin.org - remove hackathon Amir Taaki
2012-07-15 19:15 ` Vladimir Marchenko
2012-07-16 23:47 ` Jeff Garzik
2012-07-17 0:09 ` Luke-Jr
2012-07-17 9:17 ` Amir Taaki
2012-07-17 9:25 ` Andreas Petersson [this message]
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=50052F7D.10103@petersson.at \
--to=andreas@petersson.at \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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