From: rhavar@protonmail•com
To: Daniel R <daniel.g.repp@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Lookinf for issues to contribute to
Date: Sat, 24 Mar 2018 10:50:54 -0400 [thread overview]
Message-ID: <CUwmNgWvHi6PWaF4d3ZV7mWMzRuep-EQoerQuNivqtTirNzGbSi7bXmeQp2sZjh5wRTuTYASGwFmEIv6N7oE2fkmbW4rkFfnfL-WXQjle0E=@protonmail.com> (raw)
In-Reply-To: <CAHtYR9E4GpwBqqmD0HDKutiXeg=cDtpyvhd_+23srv5_c1AFQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Maybe:
https://github.com/bitcoin/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
Just pick something small (even if it's not interesting), struggle with it, struggle with it some more, do a git blame on the parts you need to modify and try contact the person if there's something you need help with.
I'd say start with simple and boring changes, and you'll organically get a better understanding.
But even better, go to:
https://github.com/bitcoin/bitcoin/pulls
And find some issues, reproduce the problem, test the fix -- and look at how the person did it. Post your results/feedback on the pull requests
I think you'll find in bitcoin (and cryptocurrencies in general) there's a lot more demand for elbow grease than advanced maths stuff =)
-Ryan
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On March 24, 2018 8:52 AM, Daniel R via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hey guys,
>
> I want to contribute to bitcoin core. I am an intermediate programmer and want to get started contributing fast. I have already cloned the git repository. Can you maybe direct me to sources where I can learn more about the structure of bitcoin core and specifically to problems where I can get experience working with the source code?
>
> I know Python, C/C++ and a bit of Java. I have advanced knowledge of cryptographic concepts and procedures and try to teach myself some of the math, especially around elliptic curves. I am currently composing a bachelor thesis around the question of Blockchain usage in the car-industry, where I try to look at different aspects of protocol-design.
>
> Best Regards
> Daniel
[-- Attachment #2: Type: text/html, Size: 2539 bytes --]
prev parent reply other threads:[~2018-03-24 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 13:52 Daniel R
2018-03-24 14:50 ` rhavar [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='CUwmNgWvHi6PWaF4d3ZV7mWMzRuep-EQoerQuNivqtTirNzGbSi7bXmeQp2sZjh5wRTuTYASGwFmEIv6N7oE2fkmbW4rkFfnfL-WXQjle0E=@protonmail.com' \
--to=rhavar@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniel.g.repp@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