public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jérémie Dubois-Lacoste" <jeremie.dl@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Looking for GREAT C++ developer for exciting opportunity in bitcoin space
Date: Sun, 29 Dec 2013 20:10:42 +0100	[thread overview]
Message-ID: <CAJqsvLC8KX04ZFLzntOecnWtN_mFeH6iTPQJp4_hv4StrVVh2w@mail.gmail.com> (raw)

Hey,

I doubt this list is for this kind of thing. I am following
bitcoin-development since a long time but never participated because I
believe discussions should be well-focused and I never had anything
relevant to say.
Evan, I am pretty sure that emails such as yours will cause the true
discussions between core-dev (or those closely graviting around) to
move elsewhere on a less public channel, where people like me won't be
able to follow them anymore. Thus my request: please post this kind of
things elsewhere, because you are hijacking a list just to target his
audience, but not to contribute relevant content. (A definition
usually describing spam).

Cheers,

Jeremie


2013/12/29 Evan Duffield <eduffield82@gmail•com>:
> Hello,
>
>
> We’re a startup looking for 1 or 2 really good C++ programmer that is
> familiar with the bitcoin internals to help with a for-profit startup.
>
>
> We will be able to provide more information about the project after signing
> a non-compete/non-disclosure agreement. Our coin will be one of the truly
> unique coins that are not just a clone of the original Bitcoin code. In
> short the project will be a merge-mined altcoin that will provide a very
> useful service to the whole crypto-coin ecosystem.
>
>
> If you have added any features to Bitcoin or related technologies this is a
> definite bonus. Please include information about the work you’re done in the
> space.
>
>
> We have detailed plans on how to implement it and the roles we are looking
> to fill. If interested please email eduffield82@gmail•com with a description
> of your work experience and we’ll vett the applications and share our plans
> to see if you’re interested.
>
>
> Thanks,
>
>
> Evan & Kyle
>
> Hawk Financial Group, LLC
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>



             reply	other threads:[~2013-12-29 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29 19:10 Jérémie Dubois-Lacoste [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-29 18:53 Evan Duffield
2013-12-29 19:27 ` Matt Corallo
2013-12-30 23:22 ` Peter Todd
2013-12-31  1:14   ` Luke-Jr
2014-01-03  5:11 ` Troy Benjegerdes

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=CAJqsvLC8KX04ZFLzntOecnWtN_mFeH6iTPQJp4_hv4StrVVh2w@mail.gmail.com \
    --to=jeremie.dl@gmail$(echo .)com \
    --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