MIME-Version: 1.0
References: <201709271856.27376.luke@dashjr.org>
	<CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com>
In-Reply-To: <CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Thu, 28 Sep 2017 12:43:19 +0000
Message-ID: <CALxbBHUPoOgEuXGryYVvuVnM+Rnv_97kCpxPW-BcGyXFLedcLA@mail.gmail.com>
To: Bryan Bishop <kanzure@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary="94eb2c05714268ca11055a3f417a"
Subject: Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority
Precedence: list

--94eb2c05714268ca11055a3f417a
Content-Type: text/plain; charset="UTF-8"

Agreed, I think a sign-off mechanism might be desirable. Currently it must
be the original author(s) signing off, but we can probably widen that to be
any 2-3 community members. They'd basically be attesting that the meaning
did not change.

- cdecker

On Wed, Sep 27, 2017 at 9:02 PM Bryan Bishop via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Wed, Sep 27, 2017 at 1:56 PM, Luke Dashjr via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> What do people think about modifying BIP 2 to allow editors to merge these
>> kinds of changes without involving the Authors? Strictly speaking, BIP 2
>> shouldn't be changed now that it is Active, but for such a minor
>> revision, I
>> think an exception is reasonable.
>>
>
> Even minor revisions can not change the meaning of text. Changing a single
> word can often have a strange impact on the meaning of the text. There
> should be some amount of care exercised here. Maybe it would be okay as
> long as edits are mentioned in the changelog at the bottom of each
> document, or mention that the primary authors have not reviewed suggested
> changes, or something as much; otherwise the reader might not be aware to
> check revision history to see what's going on.
>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--94eb2c05714268ca11055a3f417a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Agreed, I think a sign-off mechanism might be desirable. C=
urrently it must be the original author(s) signing off, but we can probably=
 widen that to be any 2-3 community members. They&#39;d basically be attest=
ing that the meaning did not change.<div><br></div><div>- cdecker<br><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Sep 27, 2017 at 9:02 PM B=
ryan Bishop via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"=
><div class=3D"gmail_quote">On Wed, Sep 27, 2017 at 1:56 PM, Luke Dashjr vi=
a bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.lin=
uxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What do people think=
 about modifying BIP 2 to allow editors to merge these<br>
kinds of changes without involving the Authors? Strictly speaking, BIP 2<br=
>
shouldn&#39;t be changed now that it is Active, but for such a minor revisi=
on, I<br>
think an exception is reasonable.<br></blockquote></div></div></div><div di=
r=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br>Ev=
en minor revisions can not change the meaning of text. Changing a single wo=
rd can often have a strange impact on the meaning of the text. There should=
 be some amount of care exercised here. Maybe it would be okay as long as e=
dits are mentioned in the changelog at the bottom of each document, or ment=
ion that the primary authors have not reviewed suggested changes, or someth=
ing as much; otherwise the reader might not be aware to check revision hist=
ory to see what&#39;s going on.<br><br></div></div><div class=3D"m_14424098=
55892789661gmail_signature" data-smartmail=3D"gmail_signature">- Bryan<br><=
a href=3D"http://heybryan.org/" target=3D"_blank">http://heybryan.org/</a><=
br>1 512 203 0507</div>
</div></div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div></div>

--94eb2c05714268ca11055a3f417a--