From: "Luke-Jr" <luke@dashjr.org>
To: slush <slush@centrum.cz>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday
Date: Tue, 6 Nov 2012 22:12:53 +0000 [thread overview]
Message-ID: <201211062212.54611.luke@dashjr.org> (raw)
In-Reply-To: <CAJna-Hh3+CChAXeEgjzOvHiamOAUY2da9iQb4AcaxYynp6GJyg@mail.gmail.com>
On Tuesday, November 06, 2012 7:56:23 PM slush wrote:
> On Tue, Nov 6, 2012 at 7:13 PM, Luke-Jr <luke@dashjr.org> 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
next prev parent reply other threads:[~2012-11-06 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 18:47 [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday Gavin Andresen
2012-11-06 19:13 ` Luke-Jr
2012-11-06 19:56 ` slush
2012-11-06 22:12 ` Luke-Jr [this message]
2012-11-07 19:37 ` Pieter Wuille
2012-11-08 9:19 ` Mike Hearn
2012-11-08 12:56 ` Pieter Wuille
2012-11-08 13:07 ` Gregory Maxwell
[not found] ` <CA+s+GJDVLLv8troMfeyWoOwM3EH4GHYtd=bzUgmg_ZegVT6kXw@mail.gmail.com>
2012-11-08 13:10 ` [Bitcoin-development] Fwd: " Wladimir
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=201211062212.54611.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=slush@centrum.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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