Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of zikula.org
	designates 74.125.82.182 as permitted sender)
	client-ip=74.125.82.182; envelope-from=drak@zikula.org;
	helo=mail-we0-f182.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAAS2fgREw+5NWaFVYd9FS-s63_-24tyWsz5_w6yc8+mGnFYUgQ@mail.gmail.com>
References: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
	<CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>
	<CANAnSg1eH8+sY6n4-cptdzS5Qj0aXdN_d8h8B9joyk73HGL6ZA@mail.gmail.com>
	<CAAS2fgREw+5NWaFVYd9FS-s63_-24tyWsz5_w6yc8+mGnFYUgQ@mail.gmail.com>
From: Drak <drak@zikula.org>
Date: Tue, 19 Nov 2013 17:07:58 +0000
Message-ID: <CANAnSg18FWEQqfqMMY_3XYeLcZ0NJN_1S5QaR0mbp34ZHqM0hg@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d9657fe03fa04eb8ab5f0
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
Precedence: list

--047d7b5d9657fe03fa04eb8ab5f0
Content-Type: text/plain; charset=UTF-8

On 19 November 2013 17:01, Gregory Maxwell <gmaxwell@gmail.com> wrote:

> On Tue, Nov 19, 2013 at 8:53 AM, Drak <drak@zikula.org> wrote:
> > 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,
>
> The IETF makes a clear distinction between individual proposals and
> documents which have been accepted by a working group. The former are
> named after their authors.  Work is not assigned a number until it is
> complete.
>
> I believe it is important to distinguish complete work that people
> should be implementing from things which are incomplete,  and even
> more important to distinguish the work of single parties.
>
> Otherwise you're going to get crap like BIP90: "Increase the supply of
> Bitcoins to 210 million" being confused as an earnest proposal
> supported by many that has traction.
>

I wasnt suggesting people add drafts willy nilly to the repository.
When working on a proposal you can work on it in your own fork and create a
PR. When it's ready to be accepted as a working draft by the WG, then it
can be merged into the draft folder. At which point, PRs are made to that
draft copy until it gets into a ready state to become final. If passed,
it's moved to the accepted/ folder.

This way random BIPS cannot be added to the drafts/ folder in the official
repo. They are only added once they are accepted as a working draft
proposal by Gavin or whatever. Now you get all the niceties of github
workflow for collaboration and tweaking of the draft proposal.

Drak

--047d7b5d9657fe03fa04eb8ab5f0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
9 November 2013 17:01, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tue, Nov 19, 2013 at 8:=
53 AM, Drak &lt;<a href=3D"mailto:drak@zikula.org">drak@zikula.org</a>&gt; =
wrote:<br>


&gt; It&#39;s quite normal for standards bodies to allocate numbers when in=
 draft<br>
&gt; status. If they don&#39;t pass, they don&#39;t pass - they are clearly=
 labelled<br>
&gt; DRAFTs.<br>
&gt;<br>
&gt; +1 on having things in a github repository. Much better for collaborat=
ion,<br>
<br>
</div>The IETF makes a clear distinction between individual proposals and<b=
r>
documents which have been accepted by a working group. The former are<br>
named after their authors. =C2=A0Work is not assigned a number until it is<=
br>
complete.<br>
<br>
I believe it is important to distinguish complete work that people<br>
should be implementing from things which are incomplete, =C2=A0and even<br>
more important to distinguish the work of single parties.<br>
<br>
Otherwise you&#39;re going to get crap like BIP90: &quot;Increase the suppl=
y of<br>
Bitcoins to 210 million&quot; being confused as an earnest proposal<br>
supported by many that has traction.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">I wasnt suggesting =
people add drafts willy nilly to the repository.</div><div class=3D"gmail_e=
xtra">When working on a proposal you can work on it in your own fork and cr=
eate a PR. When it&#39;s ready to be accepted as a working draft by the WG,=
 then it can be merged into the draft folder. At which point, PRs are made =
to that draft copy until it gets into a ready state to become final. If pas=
sed, it&#39;s moved to the accepted/ folder.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">This way ra=
ndom BIPS cannot be added to the drafts/ folder in the official repo. They =
are only added once they are accepted as a working draft proposal by Gavin =
or whatever. Now you get all the niceties of github workflow for collaborat=
ion and tweaking of the draft proposal.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Drak<br></d=
iv><div class=3D"gmail_extra"><br></div></div>

--047d7b5d9657fe03fa04eb8ab5f0--