From: "Jorge Timón" <jtimon@jtimon•cc>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Where do I start?
Date: Thu, 30 Apr 2015 10:08:20 +0200 [thread overview]
Message-ID: <CABm2gDoUixqd3OuqNjH1Lg_sQyzSX9H3HWY+a3==frn7AFybgw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
As Mike says it depends on your interests. But one thing that is almost
always welcomed is improving the tests, and it is unlikely that it
conflicts with other people's PRs (unless they're changing that part of the
code and need to update those tests. Improving documentation is also good
and you can do that while reading the code. Usually I just start cloning,
compiling and changing things as I read, "if I understand this correctly,
this change should not break the tests, if I understand this, this other
change should break the build", etc.
But again, is up to you.
On Apr 16, 2015 2:34 PM, "Mike Hearn" <mike@plan99•net> wrote:
> Hey Gabe,
>
> That's diving into the deep end for sure! :)
>
>> What are some current things that are lacking in Bitcoin core? Or am I
>> better off making something else for the ecosystem?
>>
> That depends on your interests.
>
> Many of the highest priority tasks in Bitcoin Core are rather complicated,
> unfortunately, even for people with experience. You can consult the issue
> tracker to get a feel for it.
>
> Alternatively, there are lots of wallet apps out there and plenty of more
> straightforward projects on them. However they may have less of a research
> flavour.
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2683 bytes --]
next prev parent reply other threads:[~2015-04-30 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANJO25K1Lox5aU-NN-j0An2ujNNHwPWNqX1ZXMs+z1udDZ1LOA@mail.gmail.com>
2015-04-16 2:14 ` gabe appleton
2015-04-16 12:33 ` Mike Hearn
2015-04-30 8:08 ` Jorge Timón [this message]
2015-04-30 9:35 ` Telephone Lemien
2015-04-30 10:28 ` Jorge Timón
2015-04-30 15:50 ` Thomas Kerin
2015-04-16 3:42 Thy Shizzle
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='CABm2gDoUixqd3OuqNjH1Lg_sQyzSX9H3HWY+a3==frn7AFybgw@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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