From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TVrOM-00077F-9t for bitcoin-development@lists.sourceforge.net; Tue, 06 Nov 2012 22:13:06 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1TVrOL-0000nE-4k for bitcoin-development@lists.sourceforge.net; Tue, 06 Nov 2012 22:13:06 +0000 Received: from ishibashi.localnet (unknown [173.170.188.216]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 6F5FC27A296B; Tue, 6 Nov 2012 22:12:59 +0000 (UTC) From: "Luke-Jr" To: slush Date: Tue, 6 Nov 2012 22:12:53 +0000 User-Agent: KMail/1.13.7 (Linux/3.5.4-gentoo; KDE/4.8.5; x86_64; ; ) References: <201211061913.35016.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201211062212.54611.luke@dashjr.org> X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1TVrOL-0000nE-4k Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday 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: Tue, 06 Nov 2012 22:13:06 -0000 On Tuesday, November 06, 2012 7:56:23 PM slush wrote: > On Tue, Nov 6, 2012 at 7:13 PM, Luke-Jr wrote: > > But more important to the success of BIP today, I think, is encouraging > > wider community participation. > > It's not about BIP process, it's possibly about content of particular > proposals. > ... > I promised to write BIP draft for Stratum, I proposed and implemented > get_transactions method to allow Stratum jobs inspection. What more do you > want, seriously? I'm soo tired by you, Luke. Perhaps the problem lies in misunderstanding of the BIP process, then, rather than awareness of it. BIP isn't just "write a document"; that's just the first step. The main thing is that it gets peer review, changed to meet the community's needs, and when done should result in a common standard suitable to the needs of the whole community. Whatever the reason, there was a failure of key members of the community to participate in the GBT BIP process and ensure it addressed their needs/wants; identifying and addressing that is something that would improve the BIP process. get_transactions is a step in the right direction, and I don't think anyone expects Stratum to reach the same level as GBT overnight considering it took months for GBT (though I have no doubt now that the GBT discussions have taken place, that some dedicated individual could probably combine the two if they dedicated a few days to it). My comments, however, were not intended to bash stratum or mere complain about the past (it can't be changed), but an attempt to learn from the past and figure out how we can improve things the next time around. Luke