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 3E79BB7A for ; Tue, 23 Jul 2019 15:09:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0D4A5224 for ; Tue, 23 Jul 2019 15:09:26 +0000 (UTC) Received: from ip-10-217-1-36.ap-northeast-1.compute.internal (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id 3973314C112 for ; Wed, 24 Jul 2019 00:09:21 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1) by 0 with SMTP; 24 Jul 2019 00:09:16 +0900 X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1]) by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id 1B3894C098 for ; Wed, 24 Jul 2019 00:09:16 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw31.oz.hdemail.jp (ip-10-122-153-121.ap-northeast-1.compute.internal [10.122.153.121]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id 01F3814C112 for ; Wed, 24 Jul 2019 00:09:15 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) X-Received: from mail-qk1-f197.google.com (lb05.oz.hdemail.jp [54.238.57.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw31.oz.hdemail.jp (Postfix) with ESMTP id 92133148C137 for ; Wed, 24 Jul 2019 00:09:15 +0900 (JST) X-Received: by mail-qk1-f197.google.com with SMTP id j81so36532420qke.23 for ; Tue, 23 Jul 2019 08:09:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=M25kpA5lV+mLyZXx6DJJMyDJM24hbVQ4wZoTe/qpA6w=; b=YnUK7RGt2rXuiE6gvnFfuxQsDY+M8V9365IOYlwg2OpN1IumHOE+3dfo5SVOCgTmIO JzCoG7CgmPJW1tp8I9XR0xCAN6QbD9kV77noK8SVKTUTCw5W+SnAFknHrycQF8kwRNc5 kzle3vTdqhYW/JHCkzHrKENA/5KtHHAmjW/9d2qGH3OGKOBmzLSVCZd5g00CB3a6v8hd 57HLnHrPLmehmXJ3lPIpcYIRwlqXYjQPGKk8NrJDWCuij6I++s/pRBoU3Coz0DmPtMjc +qBuzdFP+7VQYTKqrn9VaFyX7Ar+PfZbjAZY2YIYrcVSUStzzaLjR8+vemGuSc2WmSSn nR5A== X-Gm-Message-State: APjAAAXB2/xO/j6DWjP47gGzAmNQj4Kd3hLNBOHw5DupPyAqWO4f8COn BVYusv5Jxr4aJceiDgrWQyiIgeDJAexoqr7ncmepvUga0qILwoJh+4kCqB4r9lROxDFIZo7qI6A cxBhcqu2r9ajtial/c/W7kN7Dt4saG5tkgX6SgNWgtD0u3xmaqQeK0zFePt16iA3Rf8JAfm6xlT lGhFVbYm5ScLxgv8P5VAyXXZZLHaGy6eMo5mB2IcYohSTC43T1jkhjO42Zk4qR7MDKJ2eanizGp +OPafpWTmP067JSnCSxTYLoBtoNmSjVADREWwS/qSe0A8JjySpl7Nn62vmaHb7DXVHukbcGZ3fF ot4zlK0xtUjymZ9LOzsSJcKKAWA= X-Received: by 2002:a0c:d251:: with SMTP id o17mr56176344qvh.109.1563894554179; Tue, 23 Jul 2019 08:09:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrhGIMSagKnke2vc7pefQ/hny7GGvKHy9ZtL8P7eZQZyxE5SXWCnHUIbptVx3vC5oCJbU5zVlGLbm0fJ1CLuc= X-Received: by 2002:a0c:d251:: with SMTP id o17mr56176327qvh.109.1563894553916; Tue, 23 Jul 2019 08:09:13 -0700 (PDT) MIME-Version: 1.0 From: Karl-Johan Alm Date: Wed, 24 Jul 2019 00:09:02 +0900 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham 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, 24 Jul 2019 11:36:44 +0000 Subject: [bitcoin-dev] Absent authors and BIP updates 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: Tue, 23 Jul 2019 15:09:28 -0000 Hello, People come in as Bitcoin developers all the time, but sometimes people also leave permanently. In the case of BIP authors, when a user leaves and does not respond to (reasonable) requests to change their BIPs, we are sort of stuck right now. BIP-2 states that anyone is allowed to request a change of a draft/proposed BIP to "rejected" status after 3 years of inactivity, but sometimes BIPs are accepted, after which the author leaves. See e.g. https://github.com/bitcoin/bips/pull/339 There are a couple of ways to address this: 1. We allow anyone to request a change of a draft/proposed BIP to "accepted", at any time. It is upon the requester to prove within reason that the BIP does fulfill the criteria as given in BIP-2. Such a request does not need the approval of the BIP author. 2. We allow BIPs to expire after 3 years, and allow the BIP repository maintainer to assign a new champion, once/if such a champion appeared. 3. We do neither, and when such is warranted, we make new BIPs with new assignations which supercede the old BIP, sort of like how BIP 2 supercedes BIP 1. Without the author to sign off on the change though, it may not be obvious enough since we can't modify the original BIP. 4. Other approach / fine as it is.