public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Introduction
Date: Mon, 22 Aug 2011 16:45:18 -0400	[thread overview]
Message-ID: <1314045918.7339.1.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <4E52A7BA.1030208@trucoin.com>

Nice to meet you.  Its always nice to have more dedicated developers.

On Mon, 2011-08-22 at 15:02 -0400, Fred Concklin wrote:
> Hey all!
> 
> My name is Fred Concklin and I plan on working on Bitcoin development
> through my position at Trucoin. I thought I'd take this chance to
> introduce myself and go over where I can make contributions.
> 
> I'm great with automated builds and testing for GNU/Linux and BSD
> platforms and generally plan on structuring the bitcoin project into a
> structure compliant with GNU autotools to facilitate testing and bug
> reporting.
autotools yay.  Also, have you seen jenkins.bluematt.me?
> 
> While I mainly spend my time in high level functional programming
> languages these days, I look forward to working on bitcoin and hope
> everybody is patient with my occasional cpp implementation ineptitudes.
No one has complained too much about mine yet, so I think you are safe.
> 
> I'm excited to begin work on bitcoin.
And Id bet everyone here is exited to have you.

Matt




      parent reply	other threads:[~2011-08-22 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 19:02 Fred Concklin
2011-08-22 19:30 ` Douglas Huff
2011-08-22 19:49   ` Luke-Jr
2011-08-22 20:12     ` Douglas Huff
2011-08-23  3:26       ` Fred Concklin
2011-08-23  3:42         ` Jay Weisskopf
2011-08-23  4:20           ` Fred Concklin
2011-08-22 20:45 ` Matt Corallo [this message]

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=1314045918.7339.1.camel@BMThinkPad.lan.bluematt.me \
    --to=bitcoin-list@bluematt$(echo .)me \
    --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