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] Bitcoin Enhancement Proposals (BEPS)
Date: Mon, 19 Sep 2011 19:06:16 -0700 (PDT)	[thread overview]
Message-ID: <1316484376.96463.YahooMailNeo@web121013.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CABsx9T0y601kjJ7ToczwhcQUoh3NZbuPa+iWwtm6-DZxZSRNPg@mail.gmail.com>

Good idea.


How about BRC?

  Bitcoin Request for Comments?

Otherwise I like the sound of BERs, but it doesn't matter too much the name.



----- Original Message -----
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Cc: 
Sent: Monday, September 19, 2011 6:57 PM
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)

New 'standard' transaction forms would be perfect candidates for BEPS.

I think we aught to have a formal proposal to separate the protocol
version from the client version, too.

--

Does anybody besides me think maybe we should name them something
other than "BEP" ?

I'm worried we'll regret it in two years when a google for "BEP003"
takes you to the BitTorrent EPs instead of the BitCoin EPs.

Maybe "BIP" == Bitcoin Improvement Proposal
or "PEB" == Proposal to Enhance Bitcoin
or "BER" == Bitcoin Enhancement Request

I think I like "BIP"  (PEB sounds like a diet soda, and I don't know
if BER should be pronounced "bear" or "beer").

I generally don't care about names, but it seems like a little
planning now might save some confusion later. And I don't want the
BitTorrent folks to get pissed off at us for 'stealing' their acronym,
either.


-- 
--
Gavin Andresen

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development




  parent reply	other threads:[~2011-09-20  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19  1:04 [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS) Luke-Jr
2011-09-19  3:22 ` Alex Waters
2011-09-19 16:01   ` bgroff
2011-09-19 16:57     ` Gavin Andresen
2011-09-19 17:23       ` Alex Waters
2011-09-20  2:06       ` Amir Taaki [this message]
2011-09-23 19:45       ` Daniel F
2011-09-25  3:27         ` Amir Taaki
  -- strict thread matches above, loose matches on Subject: below --
2011-09-19  0:31 Amir Taaki

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=1316484376.96463.YahooMailNeo@web121013.mail.ne1.yahoo.com \
    --to=zgenjix@yahoo.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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