public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99•net>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
	<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Random order for clients page
Date: Mon, 9 Jul 2012 20:30:14 +0200	[thread overview]
Message-ID: <CANEZrP1vwDubXrY3eoq4P4SAN=GK06iVaVx4pMWZKmBwQc9awg@mail.gmail.com> (raw)
In-Reply-To: <1341857882.56956.YahooMailNeo@web121006.mail.ne1.yahoo.com>

It's easy to say, this page is controversial, so let's get rid of it.

However that starts the project down the road of being dominated by
our internal politics rather than what actually makes sense from the
end users perspective. That route spells doom for any product. You can
always tell when a UI or product is the result of internal politics,
whether it be the difficulty of plug-n-play hardware on Linux (no
driver api) to how Microsoft is incapable of producing anything that
isn't built on Windows. Gmail labs is another example of this.

It makes sense that if I go to bitcoin.org, I am educated about the
system and what is available for it. It doesn't make any sense to have
some stuff on the main site and other stuff on a wiki (which may get
randomly vandalized and looks less professional), based on how
"controversial" some developers find it.

FWIW I am dead set against anyone randomly changing the website
without a pull request and such changes should be reverted and
resubmitted through the proper channels. I don't perceive much value
in randomization or trying to make this page "fair". If anything, we
need to pick somebody (one person) who has a strong focus on regular
people and their needs, then just make them the sole committer to the
website. That way disputes can be resolved by them making a decision,
instead of ridiculous edit wars.



  reply	other threads:[~2012-07-09 18:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 15:54 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
2012-07-09 18:18       ` Amir Taaki
2012-07-09 18:30         ` Mike Hearn [this message]
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='CANEZrP1vwDubXrY3eoq4P4SAN=GK06iVaVx4pMWZKmBwQc9awg@mail.gmail.com' \
    --to=mike@plan99$(echo .)net \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=zgenjix@yahoo$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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