From: Wladimir <laanwj@gmail•com>
To: xor@freenetproject•org
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP process
Date: Sun, 19 Oct 2014 11:49:48 +0200 [thread overview]
Message-ID: <CA+s+GJB+RfqYNH+c99uLgFtJPEigW378A62bqYfZm2A_3o9c3A@mail.gmail.com> (raw)
In-Reply-To: <2753630.UjohjSx8jx@1337h4x0r>
On Sun, Oct 19, 2014 at 9:17 AM, xor <xor@freenetproject•org> wrote:
> 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.
The problem is not one of traffic, but of confusion of concerns, and of focus.
That specific questions about Bitcoin Core are being asked, for
example about watch-only functionality, in the same list where changes
to the entire system (BIPs) should be decided on doesn't make sense.
This has in practice caused some developers of alternative clients to
not subscribe to this list, even though they *should* follow BIP
discussion otherwise it makes no sense to have a process in the first
place.
Wladimir
next prev parent reply other threads:[~2014-10-19 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:29 Wladimir
2014-10-15 9:22 ` Gregory Maxwell
2014-10-15 9:36 ` Wladimir
2014-10-15 18:58 ` Cory Fields
2014-10-16 7:50 ` Thomas Zander
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46 ` Mike Hearn
2014-10-15 15:54 ` Adam Back
2014-10-15 16:47 ` Peter Todd
2014-10-15 18:13 ` Mike Hearn
2014-10-16 7:38 ` Thomas Zander
2014-10-16 14:19 ` Oliver Egginger
2014-10-15 19:00 ` Btc Drak
2014-10-15 19:40 ` Peter Todd
2014-10-16 4:41 ` Luke Dashjr
2014-10-19 7:17 ` xor
2014-10-19 9:42 ` Btc Drak
2014-10-19 9:49 ` Wladimir [this message]
2014-10-19 18:58 ` Thomas Zander
2014-10-20 0:33 ` odinn
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 19:17 Gavin Andresen
2011-10-18 21:26 ` Nils Schneider
2011-10-20 5:02 ` Alex Waters
2011-10-20 11:27 ` Christian Decker
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=CA+s+GJB+RfqYNH+c99uLgFtJPEigW378A62bqYfZm2A_3o9c3A@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=xor@freenetproject$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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