[bitcoin-dev] Revising BIP 2 to expand editorial authority

[bitcoin-dev] Revising BIP 2 to expand editorial authority

[Luke Dashjr]

Many pull requests to the BIPs repository are spelling corrections or similar, 
which are obvious to merge. Currently, the BIP process requires the Author of 
the affected BIPs to ACK any changes, which seems inefficient and unnecessary 
for these kind of editorial fixes.

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.

I've prepared a draft PR for BIP 2 here:
    https://github.com/bitcoin/bips/pull/596

If you oppose this change, please say so within the next month.

Luke

Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority

[Bryan Bishop]

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

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

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

Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority

[Sjors Provoost]

[-- Attachment #1.1: Type: text/plain, Size: 1158 bytes --]


Op 27 sep. 2017, om 22:01 heeft Bryan Bishop via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
> 
> On Wed, Sep 27, 2017 at 1:56 PM, Luke Dashjr via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org <mailto: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.

Perhaps it's enough to @mention authors in the PR and give them a week to object before merging?

Sjors

[-- Attachment #1.2: Type: text/html, Size: 2020 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority

[Jean-Paul Kogelman]

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

Perhaps having authors consent to certain types of changes when they submit their BIP?


> On Sep 27, 2017, at 1:20 PM, Sjors Provoost via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
> 
>> Op 27 sep. 2017, om 22:01 heeft Bryan Bishop via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
>> 
>>> 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.
> 
> Perhaps it's enough to @mention authors in the PR and give them a week to object before merging?
> 
> Sjors
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

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

Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority

[Christian Decker]

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

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
>

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

Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority

[Peter Todd]

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

On Wed, Sep 27, 2017 at 02:01:40PM -0500, Bryan Bishop via bitcoin-dev 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.

As part of this, we may want to say that the BIP editor should
cryptographically sign (and ideally timestamp) all their changes as a secondary
measure to make it clear who actually made the change.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]