Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SoIiz-0001Bu-S2 for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 18:30:21 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.41 as permitted sender) client-ip=74.125.82.41; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f41.google.com; Received: from mail-wg0-f41.google.com ([74.125.82.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SoIiy-0001O6-VZ for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 18:30:21 +0000 Received: by wgbds1 with SMTP id ds1so2726146wgb.4 for ; Mon, 09 Jul 2012 11:30:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.81.165 with SMTP id b5mr31483909wiy.17.1341858614728; Mon, 09 Jul 2012 11:30:14 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.19.13 with HTTP; Mon, 9 Jul 2012 11:30:14 -0700 (PDT) In-Reply-To: <1341857882.56956.YahooMailNeo@web121006.mail.ne1.yahoo.com> References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com> <1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com> <1341857882.56956.YahooMailNeo@web121006.mail.ne1.yahoo.com> Date: Mon, 9 Jul 2012 20:30:14 +0200 X-Google-Sender-Auth: xX1J2p9MNaVDZyQyiNE_I1MFpzw Message-ID: From: Mike Hearn To: Amir Taaki Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1SoIiy-0001O6-VZ Cc: "bitcoin-development@lists.sourceforge.net" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 18:30:21 -0000 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.