public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Drak <drak@zikula.org>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
Date: Tue, 19 Nov 2013 16:53:38 +0000	[thread overview]
Message-ID: <CANAnSg1eH8+sY6n4-cptdzS5Qj0aXdN_d8h8B9joyk73HGL6ZA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>

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

On 19 November 2013 16:32, Wladimir <laanwj@gmail.com> wrote:

>
> On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>
>> BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and
>> are not automatically assigned a BIPS number.
>>
>
> Are we going to move ahead with this?
>
> If so, I'm volunteering to create the repository and import the current
> BIPs from the wiki there (and convert from wiki markup to markdown where
> necessary).
>
> 2) Time passes.  Software for BIP drafts is developed, tested,
>> published, and publicly discussed in a typical open source manner.
>>
>
> Personally I think it is useful to have a number as soon as a BIP can be
> implemented, even if still in draft status; it gives something to refer to
> when mentioning a certain improvement proposal (in commit messages and such
> it could be called BIP xxx Draft).
> I don't think we are at risk of running out of numbers to assign any time
> soon.
>

It's quite normal for standards bodies to allocate numbers when in draft
status. If they don't pass, they don't pass - they are clearly labelled
DRAFTs.

+1 on having things in a github repository. Much better for collaboration,

Drak

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

  reply	other threads:[~2013-11-19 16:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 14:30 [Bitcoin-development] Revisiting the BIPS process, a proposal Jeff Garzik
2013-10-21 14:34 ` Jeff Garzik
2013-10-21 15:46   ` Andreas Schildbach
2013-10-21 16:14     ` Jeff Garzik
2013-10-21 17:17 ` Jeff Garzik
2013-10-21 19:38   ` Jean-Paul Kogelman
2013-10-21 19:47     ` Luke-Jr
2013-10-21 20:57       ` Benjamin Cordes
2013-10-21 20:59       ` Benjamin Cordes
2013-10-22  6:39       ` Martin Sustrik
2013-10-22  6:59         ` Jean-Paul Kogelman
2013-10-22  7:03           ` Gregory Maxwell
2013-10-22  7:34             ` Martin Sustrik
2013-10-22  7:49               ` Peter Todd
2013-10-22  7:56               ` Gregory Maxwell
2013-10-22  8:20                 ` Martin Sustrik
2013-10-22 14:08               ` Jeff Garzik
2013-10-23  7:38                 ` Martin Sustrik
2013-10-23 19:40                   ` Peter Todd
2013-10-23 20:05                     ` Martin Sustrik
2013-10-23 20:27                       ` Peter Todd
2013-10-23 21:07                         ` Pieter Wuille
2013-10-23 21:42                           ` Allen Piscitello
2013-10-23 21:49                             ` Luke-Jr
2013-10-24  7:03                           ` Martin Sustrik
2013-10-24 10:39                             ` Jeff Garzik
2013-10-24 11:11                             ` Christian Decker
2013-10-24 19:43                               ` Jeremy Spilman
2013-11-19 16:32 ` Wladimir
2013-11-19 16:53   ` Drak [this message]
2013-11-19 17:01     ` Gregory Maxwell
2013-11-19 17:07       ` Drak
2013-11-19 17:45       ` Wladimir
2013-11-19 17:54         ` Gregory Maxwell
2013-11-19 17:06   ` Peter Todd
     [not found]     ` <CA+s+GJA=p+yvoJqUAMQQRcfYK1B8eMVSJDWaXW8o+X5dzCXkdA@mail.gmail.com>
2013-11-19 17:21       ` [Bitcoin-development] Fwd: " Wladimir

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=CANAnSg1eH8+sY6n4-cptdzS5Qj0aXdN_d8h8B9joyk73HGL6ZA@mail.gmail.com \
    --to=drak@zikula.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=laanwj@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