public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
	<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] 0.4.x stable branch
Date: Mon, 19 Sep 2011 06:48:47 -0700 (PDT)	[thread overview]
Message-ID: <1316440127.85874.YahooMailNeo@web121018.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CABsx9T2FBNv26E4LHmi9GVfi1HLR1wR__qGp1_gjco8rwN0L4Q@mail.gmail.com>

>Eventually, when there are a bunch of bitcoin implementations to

>choose from, I think bitcoin.org should look like bittorrent.org -- it
>should become a forum for developers to exchange ideas about the
>direction of bitcoin.
>
>Gavin Andresen

Thanks for your support. This is a noble ideal and will ensure bitcoin's eventual success by serving as a neutral platform for discussions.

One step I've taken in this direction is to setup a process for proposing changes to the bitcoin protocol. See my other email to this list and this url:

  https://en.bitcoin.it/wiki/Bitcoin_Enhancement_Proposals

The first proposal BEP 0001 is copied from Python's PEP 0001 and is a good starting point. I've marked it as a draft since it's only a non-working proposal. After that with mutual consent and discussion, we can move it to active status and start to think about setting up an arbitration committee.

We should in general favour long discussion over voting. The Wikipedia model for resolving issues through hammering out details is superior to debian with a cycling board of voting members.

The bittorrent page looks like a good future ideal to model ourselves off of and the EP pages too:

  http://bittorrent.org/beps/bep_0000.html

BEP 0001 needs review and comments. As you can see, bittorrent did the exact same thing here (copying the PEP process) with success:

  http://bittorrent.org/beps/bep_0001.html

genjix / Amir Taaki




  parent reply	other threads:[~2011-09-19 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 23:30 Luke-Jr
2011-09-19 12:49 ` Gavin Andresen
2011-09-19 13:03   ` Gregory Maxwell
2011-09-19 13:48   ` Amir Taaki [this message]
2011-09-19 15:00   ` Luke-Jr
2011-09-19 15:06     ` Gregory Maxwell
2011-09-20  4:41     ` theymos
2011-09-20 19:10 ` Jeff Garzik
2011-09-20 20:37   ` Luke-Jr
2011-09-21 14:24     ` Alex Waters

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=1316440127.85874.YahooMailNeo@web121018.mail.ne1.yahoo.com \
    --to=zgenjix@yahoo$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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