From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id DFC61C000D for ; Tue, 7 Sep 2021 11:45:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id C233C40420 for ; Tue, 7 Sep 2021 11:45:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ZKubu7c9auhH for ; Tue, 7 Sep 2021 11:45:54 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by smtp4.osuosl.org (Postfix) with ESMTPS id EE34B403CC for ; Tue, 7 Sep 2021 11:45:53 +0000 (UTC) Received: by mail-yb1-xb2a.google.com with SMTP id e131so19156757ybb.7 for ; Tue, 07 Sep 2021 04:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=TOIdPOAGPt8+fQFuWE+78BCiESNSOo55jhWTB+QgCQo=; b=bvcH+wKZ+a4MDtVBzL4ECXKrUXvamXHZlAXSqVEdNEYi6upHLAZBLasUTmNaMBzPSc 0DaOFwWvaK9+/tXoliaiyiDgH2viLnlk/0SUJRFucFfTYnMzB519Znc9ancKwd3m40An iCJFHIK3y05HyH5TL/PtT3P8+aBpgpdqO04OVL+lgabCoZRIUHE5SWjKsivlo+HthRAB qfoH0nWX2sXu+aQMSiJjk0j89nQFyqGseHXHg0SWviKU8Ed0t8s0xLpTFNDqp5m0VSTS rqyDIa681ZZXfbwGIg3Fx1nVv30lTRy4bmcwcv7oSV3YhtKenNtVkkI28sD/d8Kv6i4q cVNQ== 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 :content-transfer-encoding; bh=TOIdPOAGPt8+fQFuWE+78BCiESNSOo55jhWTB+QgCQo=; b=gj8Lv6+KaXuwXEcRB95ZU+GfgRqhemQMEdSVy3ESKgXebdXE/E+DKPS4+6icOP/wGf xN/scy5VoqnZqFsamrwp9UAiGOMCBX+OEqLnFvbRIfmUCcKCTOwjFmHHx0r/wImkn2TU BOQWqtqWGZ7Nd8Jc4z82tawMIxKXlpqtcsRfD7eC71hhm1llNrOOpFsbLk+X8Aq9rxyP Af/Dmifhylu4j7EMlTtRNkVShBWzE2N3hT76QR3fG98S/W43ShwnVQ8qjMVPKO04C7zU S8IaeTU1yvBYAZs/2yupBrWG7R2c/+TGqSMOIHWY8RgNz2Cqb4u4mWFKSsqzd/LxeLNG /CRg== X-Gm-Message-State: AOAM531hplEA7kouft21P8k48UBTGutZCkNYENhW9UHZ7dwYR3Xsl96d GrmM0dUP5DK+Ua0GjIpP/+pjMg3a+4T+iNKpd8FlYkOg8+0gjg== X-Google-Smtp-Source: ABdhPJzWjbEQPhtvQ3JGQPKkDp8q0nArjLEVRwpY/5OapZ5MFPpVjnjgdF5DfnRwyY3R2ZgKFLkq34xHj8cxCCOjdVs= X-Received: by 2002:a05:6902:70d:: with SMTP id k13mr21277094ybt.387.1631015152716; Tue, 07 Sep 2021 04:45:52 -0700 (PDT) MIME-Version: 1.0 From: Michael Folkson Date: Tue, 7 Sep 2021 12:45:42 +0100 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 07 Sep 2021 13:39:13 +0000 Subject: [bitcoin-dev] BIP process meeting - Tuesday September 14th 23:00 UTC on #bitcoin-dev Libera IRC 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, 07 Sep 2021 11:45:55 -0000 With a new BIP editor (Kalle Alm) in place and Taproot activation locked in it is probably/possibly as good time as any to revisit the BIP process and see if we can bolster it, improve it or at least inform why certain things operate the way they do. Hence two IRC meetings are being organized, one on Tuesday September 14th (23:00 UTC) and one on Wednesday September 29th (23:00 UTC), both on the Libera IRC channel #bitcoin-dev. Possible discussion topics range from the relatively mundane (should BIP champions need to ACK basic spelling change PRs) to the possibly contentious (what role if any do the BIPs have in informing the community of soft fork activation parameters). At the very least it would be good to address some common misunderstandings and subtleties of the BIP process that many (including myself) are lacking context on. So if you are interested in the BIP process or certainly if you have experienced frustrations with the BIP process in the past as a BIP champion or BIP contributor please attend and we=E2=80=99ll see what progre= ss we can make. There is a BIP process wishlist that some have already contributed ideas too: https://github.com/bitcoin/bips/wiki/BIP-Process-wishlist And of course BIP 2 outlines the current BIP process: https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki This is being organized in the spirit of seeking to improve a process and a resource that we as a community all rely on so please engage in the spirit that is intended. I will keep the mailing list informed of anything that comes out of the meetings and the #bitcoin-dev channel is open for discussion outside of the meetings. --=20 Michael Folkson Email: michaelfolkson@gmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3