1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1YnjWH-0007Cb-5D
for bitcoin-development@lists.sourceforge.net;
Thu, 30 Apr 2015 08:08:29 +0000
Received: from mail-wi0-f170.google.com ([209.85.212.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YnjWF-0002Ts-4S
for bitcoin-development@lists.sourceforge.net;
Thu, 30 Apr 2015 08:08:29 +0000
Received: by wief7 with SMTP id f7so7006269wie.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 30 Apr 2015 01:08:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=Jc0MBylzzzovetjTkIuA2Oc8dB7/EaFmCVlM23bWPDM=;
b=GgVgHZVK8MwkpuFk1yfmw/ANYMlJ1v1fW+GF++C1ATaLHBmQyTx3fpLscFIXyMpTGR
SvKf9vtw7ByAHAojZIVw7IwbIo7UMu/YlxqRAVOgqajlz/NERb+nHbW4/JAVDOl9c+mn
iCQQre1a1XCKRGFASCgGtYWnxXr59euD/zT5AHThyrjDub2veTYZB7DjuSAP6X1ZMrQe
vBplsb97zGQOY6FvV3Y4dk7aeULMiuLIIY545Uk+E+2oHiTIy6FnLXRljwAnI1IGUeUs
yiiHYeagzXH8C33LXXgVHGgN9qWKFHFBbued0FZyxrm/KMkpQdR+aXimBT3hVF3BNFml
ppLQ==
X-Gm-Message-State: ALoCoQkNwR9H//24WShP33uS85XPBVF3tYjJNhKj2pp+aJmh5FWTteAYe4vom3qTtnRVEMrjk5c4
MIME-Version: 1.0
X-Received: by 10.195.17.196 with SMTP id gg4mr5858683wjd.109.1430381300964;
Thu, 30 Apr 2015 01:08:20 -0700 (PDT)
Received: by 10.194.124.2 with HTTP; Thu, 30 Apr 2015 01:08:20 -0700 (PDT)
Received: by 10.194.124.2 with HTTP; Thu, 30 Apr 2015 01:08:20 -0700 (PDT)
In-Reply-To: <CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com>
References: <CANJO25K1Lox5aU-NN-j0An2ujNNHwPWNqX1ZXMs+z1udDZ1LOA@mail.gmail.com>
<CANJO25KXoYXKZf-TZRD3HviU141+rYUB2d=4Xf9DqRrzD9P94w@mail.gmail.com>
<CANEZrP0vJug1tGNiL5wQUuA0-rr3eM1Yp8DbO3Apiu1CX=j3bQ@mail.gmail.com>
Date: Thu, 30 Apr 2015 10:08:20 +0200
Message-ID: <CABm2gDoUixqd3OuqNjH1Lg_sQyzSX9H3HWY+a3==frn7AFybgw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=089e01681bbe5678710514ec99b6
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YnjWF-0002Ts-4S
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Where do I start?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 08:08:29 -0000
--089e01681bbe5678710514ec99b6
Content-Type: text/plain; charset=UTF-8
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
>
>
--089e01681bbe5678710514ec99b6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">As Mike says it depends on your interests. But one thing tha=
t 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 i=
s also good and you can do that while reading the code. Usually I just star=
t cloning, compiling and changing things as I read, "if I understand t=
his correctly, this change should not break the tests, if I understand this=
, this other change should break the build", etc.<br>
But again, is up to you.</p>
<div class=3D"gmail_quote">On Apr 16, 2015 2:34 PM, "Mike Hearn" =
<<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hey Gabe=
,<div><br></div><div>That's diving into the deep end for sure! :)</div>=
<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><p dir=3D"ltr">What are some current things that are lacking in B=
itcoin core? Or am I better off making something else for the ecosystem?</p=
></blockquote><div>That depends on your interests.</div><div><br></div><div=
>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.</div><div><br></div><div>Alternatively, there=
are lots of wallet apps out there and plenty of more straightforward proje=
cts on them. However they may have less of a research flavour.</div></div><=
/div></div>
<br>-----------------------------------------------------------------------=
-------<br>
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT<br>
Develop your own process in accordance with the BPMN 2 standard<br>
Learn Process modeling best practices with Bonita BPM through live exercise=
s<br>
<a href=3D"http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-=
" target=3D"_blank">http://www.bonitasoft.com/be-part-of-it/events/bpm-camp=
-virtual-</a> event?utm_<br>
source=3DSourceforge_BPM_Camp_5_6_15&utm_medium=3Demail&utm_campaig=
n=3DVA_SF<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div>
--089e01681bbe5678710514ec99b6--
|
