public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Martin Sustrik <sustrik@250bpm.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:36:04 +0200	[thread overview]
Message-ID: <CAKaEYhKZtN-wT3puES=iF+6L83z0haHS+P2tYHWZ14T4=Gf+aw@mail.gmail.com> (raw)
In-Reply-To: <5264D1DB.5060107@250bpm.com>

[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]

On 21 October 2013 09:03, Martin Sustrik <sustrik@250bpm.com> wrote:

> On 21/10/13 08:52, Jean-Paul Kogelman wrote:
> > How about putting them into sub directories that map onto the status of
> the BIP?
> >
> > Reading BIP 1, that would make:
> >
> > Accepted
> > Active
> > Draft
> > Deferred
> > Final
> > Rejected
> > Replaced
> > Withdrawn
>
> Have it been considered to do this via IETF? The process there is
> hardened by 40 years of experience and 7000+ RFCs. Probably better than
> anything you can devise yourself.
>

IETF is great for some things.  I think the bitcoin URI scheme is being
registered with them.

However the process can take many years to get to an RFC, for something
relatively simple, not to mention there can be costs too

Given that crypto currencies are a relatively new field, I am unsure the
IETF has a wealth of expertise in this area, compared with the core devs

Maybe IETF is better to standardize some of the communications or
serialization components, but not so much the BIPs.  Or perhaps some of the
BIPs can be written up as "Informational" rather than "Proposed Standard"
in the RFC format, and reviewed

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.


>
> Martin
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 3244 bytes --]

  parent reply	other threads:[~2013-10-21  9:36 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 [this message]
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='CAKaEYhKZtN-wT3puES=iF+6L83z0haHS+P2tYHWZ14T4=Gf+aw@mail.gmail.com' \
    --to=melvincarvalho@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=sustrik@250bpm.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