From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
To: Sjors Provoost <sjors@sprovoost.nl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority
Date: Wed, 27 Sep 2017 14:00:35 -0700 [thread overview]
Message-ID: <04038964-659F-4105-B086-8C0AB9FF765C@me.com> (raw)
In-Reply-To: <965940AD-A698-4B5F-9909-105E8A32B398@sprovoost.nl>
[-- 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 --]
next prev parent reply other threads:[~2017-09-27 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 18:56 [bitcoin-dev] Revising BIP 2 to expand editorial authority Luke Dashjr
2017-09-27 19:01 ` Bryan Bishop
2017-09-27 20:20 ` Sjors Provoost
2017-09-27 21:00 ` Jean-Paul Kogelman [this message]
2017-09-28 12:43 ` Christian Decker
2017-09-29 1:52 ` Peter Todd
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=04038964-659F-4105-B086-8C0AB9FF765C@me.com \
--to=jeanpaulkogelman@me.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=sjors@sprovoost.nl \
/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