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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <thomasV1@gmx.de>) id 1SoIiU-000187-Jw
for bitcoin-development@lists.sourceforge.net;
Mon, 09 Jul 2012 18:29:50 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmx.de
designates 213.165.64.22 as permitted sender)
client-ip=213.165.64.22; envelope-from=thomasV1@gmx.de;
helo=mailout-de.gmx.net;
Received: from mailout-de.gmx.net ([213.165.64.22])
by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1SoIiT-0000CW-Ln for bitcoin-development@lists.sourceforge.net;
Mon, 09 Jul 2012 18:29:50 +0000
Received: (qmail 19252 invoked by uid 0); 9 Jul 2012 18:29:43 -0000
Received: from 84.101.32.141 by www025.gmx.net with HTTP;
Mon, 09 Jul 2012 20:29:43 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Date: Mon, 09 Jul 2012 20:29:43 +0200
From: thomasV1@gmx.de
In-Reply-To: <CALf2ePwKcRWmaw=S=dFs8QTSg98obyYPoP2U21H5UL30KDBxmA@mail.gmail.com>
Message-ID: <20120709182943.257650@gmx.net>
MIME-Version: 1.0
References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<CAAS2fgRd0gqrxXs4Le6nydYBaG7EO=T7FrtX6QZpg3aJtAxSvg@mail.gmail.com>
<1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<CAAS2fgQRo4swDTQjPE0PmnpZ9uS+TDNQdOR6q4K70xsNJY9RfQ@mail.gmail.com>
<CALf2ePwKcRWmaw=S=dFs8QTSg98obyYPoP2U21H5UL30KDBxmA@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
X-Authenticated: #19670841
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX1+TH55WItuTQ2UabFsGVN4gDyDK9IxzszB9kFxwqa
kaoKI8cE34WtJSbzMQZFh/Qi7F/8NKgSqiOA==
Content-Transfer-Encoding: 8bit
X-GMX-UID: QEaJb8EFeSEqXlhER3Uh9M5+IGRvb4CC
X-Spam-Score: -1.2 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [213.165.64.22 listed in list.dnswl.org]
-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
(thomasv1[at]gmx.de)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (thomasv1[at]gmx.de)
X-Headers-End: 1SoIiT-0000CW-Ln
Subject: Re: [Bitcoin-development] Random order for clients page
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: Mon, 09 Jul 2012 18:29:50 -0000
I agree with Alan.
I too am happy to see my client listed on bitcoin.org, and I don't mind Bitcoin-Qt being listed first. I have no problem with a "czar" approach if it can solve conflicts.
I believe that it is useful to keep the 'clients' page on bitcoin.org, because it contributes to clarifying the difference between the Bitcoin client and Bitcoin as a protocol/network/ecosystem. It shows that Bitcoin is much more than its original implementation. It is a sign of health.
Thomas
-------- Original-Nachricht --------
> Datum: Mon, 9 Jul 2012 14:03:55 -0400
> Von: Alan Reiner <etotheipi@gmail.com>
> An: Gregory Maxwell <gmaxwell@gmail.com>
> CC: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net>
> Betreff: Re: [Bitcoin-development] Random order for clients page
> I generally agree with Greg. I don't see anything he's said or done as
> anti-alt-client.
>
> As an alt-client developer, I'm happy to see my client on the main page,
> but I'm also happy if that "clients" page is simply an acknowledgement
> that
> there's more to the Bitcoin world than just the Bitcoin-Qt client, and a
> link of where to find more information (i.e. the wiki). I would still *
> prefer* to have the page the way it is, because I think alt clients should
> be more accessible and word will spread better where it is now -- but I
> also recognize the inherent difficulty of gaining any kind of consensus of
> how it should be organized, what goes on the list, etc, and no matter how
> you do it, someone will complain about it being unfair or not right.
>
> We either have to have a "czar" who is trusted to make responsible
> decisions, and complaints of being unfair or recommendations for
> improvements can go through that person, but ultimately it is that person
> who makes the call. Or we just move it to another page that is less
> strictly controlled and where these things matter less. Trying to gain
> consensus among an amalgamation of developers all with competing
> priorities
> and "products" is a terrible way to try to agree on stuff.
>
> -Alan
>
>
>
>
|
