Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4B5C0C000B for ; Tue, 27 Apr 2021 11:49:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 2A835402DD for ; Tue, 27 Apr 2021 11:49:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.65 X-Spam-Level: X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=q32-com.20150623.gappssmtp.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-nsWIHG1KFC for ; Tue, 27 Apr 2021 11:49:23 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by smtp4.osuosl.org (Postfix) with ESMTPS id 4E5D8402D1 for ; Tue, 27 Apr 2021 11:49:23 +0000 (UTC) Received: by mail-pl1-x630.google.com with SMTP id v20so3449473plo.10 for ; Tue, 27 Apr 2021 04:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=K2ntybzDlEvAXhXxpr0cJ5rdsQwYrg+hqzu0VynvUP4=; b=RMDA51h5jtvzvbDeSiH3SqK/mflP0/yfI5BCsbI7WHhmZcYTKqfKaF48T0ei+xoUYl AA/ZlK9zvE14M3aMVVGNgjcPx/9b38/ZdFAq8rn2o2M8//WYI1/Cr2iCgJMtmfkvEGuo d6gcj04tpoItwqeOZEyzIvv37+aRFKyG5jR0e/21KiLIH0fPTXmA2AoCNqqijEzNNMcu mGPRTMRiy67nM13GO34LLgCT+mwKvZc3aAJlMIOt1l98NUht3xjbz/6IS7Mi7fOSVVpl Cql16HrDAuhl2T0nUmwcDe4C8SFvbkLVm/yxZG3AqhiEnyOLj+ZNgoheBRTvg/0mbTyZ zS1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=K2ntybzDlEvAXhXxpr0cJ5rdsQwYrg+hqzu0VynvUP4=; b=RHJyL7gqLm+H2HsT+cnpEyr9fZNhUQI2n/+GDQV/VC4QYv5Sik8YIUi2Xngu3FapcM tmYeQIUqXheL0dsE0Ju0ZjOGBeTAG5lzTJotoccgZC+PSnUapxK7pzdWFuReT02F8eCa xJDPaRWkC8a9iEgPfM4j92ALp57WtbNs3iFjJu/hH3JzO14EdDfI7qgzgtkTcVV6WVPQ 4araeS3vlSn5ibHhd+OjYZDYBXgzrPEU5OMWmpr995NaC9EAWvBUcEjwe6pS+x63zAKa M1sMkNnTR85A2ZhBEtuywnltuJAfAl8sb1GKlo8e5vy+UMRWmkdy40mdgDw70K1dtB/A 8bjQ== X-Gm-Message-State: AOAM530tM72NFeQmiR8jX9n+FevKJ+vk1Yrplz20DAxNaBiKtYREwqJv 7pGDinNvUbUCp8umA6E8EvqnnQo4dfw3Q2htqTh1XbA= X-Google-Smtp-Source: ABdhPJycMhdXRu7AADMahRQCifh+C8zjULPRGMrV0HY1+NAgfMoUjlCtJWqA0M99QwsRU06ryVVbj2joJ1/+meeptfI= X-Received: by 2002:a17:90a:9405:: with SMTP id r5mr4625766pjo.139.1619524162625; Tue, 27 Apr 2021 04:49:22 -0700 (PDT) MIME-Version: 1.0 References: <202104230209.05373.luke@dashjr.org> <202104252100.07296.luke@dashjr.org> <40214e32-ffb3-9518-7bc8-9c1059f50da7@mattcorallo.com> <202104252122.40909.luke@dashjr.org> <248f871e-1b83-8c7c-678b-3ed0585a6357@mattcorallo.com> <20210426194309.2k5exujz23vjrgwc@ganymede> <773C1Ki5dlSNlxD3HK0eJDKHQ9Ikb5vwuKPZ3dkgEPqUmPGN6DrpLv47LNITHOlu7XWzmIpAmgw24noihYJ5lI5Qhmg7yIlboGQsfAowFCw=@protonmail.com> In-Reply-To: <773C1Ki5dlSNlxD3HK0eJDKHQ9Ikb5vwuKPZ3dkgEPqUmPGN6DrpLv47LNITHOlu7XWzmIpAmgw24noihYJ5lI5Qhmg7yIlboGQsfAowFCw=@protonmail.com> From: Erik Aronesty Date: Tue, 27 Apr 2021 07:49:10 -0400 Message-ID: To: "W. J. van der Laan" , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 27 Apr 2021 12:05:53 +0000 Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2021 11:49:25 -0000 seems like this is solved by a workflow where a maintainer who requests changes clearly tags every entry as "changes needed" or "review requested",, and then the author can resolve/remove the tag after the changes are made. not sure PR's are the right tech here. On Tue, Apr 27, 2021 at 6:28 AM W. J. van der Laan via bitcoin-dev wrote: > > On Monday, April 26th, 2021 at 9:43 PM, David A. Harding via bitcoin-dev = wrote: > > > On Sun, Apr 25, 2021 at 05:31:50PM -0400, Matt Corallo via bitcoin-dev = wrote: > > > > > In general, I think its time we all agree the BIP process has simply = failed > > > > > > and move on. Luckily its not really all that critical and proposed pr= otocol > > > > > > documents can be placed nearly anywhere with the same effect. > > > > I like the idea of decentralizing the BIPs process. It is a historical ar= tifact that the bips repository is part of the same organization that bitco= in core is part of. But there shouldn't be the perception that standardizat= ion is driven by that, or that there is any kind of (non-trivial) gatekeepi= ng. > > I understand where this perception is coming from, though. There being 11= 1 PRs open at https://github.com/bitcoin/bips/pulls indicates that there is= some kind of bottleneck. I hope adding more BIP editors can mitigate this = somewhat. > > Though it also happens that the BIP author simply don't care about change= s anymore and doesn't respond, in which case the PR lingers without any fau= lt from the BIPs maintainer. So something is to be said of having the BIP r= epository mirror/aggregate author's own work trees, and changes needing to = be proposed there instead of "upstream". > > -W > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev