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
159
160
161
162
163
164
165
166
167
168
169
170
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1VXdJr-0004oC-7Q
for bitcoin-development@lists.sourceforge.net;
Sat, 19 Oct 2013 20:40:19 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.172 as permitted sender)
client-ip=209.85.217.172; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f172.google.com;
Received: from mail-lb0-f172.google.com ([209.85.217.172])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VXdJp-0007Qs-82
for bitcoin-development@lists.sourceforge.net;
Sat, 19 Oct 2013 20:40:19 +0000
Received: by mail-lb0-f172.google.com with SMTP id c11so3597314lbj.17
for <bitcoin-development@lists.sourceforge.net>;
Sat, 19 Oct 2013 13:40:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.6.169 with SMTP id c9mr6567699laa.28.1382215210427; Sat,
19 Oct 2013 13:40:10 -0700 (PDT)
Received: by 10.112.89.72 with HTTP; Sat, 19 Oct 2013 13:40:10 -0700 (PDT)
In-Reply-To: <CAKLmikPZhhTs2rf5h52KHLrWB38S=JgiOc+pCPx0FXvT7c_aow@mail.gmail.com>
References: <CAKLmikPZhhTs2rf5h52KHLrWB38S=JgiOc+pCPx0FXvT7c_aow@mail.gmail.com>
Date: Sat, 19 Oct 2013 13:40:10 -0700
Message-ID: <CAAS2fgTcTKAA0Xdzk3xZ-3sWwoPgPGmQdugG-0jjhPmntXitfQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mitar <mmitar@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VXdJp-0007Qs-82
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source
community
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: Sat, 19 Oct 2013 20:40:19 -0000
On Sat, Oct 19, 2013 at 9:38 AM, Mitar <mmitar@gmail.com> wrote:
> Hi!
> Interesting read:
> http://courses.ischool.berkeley.edu/i290m-ocpp/site/article/nmerrill-assi=
gn3.html
Hopefully Nick will show up someplace and offer some specific pointers
to where we failed him.
The only interaction I can find from him on IRC is in #bitcoin, rather
than #bitcoin-dev:
--- Day changed Mon Sep 16 2013
11:45 < csmpls> Hi, I'm interested in contributing to the official
bitcoin project. Is there a mailing list I can join?
11:46 < neo2> csmpls, contributing how?
11:47 < csmpls> neo2 - probably start by approaching a low priority
issue like this one https://github.com/bitcoin/bitcoin/issues/2545
11:48 < michagogo> csmpls: There *is* a mailing list
11:48 < michagogo> ;;google bitcoin-dev mailing list
11:48 <@gribble> SourceForge.net: Bitcoin: bitcoin-development:
<http://sourceforge.net/mailarchive/forum.php?forum_name=3Dbitcoin-developm=
ent>;
Bitcoin-development Info
11:48 < csmpls> Great, thanks.
11:48 < michagogo> I don't know how active it is, though
11:49 < michagogo> There's also the #bitcoin-dev channel
I got involved with Bitcoin without previously interacting with other
contributors (AFAIK) and maybe things have changed in ways invisibly
to me. But I don't think so. Michagogo, who was answering there, is a
newer participant and I don't think anyone knows him from anywhere.
Certainly if things have become less welcome to new participants that
would be bad.
I can point out a number of other recent contributors who, as far as I
can tell, just showed up and stared contributing. But I don't think
that the existence of exceptions is sufficiently strong evidence that
there isn't a problem.
The specific complaints I can extract from that article are:
"I wasn't even allowed to edit the wiki"
I'm confused about this, if he's referring to en.bitcoin.it. Editing
it is open to anyone who is willing to pay the 0.01
(https://en.bitcoin.it/wiki/BitcoinPayment) anti-spam fee. This isn't
a policy set by the bitcoin development community, though I'm not sure
that its a terrible one. I've both paid it on behalf of other users
and made edits on behalf of people who didn't want to go to it. At
least relative to some policy which requires actual approval the
payment antispam is at least open to anyone with Bitcoin.
"My IRC questions about issues on the github page were never answered"
Without a nick I'm unable to find more than the above, unfortunately.
So I don't yet know what we need to improve there.
"#bitcoin-dev would rather talk about conspiracies, or about
destroying other cryptocurrencies"
I've been pretty aggressive about punting out offtopic conversation
from #bitcoin-dev lately. Enough that I worried that my actions would
be the inspiration for this complaint. Much of the time discussion
like that is brought in and primarily continued by people who are not
active in the development community at all, but deflecting it to other
challenge without creating a hostile environment (or one that merely
feels hostile to new people) is hard. Nicks comments themselves may
be a useful thing for me to show to people in the future on that
point.
"Bitcoiners are a bunch of paranoid, anti-authoritarian nutjobs"
I actually don't think that this stereotype accurately reflects the
development community. (In fact, I personally enjoy the great sport of
being called a statist by some of these aformentioned jutjobs, but
none of them are developers). On his other article Nick also asserts
"Most contributors hide their identities", but this is factually
untrue as far as I can tell. (In that same article he writes,
"Bitcoin's core code is written in Typescript, which is compiled into
C++"=E2=80=A6)
"I looked at the many items sitting in pull request purgatory"
Many of the long standing pull requests are actually created by people
with direct commit access. We use a model which has a relatively long
pipeline, a fact which I think is justified by the safety
criticialness of the software and our current shortages of active
review. Hopefully long term motion towards increased codebase
modularity will allow faster merging of "safe" changes.
But I suspect there will always be a backlog, at least of "unsafe" changes.
Which brings me to,
"I didn't even know what I had to do"
Above all, I think the most important takeaway from this is that we
need to have better introductory materials.
One obvious place to put them would be
http://bitcoin.org/en/development but the IRC question makes me
believe that Nick hadn't actually found that page, it's a little
buried.
|
