public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Arto Bendiken <arto@bendiken.net>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Mon, 21 Oct 2013 11:44:08 +0200	[thread overview]
Message-ID: <CAE7aNuT20J6L40_u3vERtMJa01eBA-=9PYqFuakoLH_w5DTsgA@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhKZtN-wT3puES=iF+6L83z0haHS+P2tYHWZ14T4=Gf+aw@mail.gmail.com>

On Mon, Oct 21, 2013 at 11:36 AM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
>
> I've followed quite a few FLOSS projects over the years.  Overall, I've been
> amazingly impressed with the BIP process (dont forget it's used in other
> systems too -- python?).  It seems an agile process, that strikes an great
> balance between needed features, and documentation.  I think that's exactly
> what will continue bitcoin's momentum in the short to medium term.

Indeed. The BIP analogs that immediately come to mind would be the
enhancement proposal processes for Python, XMPP, and BitTorrent:

http://www.python.org/dev/peps/
http://xmpp.org/xmpp-protocols/xmpp-extensions/
http://www.bittorrent.org/beps/bep_0000.html

-- 
Arto Bendiken | @bendiken | http://ar.to



  reply	other threads:[~2013-10-21  9:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 16:38 [Bitcoin-development] A critique of bitcoin open source community 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
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 [this message]
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='CAE7aNuT20J6L40_u3vERtMJa01eBA-=9PYqFuakoLH_w5DTsgA@mail.gmail.com' \
    --to=arto@bendiken.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=melvincarvalho@gmail.com \
    /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