path: root/1a/352990fc28ebaa69d29346b624861e860e3f8b

Return-Path: <karljohan-alm@garage.co.jp>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 6D689C000D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:28:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 4F7C1605B7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:28:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level: 
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 8A0UrGbheNSR
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:28:46 +0000 (UTC)
X-Greylist: delayed 00:09:43 by SQLgrey-1.8.0
Received: from mta18.mta.hdems.com (mta18.mta.hdems.com [52.198.247.241])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 4FD796066E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:28:46 +0000 (UTC)
Received: from mo.hdems.com (unknown [10.5.84.143])
 by mta18.mta.hdems.com ('HDEMS') with ESMTPSA id 4H8bm42697z1XNwFY
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:19:00 +0000 (UTC)
X-HDEMS-MO-TENANT: garage.co.jp
Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com.
 [209.85.167.71]) by gwsmtp.prod.mo.hdems.com with ESMTPS id
 gwsmtpd-trans-26ff106c-e842-4247-913d-a6782a9a0833
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 10:18:59 +0000
Received: by mail-lf1-f71.google.com with SMTP id
 bu42-20020a05651216aa00b003f69fb173a2so912839lfb.13
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 15 Sep 2021 03:18:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:content-transfer-encoding;
 bh=jEO+J6g7seQFz8fHUXqSAPfhqcQtGQLKaimlzzZEhWI=;
 b=HiEf31nJPiQp9ZwX+3ZEpudh7r+oenTBIWyokkIf3mekqzXf0lgT2asguFvU7pJj7i
 RR95lY89NEhEkVTlx7DlIEuthISt2oATxDroKtfXfAEdioJRHPf88D+6ofcgDdw4GrJa
 o8MkILr8/v2ykdTSzOpwCJj3jLLA7MGhLtEbJX/21ouHMfvGDLVErgCaIsd7KWBYdMnk
 eyHnS+2MjA3funQzfXF1S/by1K2RpMF0o+OclJDkI0ReV2GF7f1h2ZOyUqnG3qOG88x6
 nchozfbOiCAi7p6SEO/eJNmzM93kI/TpNoJc9VZ+HYJlvEv9w87qDBDSINVW2oqB2QUm
 WU4g==
X-Gm-Message-State: AOAM532O7nGa+SdddsOGbF6NUanI0BkvsOLu64BrBEu79JRJjN1vWC9p
 16Uv/yoilBESqo9ygbEMA0xOSZgP/BYGiYznrnywkyKUHbpMDq5X2pkPWbFCv0wedsxiCcNqKZX
 JcU0wvXsiXVnKr6DRpK9SOa88cfEe9pShaPHgDBZoSesZa5Fh39rkB3xFkl4rNlosxUPiYS3yoX
 6J/wp7HGgj8cnegB1lZeZuJ5gp4kWYraw/UFkX6VBZZYOr8AjSagWUfcXXJwRysk8Ap2VBMkLIl
 QB0SMcnjACc+4wyIT62iOEifbMlcRNOg7lrB2MmO4hJPzGqQqDaq/En8gOSWg5sZQlbAqJBsdmH
 w40BKXZuD0EOev7mLMg+z7FoV90/
X-Received: by 2002:a19:4346:: with SMTP id m6mr6313473lfj.406.1631701138315; 
 Wed, 15 Sep 2021 03:18:58 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJx8zZNPndLXlQmp3disZiuv49Lvff1iOXRvUMrqtYMzdz0Agt2B74QE8K1CoPIB4YbVeHPKdNmeHrnD+xWWiD0=
X-Received: by 2002:a19:4346:: with SMTP id m6mr6313448lfj.406.1631701137800; 
 Wed, 15 Sep 2021 03:18:57 -0700 (PDT)
MIME-Version: 1.0
References: <CALJw2w7f2JfskLQPwEBsKTqpJBo+qccP-y6oAX5EEzJ3vo0Grw@mail.gmail.com>
 <10670b5b-2c3f-61d0-c2e4-0d496d14f2cd@federicociro.com>
In-Reply-To: <10670b5b-2c3f-61d0-c2e4-0d496d14f2cd@federicociro.com>
From: Karl-Johan Alm <karl@dglab.com>
Date: Wed, 15 Sep 2021 19:18:41 +0900
Message-ID: <CALJw2w4v5weerSGBCj0v=QB=0uG7YmkOtEs_kXrPydoS-_hibw@mail.gmail.com>
To: Federico Berrone <me@federicociro.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] BIP extensions
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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, 15 Sep 2021 10:28:48 -0000

Hi Frederico,

Welcome to the bitcoin-dev list. :)

Michael Folkson is currently pushing for a revision to BIP 2, which is
discussed in the "BIP process meeting" thread here. You could help out
by participating in that process. There's a wiki page with ideas for
this in [1] and the current plan is to modify [2] or some other pull
request to reflect what everyone decides.

[1] https://github.com/bitcoin/bips/wiki/BIP-Process-wishlist
[2] https://github.com/bitcoin/bips/pull/1015

-Kalle.

On Wed, 15 Sept 2021 at 17:29, Federico Berrone via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Hi Karl-Johan,
> I fully agree with your proposal. In order to de-clutter BIPs and make a
> more understandable proposal, we can add the additional information in a
> separate piece. Also, this would maintain the original proposal without
> any modifications, showing the original spirit of it.
> Let me know how can I help you with your proposal.
>
> Regards,
> Federico Berrone.
>
> P/D: This is my first participation in the bitcoin-dev list, sorry if I
> am breaking any rule, I would be glad to know if that is the case.
>
> El 15/09/2021 a las 8:14, Karl-Johan Alm via bitcoin-dev escribi=C3=B3:
> > BIPs are proposals.
> >
> > They begin as ideas, are formulated and discussed on this list, and
> > assuming no glaring flaws are observed, turned into pull requests to
> > the bips repository, assigned a BIP number by the editors, and merged.
> >
> > It is then organically incorporated into the various entities that
> > exist in the Bitcoin space. At this point, it is not merely a
> > proposal, but a standard. As entities place their weight behind a BIP,
> > it makes less and less sense to consider its author the "maintainer"
> > of the BIP, with rights to modify it at their whim. Someone may have
> > agreed to the proposal in its original form, but they may disagree
> > with it if it is altered from under their feet.
> >
> > BIPs are modified for primarily three reasons:
> >
> > 1. Because of spelling errors, or to otherwise improve on their
> > description without changing what is actually proposed.
> > 2. To improve the proposal in some way, e.g. after discussion or after
> > getting feedback on the proposed approach.
> > 3. To add missing content, such as activation strategy.
> >
> > I propose that changes of the second and third type, unless they are
> > absolutely free from contention, are done as BIP extensions.
> >
> > BIP extensions are separate BIPs that extend on or an existing BIP.
> > BIP extensions do not require the approval of the extended-upon BIP's
> > author, and are considered independent proposals entirely. A BIP that
> > extends on BIP XXX is referred to as BIP-XXX-Y, e.g. BIP-123-1, and
> > their introductory section must include the wording "
> >
> > This BIP extends on (link: BIP-XXX).
> >
> > ".
> >
> > By making extensions to BIPs, rather than modifying them long after
> > review, we are giving the community
> > 1. the assurance that a BIP will mostly remain in its form forever,
> > except if an obvious win is discovered,
> > 2. the ability to judge modifications to BIPs, such as activation
> > parameters, on their merits alone, and
> > 3. the path to propose modifications to BIPs even if their authors
> > have gone inactive and cease to provide feedback, as is the case for
> > many BIPs today, as BIP extensions do not require the approval of the
> > extended-upon BIP.
> >
> > (Apologies if this has been proposed already. If so, feel free to
> > ignore this message, and sorry to have wasted your time.)
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev