public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@exmulti.com>
To: Amir Taaki <zgenjix@yahoo.com>
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Wed, 2 May 2012 19:04:08 -0400	[thread overview]
Message-ID: <CA+8xBpdsOWdBwEhO2pAAMZiEyvcr-xZL-EnmSsb-vMtowDyu4w@mail.gmail.com> (raw)
In-Reply-To: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>

On Mon, Apr 30, 2012 at 1:50 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> Check it :) https://github.com/bitcoin/bitcoin.org/pull/34

Personally, all this seems far too focused on a centralized website
(bitcoin.org), and presents far too many choices at once to the user.

On bitcoin.org (registered by Satoshi), I would rather see the Satoshi
reference client and perhaps an "other clients" link on the wiki.

Modern websites are working hard to _reduce_ the number of download
links, not _increase_ them.  See, e.g.
http://fedoraproject.org/en/get-fedora where a single download choice
is presented, and then an "other options" link is below the great big
download button.

Rather than fighting over what a particular bitcoin.org page should
look like, why not maintain an independently managed
BitcoinClients.org website?  Or GetBitcoinClient.org or somesuch.

Solve this problem in a distributed fashion, rather than stuffing it
all onto bitcoin.org.  Bitcoin.org, IMO, is the home of the "reference
project" not the entire bitcoin community.  Emphasizing that months
ago was why the forum was moved to bitcointalk.org.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com



  parent reply	other threads:[~2012-05-02 23:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 17:50 [Bitcoin-development] new bitcoin.org clients page Amir Taaki
2012-04-30 18:23 ` Alan Reiner
2012-04-30 18:31   ` Amir Taaki
2012-04-30 19:51     ` Alan Reiner
2012-05-02 13:22       ` Mike Hearn
2012-05-02 13:30         ` Gregory Maxwell
2012-05-02 13:32           ` Mike Hearn
2012-05-02 13:31         ` Luke-Jr
2012-05-02 16:21           ` grarpamp
2012-05-02 16:30             ` Luke-Jr
2012-05-02 16:58               ` grarpamp
2012-05-02 18:29                 ` Jeff Garzik
2012-05-02 19:25                   ` Amir Taaki
2012-05-02 19:34                     ` Gary Rowe
2012-05-02 19:40                       ` Raphael NICOLLE
2012-05-02 19:42                         ` Gary Rowe
2012-05-02 19:43                       ` Alan Reiner
2012-05-02 19:43                       ` Amir Taaki
2012-05-02 19:46                         ` Gary Rowe
2012-05-02 19:56                         ` Alan Reiner
2012-05-02 20:25                       ` Luke-Jr
2012-05-02 20:39                         ` Gary Rowe
2012-05-02 19:35                     ` Alan Reiner
2012-05-03  9:06                   ` grarpamp
2012-05-02 13:38         ` Gregory Maxwell
2012-05-02 13:42           ` Mike Hearn
2012-05-02 15:01             ` Alan Reiner
2012-05-02 16:53         ` grarpamp
2012-05-03  7:28         ` Andreas Schildbach
2012-05-03  9:24           ` Jorge Timón
2012-05-03  9:53             ` Andreas Schildbach
2012-05-03 10:25               ` Jorge Timón
2012-05-02 23:04 ` Jeff Garzik [this message]
2012-05-02 20:41 Jim

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=CA+8xBpdsOWdBwEhO2pAAMZiEyvcr-xZL-EnmSsb-vMtowDyu4w@mail.gmail.com \
    --to=jgarzik@exmulti.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=zgenjix@yahoo.com \
    /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