From: Panos Sakkos <panos.sakkos@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Ramping up with bitcoin core engineering?
Date: Mon, 2 Nov 2015 14:30:48 +0100 [thread overview]
Message-ID: <CAERNvEQ6vGvf57N3LdiKZduSMWpyTMyptm-_pVE2y+gBeKtq0Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 593 bytes --]
next reply other threads:[~2015-11-02 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 13:30 Panos Sakkos [this message]
2015-11-02 21:05 ` [bitcoin-dev] Ramping up with bitcoin core engineering? Eric Martindale
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=CAERNvEQ6vGvf57N3LdiKZduSMWpyTMyptm-_pVE2y+gBeKtq0Q@mail.gmail.com \
--to=panos.sakkos@gmail.com \
--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