From: Eric Martindale <eric@ericmartindale•com>
To: Panos Sakkos <panos.sakkos@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Ramping up with bitcoin core engineering?
Date: Mon, 02 Nov 2015 21:05:39 +0000 [thread overview]
Message-ID: <CAAf19WoPd7oZG5MaDfu4Mi0mb=4uv6zGEd1XqLMY7D3sX2UR6A@mail.gmail.com> (raw)
In-Reply-To: <CAERNvEQ6vGvf57N3LdiKZduSMWpyTMyptm-_pVE2y+gBeKtq0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
The Bitcoin.org Development Guide has grown by leaps in bounds this year,
and has two great introductions:
1. https://bitcoin.org/en/development for an overview of how a developer
can contribute,
2. https://bitcoin.org/en/developer-reference for in-detail reference to
how the whole system works.
Other great places to get involved or find more detail include the Bitcoin
Wiki <https://en.bitcoin.it/wiki/Main_Page> and the #bitcoin-dev room on
Freenode <irc://irc.freenode.net/bitcoin-dev>.
Hope that helps!
On Mon, Nov 2, 2015 at 6:03 AM Panos Sakkos via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hey,
>
> I'm interested in helping out with the development of Bitcoin Core.
> I'm used to getting involved with huge projects by starting to write unit
> tests (in order to get familiar with the project's tools, infrastructure
> etc).
>
> Is there any ramp up process (like for example any documentation) that I
> can start with?
>
> Also, if you are a leading a test effort and you need a hand, please 'r'
> me :)
>
> Thanks in advance!
> :panos
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2068 bytes --]
prev parent reply other threads:[~2015-11-02 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 13:30 Panos Sakkos
2015-11-02 21:05 ` Eric Martindale [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='CAAf19WoPd7oZG5MaDfu4Mi0mb=4uv6zGEd1XqLMY7D3sX2UR6A@mail.gmail.com' \
--to=eric@ericmartindale$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=panos.sakkos@gmail$(echo .)com \
/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