From: Jean-Paul Kogelman <jeanpaulkogelman@me•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Sat, 19 Oct 2013 17:52:49 -0700 [thread overview]
Message-ID: <9EF588BB-14B5-495A-8253-82574DCB1A8A@me.com> (raw)
In-Reply-To: <20131019235746.GA29032@savin>
[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]
>> Having it on the BIP page doesn't make it any more official, I agree, but it does increase its exposure and will hopefully spark some more discussion.
>
> Having it on the BIP page *does* make it more official, at least the way
> we've been using the BIP page, which is to filter out the proposals that
> haven't gotten much support at all. (or maybe are just controversial)
Interesting. The main reason I wrote my proposal was because the only proposal that came close to covering the same area was BIP 39, which at that time had 2 paragraphs of text (although admittedly did link to a text file off site where the draft was being developed). And currently there are 2 proposals that have numbers allocated but are empty (BIP 40 and 41) with no references to the development or discussion.
I appreciate the fact that acceptance of proposals on the BIP page are more strict, but it may be desirable to have the enforcement be more uniform. Also, BIP 38 is gaining more acceptance out in the community (many sites support the import of these keys and a growing number of paper wallet sites / coin / card vendors are offering it as an option), yet it's still missing from the BIP list, which seems to me a bit counter to the arguments given about community acceptance.
> FWIW I myself haven't pushed hard for getting an "official" BIP number
> for my draft NODE_BLOOM BIP, even though I've got support from most of
> the dev team on the pull-request:
> https://github.com/bitcoin/bitcoin/pull/2900 I'm probably at the point
> where I could get one assigned - Litecoin for instance has made that
> change - but really I just see that as a formality; that it's still a
> controversial idea is much more relevant.
> In any case I don't see any working code in your email, I'd suggest
> writing some. You're BIP would be much more likely to be accepted if you
> were more involved in wallet development.
Good point. I'm developing my own client (which has the code up and running, with unit tests), but I'm not ready to release it just yet until I've got all the client's alpha features working. Would putting contact information there so people can ask for the relevant code be sufficient until I have my client up on github?
jp
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2013-10-20 0:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 16:38 Mitar
2013-10-19 16:50 ` Melvin Carvalho
2013-10-19 20:40 ` Gregory Maxwell
2013-10-19 21:09 ` Mitar
2013-10-19 21:16 ` Jean-Paul Kogelman
2013-10-19 22:29 ` Luke-Jr
2013-10-19 23:20 ` Gregory Maxwell
2013-10-19 23:35 ` Jean-Paul Kogelman
2013-10-19 23:57 ` Peter Todd
2013-10-20 0:52 ` Jean-Paul Kogelman [this message]
2013-10-20 22:43 ` Peter Todd
2013-10-20 23:11 ` Peter Todd
2013-10-21 0:27 ` Jeff Garzik
2013-10-21 6:25 ` Peter Todd
2013-10-21 6:40 ` Jean-Paul Kogelman
2013-10-21 6:43 ` Peter Todd
2013-10-21 6:52 ` Jean-Paul Kogelman
2013-10-21 7:03 ` Martin Sustrik
2013-10-21 7:07 ` Jean-Paul Kogelman
2013-10-21 7:28 ` Martin Sustrik
2013-10-21 9:36 ` Melvin Carvalho
2013-10-21 9:44 ` Arto Bendiken
2013-10-21 9:49 ` Jean-Paul Kogelman
2013-10-21 10:21 ` Jorge Timón
2013-10-20 10:00 ` Wladimir
2013-10-19 23:21 ` Jean-Paul Kogelman
2013-10-19 23:22 ` Jean-Paul Kogelman
2013-10-19 22:33 ` Mike Hearn
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=9EF588BB-14B5-495A-8253-82574DCB1A8A@me.com \
--to=jeanpaulkogelman@me$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(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