From: Caleb Roger Davis <moabtek@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Bitcoin development (testing & where to get Wallet code)
Date: Tue, 29 Jul 2014 16:32:19 -0600 [thread overview]
Message-ID: <CALEpF5ab+T6k+QXK-AujQQcYPq_PyoaxB3KDGctRe1KicZpfWA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
I have several Bitcoin contributions I would like to make, mostly for
learning purposes to get started:
1. I would like to contribute to unit and/or other types of tests
(code), not production code.
2. I would like to understand the Bitcoin code (as much as possible from
top to bottom)
3. I would like to write a Bitcoin wallet in another language (so would
like to know where to get the "Bitcoin - Core Wallet" code, but not sure
where it resides.
I am a seasoned software developer, but I do need direction on where to get
started. If there is a wiki doc for new developers that would reduce my
searching and experimentation that would be great.
For each of the three items above, I would like to know the tools and
frameworks I would need to understand and initially work on tests ( how to
run the existing tests to get code coverage and find where coverage is
needed, what is the preferred IDE and full development stack etc ), and
also where to get started looking at the bitcoin core code and also the
wallet code (where is the initial starting point and then I could trace
from there ).
Is there a separate area (github & mailing list) for core wallet
development?
Sincerely,
--
Caleb
[-- Attachment #2: Type: text/html, Size: 1413 bytes --]
next reply other threads:[~2014-07-29 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 22:32 Caleb Roger Davis [this message]
2014-07-29 23:12 ` Felipe Micaroni Lalli
2014-07-30 7:38 ` Caleb Roger Davis
2014-07-30 8:27 ` Andreas Schildbach
2014-07-30 8:37 ` Wladimir
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=CALEpF5ab+T6k+QXK-AujQQcYPq_PyoaxB3KDGctRe1KicZpfWA@mail.gmail.com \
--to=moabtek@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