Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Xg0uy-0000Qh-Ub for bitcoin-development@lists.sourceforge.net; Mon, 20 Oct 2014 00:33:48 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of riseup.net designates 198.252.153.129 as permitted sender) client-ip=198.252.153.129; envelope-from=odinn.cyberguerrilla@riseup.net; helo=mx1.riseup.net; Received: from mx1.riseup.net ([198.252.153.129]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Xg0ux-00082u-Fx for bitcoin-development@lists.sourceforge.net; Mon, 20 Oct 2014 00:33:48 +0000 Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 8E64C40C35 for ; Mon, 20 Oct 2014 00:33:41 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: odinn.cyberguerrilla) with ESMTPSA id 16F6822551 Message-ID: <5444585E.5080600@riseup.net> Date: Mon, 20 Oct 2014 00:33:34 +0000 From: odinn MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <2753630.UjohjSx8jx@1337h4x0r> In-Reply-To: <2753630.UjohjSx8jx@1337h4x0r> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.4 at mx1 X-Virus-Status: Clean X-Spam-Score: -3.0 (---) 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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [198.252.153.129 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -1.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Headers-End: 1Xg0ux-00082u-Fx Subject: Re: [Bitcoin-development] BIP process 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 Oct 2014 00:33:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Earlier in the discussion I suggested Discourse so that the BIP page would be able to look smoother and draw more input. Unsystem forum is run on Discourse and has twitter, github, and e-mail integration. For those who haven't explored it, here is what that looks / feels like: https://forum.unsystem.net/ I'm curious as to why this sort of solution should or should not be considered from someone else's perspective. In the end, whatever works best for all concerned, I'm fine with it, but I'd like to hear more about people's thoughts on Discourse. (I kind of like the feel of it.) xor wrote: > On Wednesday, October 15, 2014 10:29:43 AM Wladimir wrote: >> B) I also think it makes sense to move the BIP discussion (both >> about the BIP process and individual BIPs) to a separate mailing >> list. >> >> bitcoin-development currently has a dual function: discussion of >> Bitcoin Core implementation concerns, as well as global changes >> to Bitcoin (in the form of BIPs). >> >> This makes the list too busy for some people, but it is critical >> that everyone writing a Bitcoin node or client is up-to-date >> with proposals and can comment on them. > > I joined the list when Bitcoin was already in the 10-billions of > market capitalization, and it actually really surprised me how low > the traffic is here given the importance of Bitcoin. > > So as a random stranger to the project, I would vote against that > if I was allowed to. There really should be *more* discussion here, > and splitting the list up won't help with that. > > Greetings > > > > ------------------------------------------------------------------------------ > > > > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. Get alerted through email, SMS, > voice calls or mobile push notifications. Take corrective actions > from your mobile device. http://p.sf.net/sfu/Zoho > > > > _______________________________________________ Bitcoin-development > mailing list Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > - -- http://abis.io ~ "a protocol concept to enable decentralization and expansion of a giving economy, and a new social good" https://keybase.io/odinn -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJURFhXAAoJEGxwq/inSG8Cpc0H+wZauz7iOj4XZJSI3VBv+5WL YAe8kDSOpa5ZprFntsFfKVU+cmSjXckPjCRI9+LsrfTR2L+VjAimjQTct1m6oRAo +5ZQ8Tn2CLEVRJRUzd8zbW8QPMuQCdzvwjs1oq8anaAPdwseEC/QhTZY6Av1MB8y nH+05mMu4YeF3RRIyjXgvxDiBBK3knoaBkbsORkVbIb7MojUBy7FnsS1JFmSs8wv XwWnkmFjVlhC8wSQYohcTWdJablxjpKRFq1ZNgDtIoXEi0dsC+G9Gc+8xub4hA/Y nDk85ihX17TBbB47SOJEAdpGrJjkb8OvdX2ubLnQPYth82wX/MWJTTdv2a4JGik= =uYGH -----END PGP SIGNATURE-----