From: Peter Todd <pete@petertodd•org>
To: Bryan Bishop <kanzure@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority
Date: Thu, 28 Sep 2017 21:52:00 -0400 [thread overview]
Message-ID: <20170929015200.GD11956@savin.petertodd.org> (raw)
In-Reply-To: <CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2017-09-29 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 18:56 Luke Dashjr
2017-09-27 19:01 ` Bryan Bishop
2017-09-27 20:20 ` Sjors Provoost
2017-09-27 21:00 ` Jean-Paul Kogelman
2017-09-28 12:43 ` Christian Decker
2017-09-29 1:52 ` Peter Todd [this message]
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=20170929015200.GD11956@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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