From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id BBF46B69 for ; Wed, 27 Sep 2017 22:00:58 +0000 (UTC) X-Greylist: delayed 01:00:00 by SQLgrey-1.7.6 Received: from pv33p36im-asmtp001.me.com (pv33p36im-asmtp001.me.com [17.142.213.62]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3AF163F9 for ; Wed, 27 Sep 2017 22:00:56 +0000 (UTC) Received: from process-dkim-sign-daemon.pv33p36im-asmtp001.me.com by pv33p36im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0OWY00L00I7U1700@pv33p36im-asmtp001.me.com> for bitcoin-dev@lists.linuxfoundation.org; Wed, 27 Sep 2017 21:00:37 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1506546037; bh=N0V7aj+CkgF03OhGw5xFyj7Y2BLnhF7QLsCnJ3HhGU4=; h=From:Content-type:MIME-version:Date:Subject:Message-id:To; b=DSAZqiBQk+yUiyxcfwg2LjfVWhKfIjmJPOSsr0myKxkyh46tOCK6kvrRPR/3nGCxz P4sOKOwKIZhxDhFlC7dy+x6CofIMoD8lmpHwRCu8DMFoUol/dI8BmOxs/2MsUszajv dcDLUFU1905x2I1fJjr2pxN7RAirCEoeSKSFtcE1E++5ZFojGRut/A9cpGxJTWBRcV BoV06RIWbrlmRUUa5sFS04FrNkymlNzzKwgBhGe92ht7/wEKNZtQD+hN4Cz5GN070X S07H34ikjDIIm8+THkL9dHDDGx/oUHvEnmWPOWd2YJG/aA3E3RJoIxkb7vTfKAVOGH 1XmzKRLXcl2Jw== Received: from icloud.com ([127.0.0.1]) by pv33p36im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0OWY00B3DICZM830@pv33p36im-asmtp001.me.com>; Wed, 27 Sep 2017 21:00:36 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-09-27_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709270293 From: Jean-Paul Kogelman Content-type: multipart/alternative; boundary=Apple-Mail-2FDBFBB4-04A8-40CB-9A96-58A6442B3175 Content-transfer-encoding: 7bit MIME-version: 1.0 (1.0) Date: Wed, 27 Sep 2017 14:00:35 -0700 Message-id: <04038964-659F-4105-B086-8C0AB9FF765C@me.com> References: <201709271856.27376.luke@dashjr.org> <965940AD-A698-4B5F-9909-105E8A32B398@sprovoost.nl> In-reply-to: <965940AD-A698-4B5F-9909-105E8A32B398@sprovoost.nl> To: Sjors Provoost , Bitcoin Protocol Discussion X-Mailer: iPhone Mail (15A402) X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 28 Sep 2017 12:51:52 +0000 Subject: Re: [bitcoin-dev] Revising BIP 2 to expand editorial authority X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2017 22:00:58 -0000 --Apple-Mail-2FDBFBB4-04A8-40CB-9A96-58A6442B3175 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Perhaps having authors consent to certain types of changes when they submit t= heir BIP? > On Sep 27, 2017, at 1:20 PM, Sjors Provoost via bitcoin-dev wrote: >=20 >=20 >> Op 27 sep. 2017, om 22:01 heeft Bryan Bishop via bitcoin-dev het volgende geschreven: >>=20 >>> On Wed, Sep 27, 2017 at 1:56 PM, Luke Dashjr via bitcoin-dev wrote: >>> What do people think about modifying BIP 2 to allow editors to merge the= se >>> 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 revisio= n, I >>> think an exception is reasonable. >>=20 >> Even minor revisions can not change the meaning of text. Changing a singl= e word can often have a strange impact on the meaning of the text. There sho= uld 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 men= tion that the primary authors have not reviewed suggested changes, or someth= ing as much; otherwise the reader might not be aware to check revision histo= ry to see what's going on. >=20 > Perhaps it's enough to @mention authors in the PR and give them a week to o= bject before merging? >=20 > Sjors > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev --Apple-Mail-2FDBFBB4-04A8-40CB-9A96-58A6442B3175 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Perhaps having authors consent to certain t= ypes 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> w= rote:


Op 27 s= ep. 2017, om 22:01 heeft Bryan Bishop via bitcoin-dev <bitcoin-dev@lists.linuxfou= ndation.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 th= ink 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. Cha= nging a single word can often have a strange impact on the meaning of the te= xt. There should be some amount of care exercised here. Maybe it would be ok= ay as long as edits are mentioned in the changelog at the bottom of each doc= ument, or mention that the primary authors have not reviewed suggested chang= es, or something as much; otherwise the reader might not be aware to check r= evision history to see what's going on.

Perhaps it's enoug= h to @mention authors in the PR and give them a week to object before mergin= g?

Sjors
________________________= _______________________
bitcoin-dev mailing list
<= span>bitcoin-dev@li= sts.linuxfoundation.org
https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
= --Apple-Mail-2FDBFBB4-04A8-40CB-9A96-58A6442B3175--