Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RzGsc-0002Wu-4T for bitcoin-development@lists.sourceforge.net; Mon, 20 Feb 2012 00:13:22 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RzGsZ-0000gm-Qk for bitcoin-development@lists.sourceforge.net; Mon, 20 Feb 2012 00:13:22 +0000 Received: by werc1 with SMTP id c1so4124183wer.34 for ; Sun, 19 Feb 2012 16:13:13 -0800 (PST) Received-SPF: pass (google.com: domain of grarpamp@gmail.com designates 10.180.24.7 as permitted sender) client-ip=10.180.24.7; Authentication-Results: mr.google.com; spf=pass (google.com: domain of grarpamp@gmail.com designates 10.180.24.7 as permitted sender) smtp.mail=grarpamp@gmail.com; dkim=pass header.i=grarpamp@gmail.com Received: from mr.google.com ([10.180.24.7]) by 10.180.24.7 with SMTP id q7mr12697313wif.14.1329696793741 (num_hops = 1); Sun, 19 Feb 2012 16:13:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.24.7 with SMTP id q7mr10631638wif.14.1329696793698; Sun, 19 Feb 2012 16:13:13 -0800 (PST) Received: by 10.180.103.132 with HTTP; Sun, 19 Feb 2012 16:13:13 -0800 (PST) In-Reply-To: <4F417E76.30001@gmail.com> References: <15A9E3BE-3288-4CDC-8243-05669298CDB0@ceptacle.com> <4F417E76.30001@gmail.com> Date: Sun, 19 Feb 2012 19:13:13 -0500 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.2 (-) 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 (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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 0.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RzGsZ-0000gm-Qk Subject: Re: [Bitcoin-development] off-topic: bitcoin-forum... 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, 20 Feb 2012 00:13:22 -0000 > Some time ago i started a googlegroup mailing list, bitcoin-discussion. > It's been pretty low-volume... but it's something. :) > http://groups.google.com/group/bitcoin-discussion Unfortunately it appears to be just as dead as the one on sourceforge. > or we could try to revive the bitcoin-list ml on sf. Well there's a couple things I see... 1) Yes, IMO, a real mailing list for users needs to exist. Among the prior reasons... lists tend to house a more technical crowd than forums which are magnets for initiates. 2) There was originally one client. Now there are many, all adherant to the same bitcoin spec. So while: bitcoin-development@lists.sourceforge.net represents the dev community for the original client, it may not, or won't be, for any other client. And as: bitcoin-list@lists.sourceforge.net was for, and is administratively tied to, the original client... it may not be the place, or a welcome one, to hold talk of all the adherant clients. 3) The sourceforge list browsing interface is ridiculously lame and overweight, and it doesn't appear to be setting a '^Reply-to: ' header which is bad. Googlegroups would be an ok site I suppose. And a pure MailMan interface would be even better and more customarily accepted. So for the user list, I'd suggest: 1) Search a bit to make sure there's not already a busy list out there somewhere. Check the list aggregator sites like markmail, gmane, etc too. 2) Charter it as bitcoin protocol, client agnostic. 3) Find an impartial administrative and robust home for the list with browsable, searchable and hopefully downloadable archives. 4) Make the announcement to other known client lists/forums. 5) Close any relevant old lists. 6) Promote via similar announcement from time to time. http://groups.google.com/group/bitcoin-discussion/about Description: A place for discussion related to bitcoin. Is this sufficient charter to go with? Is the creator/maintainer known impartial? What happens to ongoing list operations when said people vanish? It is presumed googlegroups itself is robust.