public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Design Competition
Date: Wed, 30 Sep 2015 07:03:15 -0400	[thread overview]
Message-ID: <560BC173.6040805@bitcoins.info> (raw)
In-Reply-To: <em8c1e6056-06c6-48e7-b975-ac8fb4dae748@platinum>

On 9/30/2015 3:16 AM, Eric Lombrozo via bitcoin-dev wrote:
> I've also got a competition where the object is to build a spaceship
> using only a watermelon, two donkeys, some duct tape, and a fire hydrant.

There are many people interested in starting new services and who are 
interested in hiring developers or at least partnering with them.  This 
is an important part of the ecosystem.  I have noticed both here and on 
Reddit that when someone proposes an idea it goes one of two ways: 
either there is a large amount of interest if the person is well known 
or liked or; the person is accused of being a spammer or made fun of if 
they are not well known or liked.  All this does is make the developers 
look like a small fickle group who actively promote Bitcoin as a an 
insiders' club (much like the Fed).  There should probably be a list 
where people can actively discuss proposed or ongoing projects and look 
for developers to hire.

Russ




  reply	other threads:[~2015-09-30 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  6:37 [bitcoin-dev] Design Competition Richard Olsen
2015-09-30  7:16 ` Eric Lombrozo
2015-09-30 11:03   ` Milly Bitcoin [this message]
2015-09-30 12:22 ` Thomas Kerin
2015-09-30 13:17   ` richard.olsen
2015-09-30 13:38     ` Benjamin
2015-10-01  4:04       ` Dave Scotese
2015-09-30 12:40 ` Jeff Garzik
2015-10-01  4:38 ` odinn

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=560BC173.6040805@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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