Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 47743C000B for ; Fri, 23 Apr 2021 07:51:08 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 29536843CC for ; Fri, 23 Apr 2021 07:51:08 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nk7byKbpl0qz for ; Fri, 23 Apr 2021 07:51:07 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) by smtp1.osuosl.org (Postfix) with ESMTPS id D59AF84333 for ; Fri, 23 Apr 2021 07:51:06 +0000 (UTC) Received: by mail-yb1-xb2d.google.com with SMTP id g38so54584752ybi.12 for ; Fri, 23 Apr 2021 00:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XvK9L1huxH67G8T5WqUWZzo3BQeZAl6rVEkyhccn3eU=; b=nbIg87GuvOwfii0KKERVpEcRcHNB4W+l7MAXsOfGJX6/U8LFcV/ZWwD5e1Z9gW9x+6 MuEs6ZkM1abW9lxoGaThwmgN9A2Ly8vBAOTXBR182l40oisac2U8i4x6l2KE4O2ZSyFe MY/o0LA5c+g6xpQXAnaFPLGnv27WNlbSqhhcU04afZ3KzH9tjFB0zzscoT3soUqSkUZQ H24+ML/CHsUHEt8udNjjUPo15pKTmjn9HhPypG7XdYlwc1J1C5iOb3k0/9aQOkI/uQ4U CpgOE2HrfuTwTEvXV2HTCcF4/+AUs/1f9NGlNJ6tX69Zp6HJmUmKSGzpMaASehhPM/Yx SqVA== 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; bh=XvK9L1huxH67G8T5WqUWZzo3BQeZAl6rVEkyhccn3eU=; b=ul0tFst4wigCwRvsr2i5VR9x96BribUK9H+C1DrL3y/IaZtLVtdLJdsJggcBoVuzXX 2TLjfkLuUgdh+jf8oyxc1zufpW+z3QhbS728IibSSEdmVX2EZdwfWURGtm8vL1gbyqKU ZfHMAFsJZarduS7IwVQ0gsAcPG/ZNPOrqqqyC/VFCWyuFsFfUCyHQZCa5HzvVzByN/gB rn0fYMtCYiUMz5irHfjROMjkAZr+6cuzvcleMVUPsg2Ml5LkKG+hLluJCW1OsFsO/UFt qOVphi9xEF42zm1pcYaFQm0u780ETl32/40fUdmKGHW6VTFfXPjDqT8N429wPWlyynQ2 ARcA== X-Gm-Message-State: AOAM530z2ftcXRcEJyLCrGrNwTWwmJ+UFghKKUPHLl1maPF3CorZ1gQo 7GIvxZTUjeZnhpyBt7J8OPHodl3lSwLuVN6apf/f/Bq9e8w= X-Google-Smtp-Source: ABdhPJylxqJzEBRuzhpLT3sR9FEWhFUaphae1uYZVROhgjCxFJxeKHZQuyr/kv/KcTD8Jm7vXrJ/EMVjXchhjA3zpP8= X-Received: by 2002:a25:ab88:: with SMTP id v8mr3479063ybi.500.1619164265696; Fri, 23 Apr 2021 00:51:05 -0700 (PDT) MIME-Version: 1.0 References: <202104230209.05373.luke@dashjr.org> In-Reply-To: <202104230209.05373.luke@dashjr.org> From: Pindar Wong Date: Fri, 23 Apr 2021 15:50:53 +0800 Message-ID: To: Luke Dashjr , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000e3d3c405c09f0e2b" Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm 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: Fri, 23 Apr 2021 07:51:08 -0000 --000000000000e3d3c405c09f0e2b Content-Type: text/plain; charset="UTF-8" ACK. p. On Fri, Apr 23, 2021 at 10:09 AM Luke Dashjr via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Unless there are objections, I intend to add Kalle Alm as a BIP editor to > assist in merging PRs into the bips git repo. > > Since there is no explicit process to adding BIP editors, IMO it should be > fine to use BIP 2's Process BIP progression: > > > A process BIP may change status from Draft to Active when it achieves > > rough consensus on the mailing list. Such a proposal is said to have > > rough consensus if it has been open to discussion on the development > > mailing list for at least one month, and no person maintains any > > unaddressed substantiated objections to it. > > A Process BIP could be opened for each new editor, but IMO that is > unnecessary. If anyone feels there is a need for a new Process BIP, we can > go > that route, but there is prior precedent for BIP editors appointing new > BIP > editors, so I think this should be fine. > > Please speak up soon if you disagree. > > Luke > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000e3d3c405c09f0e2b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
ACK.

p.

=

= On Fri, Apr 23, 2021 at 10:09 AM Luke Dashjr via bitcoin-dev <bitcoin-dev@lists.linuxfound= ation.org> wrote:
Unless there are objections, I intend to add Kalle Alm as a BIP = editor to
assist in merging PRs into the bips git repo.

Since there is no explicit process to adding BIP editors, IMO it should be =
fine to use BIP 2's Process BIP progression:

> A process BIP may change status from Draft to Active when it achieves<= br> > rough consensus on the mailing list. Such a proposal is said to have > rough consensus if it has been open to discussion on the development > mailing list for at least one month, and no person maintains any
> unaddressed substantiated objections to it.

A Process BIP could be opened for each new editor, but IMO that is
unnecessary. If anyone feels there is a need for a new Process BIP, we can = go
that route, but there is prior precedent for BIP editors appointing new BIP=
editors, so I think this should be fine.

Please speak up soon if you disagree.

Luke
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000e3d3c405c09f0e2b--