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: [Bitcoin-development] All pre-BIP BIPs are not valid
Date: Sun, 29 Jan 2012 14:40:14 -0800 (PST)	[thread overview]
Message-ID: <1327876814.85926.YahooMailNeo@web121001.mail.ne1.yahoo.com> (raw)

Hi all,

Luke Dashjr is telling me that BIP 20 was accepted as Final a year ago (before the BIP process existed).

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


I respectfully disagree. I find it nonsensical to have a BIP to have been accepted before the BIP process existed. My feeling is that a BIP needs to go through the proper formalised motions in public before becoming accepted.

The URI Scheme did not go through these motions. I did not know it was even accepted, and at least 2 implementations have objected to the standard as is. This is problematic because a standard is meant to be consensus building not enforcement from above.

Ergo I am going to say:

NO BIP EXISTED BEFORE THE BIP PROCESS.

NEW BIPS ARE ALWAYS DRAFT STATUS.

BIPS CHANGE STATUS AS SPECIFIED IN BIP 0001

Luke claims I do not have the ability to specify those conditions above.

If there are any objections then please tell me. I did not get to observe the process for BIP 20, therefore I am not accepting it. Anybody is welcome to submit a competing BIP to Luke's BIP 20 (as has happened with BIP 16 and 17).




             reply	other threads:[~2012-01-29 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 22:40 Amir Taaki [this message]
2012-01-29 22:50 ` [Bitcoin-development] All pre-BIP BIPs are not valid Luke-Jr
2012-01-29 23:02 ` Matt Corallo
2012-01-29 23:10   ` Luke-Jr

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=1327876814.85926.YahooMailNeo@web121001.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