From: thomasV1@gmx.de
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Random order for clients page
Date: Mon, 09 Jul 2012 20:29:43 +0200 [thread overview]
Message-ID: <20120709182943.257650@gmx.net> (raw)
In-Reply-To: <CALf2ePwKcRWmaw=S=dFs8QTSg98obyYPoP2U21H5UL30KDBxmA@mail.gmail.com>
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
>
>
>
>
next prev parent reply other threads:[~2012-07-09 18:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:54 [Bitcoin-development] Random order for clients page Amir Taaki
2012-07-09 16:04 ` Gregory Maxwell
2012-07-09 16:09 ` Amir Taaki
2012-07-09 16:39 ` Stefan Thomas
2012-07-09 16:55 ` Harald Schilly
2012-07-09 17:21 ` Luke-Jr
2012-07-09 17:46 ` Gregory Maxwell
2012-07-09 18:03 ` Alan Reiner
2012-07-09 18:29 ` thomasV1 [this message]
2012-07-09 18:18 ` Amir Taaki
2012-07-09 18:30 ` Mike Hearn
2012-07-09 22:26 ` Stefan Thomas
2012-07-09 22:37 ` Mike Hearn
2012-07-10 2:36 ` Stefan Thomas
2012-07-10 2:44 ` Alan Reiner
2012-07-10 3:05 ` Gregory Maxwell
2012-07-10 7:12 ` Wladimir
2012-07-10 9:11 ` Stefan Thomas
2012-07-13 15:20 ` Daniel F
2012-07-09 23:07 ` [Bitcoin-development] Wiki client list (was: Random order for clients page) Luke-Jr
2012-07-09 18:48 ` [Bitcoin-development] Random order for clients page Gregory Maxwell
2012-07-09 20:44 ` Jeff Garzik
2012-07-09 17:33 ` Nils Schneider
2012-07-09 18:24 ` Amir Taaki
2012-07-09 18:54 Jim
2012-07-09 18:57 ` Gregory Maxwell
2012-07-09 19:14 ` Alan Reiner
2012-07-09 20:13 ` Gary Rowe
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=20120709182943.257650@gmx.net \
--to=thomasv1@gmx.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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