Return-Path: <sjors@sprovoost.nl> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C3A5FA92 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Sep 2017 20:20:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D036820D for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Sep 2017 20:20:58 +0000 (UTC) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2194C20C76 for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Sep 2017 16:20:58 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 27 Sep 2017 16:20:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sprovoost.nl; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=CXCyNfCM7WwLr+jjH1Z6h3e0wLNnk5tSMfW/Cm4s1 Qc=; b=Hknm7rumD577T0XYWxM9plXwBTYfqyRkUVNb5HS9l8jIywzuOAaXV/bEo C6PDP/YcMlfPAd9Cx1pZ6a4ElxiNQKwYueJ8JECefy2QDyCJW1/0iFcaJ3cLFAEv rbRkPOxO5FgE2m/SWmW2SGTqVM7jXQL4f+jAOy+6gAtbbd0MhwCxQVifNO29/Waw 8VETmKb3+oMlr5yyaX+V6CLbWXqbjDTiYvll/nHUrU0JRPC8TQfx3ZCP0+aB1GkA teficw4pFpCYeM9efI3uIyL46ft3QxiAvUcMaYhyNCAjlbpWorBuXt264/j3gEVs Z3uqHO6mSKNzFaLw/49RkoFyW4nBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=CXCyNfCM7WwLr+jjH1 Z6h3e0wLNnk5tSMfW/Cm4s1Qc=; b=ei65U9gqD7Toq7Yn/2+9uvX+OrWgaa4TFj XryYsitOzLJQ4Hy0iBVguO54EMFUl43szG9g4GZ8FdZ7xredk+MMMnJI4MPZLGlE x1y71qxvCRtjGjGkK26Gvnj5zUIXkornQrJ/ui7Z/mN0lCC9t3aOA05fxePqbb+D mgZZBUZhPJmrTFOBk9PxyXx+JlLMQJXD9eby7MCuNemWQM9ArG+PgPi9YwWMDXw9 hniczJGvjMQ4ITvvSCMhuYbDWu3kuBJtRz15rGZWRwX5LHGsjzH3F2LiIMbIPeu0 9oAxFVaYYcgQtMZKrZ3WuW8Y0kx4NkdkYmD3CZ//jnWWH0dEm3KQ== X-ME-Sender: <xms:KgjMWQ1q3BFy-31_x85MNy6kKYkzr07eTWSPf7dtazAAKkCgferssQ> X-Sasl-enc: JCLQ/lJwNRxLQC6TS1f13UpYewssTpe7P+jkuhXesLXr 1506543657 Received: from [192.168.0.108] (unknown [78.96.81.19]) by mail.messagingengine.com (Postfix) with ESMTPA id 512D67F3CA for <bitcoin-dev@lists.linuxfoundation.org>; Wed, 27 Sep 2017 16:20:57 -0400 (EDT) From: Sjors Provoost <sjors@sprovoost.nl> Content-Type: multipart/signed; boundary="Apple-Mail=_B6E4FBDB-F52A-4F3C-A20B-02ACA22F4432"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.6\)) Date: Wed, 27 Sep 2017 23:20:54 +0300 References: <201709271856.27376.luke@dashjr.org> <CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com> To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> In-Reply-To: <CABaSBaz=pMfTz2UF-WpyxrkGY9XZO+zTHR7-Oie79J1Ap10hpQ@mail.gmail.com> Message-Id: <965940AD-A698-4B5F-9909-105E8A32B398@sprovoost.nl> X-Mailer: Apple Mail (2.3445.1.6) X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE, RCVD_IN_DNSWL_LOW 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: Wed, 27 Sep 2017 20:22:16 +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 <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Wed, 27 Sep 2017 20:20:59 -0000 --Apple-Mail=_B6E4FBDB-F52A-4F3C-A20B-02ACA22F4432 Content-Type: multipart/alternative; boundary="Apple-Mail=_2E2C93E2-F229-4CEF-82FC-B129836B592C" --Apple-Mail=_2E2C93E2-F229-4CEF-82FC-B129836B592C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Op 27 sep. 2017, om 22:01 heeft Bryan Bishop via bitcoin-dev = <bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven: >=20 > 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. >=20 > 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 --Apple-Mail=_2E2C93E2-F229-4CEF-82FC-B129836B592C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br = class=3D""><div>Op 27 sep. 2017, om 22:01 heeft Bryan Bishop via = bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" = class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>> het volgende = geschreven:<br class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" = class=3D""><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Wed, = Sep 27, 2017 at 1:56 PM, Luke Dashjr via bitcoin-dev <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" = target=3D"_blank" = class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>></span> = wrote:<br class=3D""><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 class=3D"">= kinds of changes without involving the Authors? Strictly speaking, BIP = 2<br class=3D""> shouldn't be changed now that it is Active, but for such a minor = revision, I<br class=3D""> think an exception is reasonable.<br class=3D""></blockquote><div = class=3D""><br class=3D"">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.<br = class=3D""></div></div></div></div></div></blockquote></div><br = class=3D""><div class=3D"">Perhaps it's enough to @mention authors in = the PR and give them a week to object before merging?</div><div = class=3D""><br class=3D""></div><div class=3D"">Sjors</div></body></html>= --Apple-Mail=_2E2C93E2-F229-4CEF-82FC-B129836B592C-- --Apple-Mail=_B6E4FBDB-F52A-4F3C-A20B-02ACA22F4432 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE7ZvfetalXiMuhFJCV/+b28wwEAkFAlnMCCYACgkQV/+b28ww EAlvhxAAjhtsNfUKWF4YnBCbJwSNhbPrCrg/M/sBx5Z8xtd8ATbyvgvLBifAWttI ep+wchIFNHy2iQwx3xAuep74W5VW160+BG1q/6KT7VFBFZERGYZYmuiNeIM2/oTL dqi17x/1wRMgV5Dj/KN0PQgMrEtBiCwBIIc01DtF/Rd81CVIb6h4/9kxqpenz74B xCwz4TX5/E3DxiriDcsMl8y5GKzVUmU2VuR7qVdkLnFSGHiqEHQFTbRpMYgro74n A0ok/hnkLVyb87XUkIvYks6U+BkoD6vMIGggnBsrlLpFpP/SN9hfsarZJnIbaPTN 7cFTXmW0VxOFTKYGmHPYzuEJZdYG9xJ9qNyq+q6tkrgi6+NdXQyQeJkHTKlEOzVP +Ye3R1FMK0wJMSdYOO0bqFzmjn6jXm7CMt7puleF8EJiQTbiZdAY5xI+kEznyetu Xv3/Qrfq5E0WD2jHH9zNWoPrsjBrcnDlYDcQPZ5sgwI2iASxDcE0WDKxYUsdlWZT cBYyo4Jdy1dQRjelAosqLDY27iODj2kZ4gKtDwdUXgXazY/Gz0f/T52WNf9IG/9l XtJ5uU6JVUcjkrMDj4N/h+lps2G6gToKZ+Zfn5mBIhyMP9EqPodapUT0eUXzCtZN IANrWWeQ+VLwW0XQb9PyfYsQwmnc39w+ZQZ2PN9tTfyJKnO2kv8= =I277 -----END PGP SIGNATURE----- --Apple-Mail=_B6E4FBDB-F52A-4F3C-A20B-02ACA22F4432--