Re: [Bitcoin-development] Where do I start?

["Jorge Timón" <jtimon@jtimon.cc>]

[-- 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 --]