From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 27 Mar 2024 16:47:05 -0700 Received: from mail-ot1-f63.google.com ([209.85.210.63]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rpcz2-0005Za-NT for bitcoindev@gnusha.org; Wed, 27 Mar 2024 16:47:05 -0700 Received: by mail-ot1-f63.google.com with SMTP id 46e09a7af769-6e6a865d967sf354860a34.1 for ; Wed, 27 Mar 2024 16:47:04 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1711583218; cv=pass; d=google.com; s=arc-20160816; b=Rl7i2+8Cz1sXx339DVSlNRVMqMmhnTwwAjcWOjk6sSkhuadXk/fkWj4RaAEAZCZ6gY 8k7T+XEzFhavILNiwv6BzsZC0OiwbMH/XFViNKj0rcz+BG/iOuNQLSkWxcDx/eh7ezpy SWpdFlzeLmDXE6+4l9zgKMTjKoQOA8je3TSpMJIU1Xuxux7J9ry2nx+yVntF5RGUGWDt XQo+TGziSffQTKrymhDgHIuk1Knid7KbrcqpIjENmyjED0vUa4/kVa1cIHiidGZbtn44 EeZ3kZEOyroaZCTe6zFC68IVSdQnCyIbeCjFc66FHGUEFxd54ophtTkcE6omYS8ofQV6 pY3g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:mime-version:references:message-id :in-reply-to:subject:cc:to:reply-to:from:date:feedback-id:sender :dkim-signature; bh=K1J5ngSMW11Rpg3+WtzkepTagsubA9H6m2KKEz0Rjuc=; fh=u2602b9wSjKobBtoUxEJ3dZBu2SW7D6Zw5XzoCcYq0w=; b=PcjmBeEzheUl6Ncabc4gO0Fqv0Cuf3yEjQBwCgA6XCl6Fb2V9ahNm0XRowf567VCJz VFojCRB20qY9q5UHp+8EHn7xNn+8kBlplVTM84LYAhufwTQqXSF+e5c13o39xfYcLOJk HHWF8XAMfAN/hDe4+I2EmbShUlYsf55JB6aCfVLAu7ZzO1ES+soZzA0CyjNpmQxSDbv9 QeW/ixYPeZSrG2pACC8232BRsTA3Vtmz4JuIQ+S0d4OFIQOXAswxumGgxL4ET6LEqFa5 KxBEzkALCEpoDWAIfxeZfqVeXLuDXvWA1IV71KCdUvzNxaQq3F0f5/1vt74ca3z15lry v8Cg==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@netpurgatory.com header.s=fm2 header.b=YU4Cih9z; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=MjQk4I9A; spf=pass (google.com: domain of jcv@netpurgatory.com designates 66.111.4.27 as permitted sender) smtp.mailfrom=jcv@netpurgatory.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1711583218; x=1712188018; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:mime-version:references:message-id:in-reply-to :subject:cc:to:reply-to:from:date:feedback-id:sender:from:to:cc :subject:date:message-id:reply-to; bh=K1J5ngSMW11Rpg3+WtzkepTagsubA9H6m2KKEz0Rjuc=; b=ji2OaoZfkT6KwSiHvgrqUOkji/J6124CfzUe64qPL181r+jOfo5Jjp4CuJcYA8voLP A0em5ftakp+NemByDJffnq0gs4YVL3zPejJevNhYySkHzrg3oXbPDVaTebnKrNLyO4wk kK9KYsB76jlKxQNCLDnBXGsFPWjsKBTfxwNr+T5+pcF9O+pv4kGFUlC3e4JUtUEVqzzy WAUo/M0XwSPFDGXcTiIWi2to60D147eKxdcjr7kApJLOoHPnBxY1RF/Mu26HcVmqRX4C pb4SsfaNyuGcyJD6IOax4cwHd8X4opVk4GWVqODKiT2rte7w3x8YMdMMPBGX28BTAJw0 3EBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711583218; x=1712188018; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:mime-version:references:message-id:in-reply-to :subject:cc:to:reply-to:from:date:feedback-id:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=K1J5ngSMW11Rpg3+WtzkepTagsubA9H6m2KKEz0Rjuc=; b=YYfTj2d5uorQY0XRcjPoB7Y9ogY3EQ07nnq5evWXoR4YJxHUydLJ1pUf4JhlAzL+XQ iQ4btVonOwmltCzzyGx4rN/ZmmXJJThROGFpSKfSCVDvOROKvjizNGXCBYl3iWJYgtPM pUwCexF4RpnDQMK3W0MPV4Kl4r3T2C2+pklWS98dtikQ5cp/+XOkaSSb0PIgjeaHgcFS ZpUdYNi9L71gcDC8LOiuOi3pkW4YM6B1jT0t0OsvYDvhS4ZP49rL1MNJvCgR4ClNc/1Y bBehZzpYtXbmZ7R0fdrEVH9HTY8E6d6yUZYo1GYpWXxCP3p2O/j5AXHWpIRNIYdQ00L4 3qog== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCXbVIYI3Z/UXTrk3dfiRN2JeKiPnJdjaD0/WF4EgpRh483k+wzJ9//f1m6kHuAnjaKBoE/2+0RA12/099amZLSqar8I7fU= X-Gm-Message-State: AOJu0YziNXPybLnGpkyyPEG4bDjKpAf19P/7N79XiLnXjy2Hjya1j47n cA5w7vteFA9egmTy2qlkO1kS1fODLdCOhy3FXfHlNTAW12LjhhfndMo= X-Google-Smtp-Source: AGHT+IELXHXezt1Dm+FnT3Yx577PKzfys2hapgZELRbifBiE52AFpG2aSHuWNwFe7kM1LHZ1a0uXgg== X-Received: by 2002:a9d:65da:0:b0:6e6:af6e:9870 with SMTP id z26-20020a9d65da000000b006e6af6e9870mr1636955oth.19.1711583218518; Wed, 27 Mar 2024 16:46:58 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:622a:1054:b0:431:5f09:9515 with SMTP id f20-20020a05622a105400b004315f099515ls451335qte.1.-pod-prod-05-us; Wed, 27 Mar 2024 16:46:57 -0700 (PDT) X-Received: by 2002:ac8:7f11:0:b0:431:4cfa:799d with SMTP id f17-20020ac87f11000000b004314cfa799dmr74966qtk.12.1711583217517; Wed, 27 Mar 2024 16:46:57 -0700 (PDT) Received: by 2002:a05:620a:4620:b0:78a:4068:6a01 with SMTP id af79cd13be357-78b7b6da342ms85a; Wed, 27 Mar 2024 16:39:05 -0700 (PDT) X-Received: by 2002:ae9:ee18:0:b0:789:e524:933b with SMTP id i24-20020ae9ee18000000b00789e524933bmr1011001qkg.31.1711582744976; Wed, 27 Mar 2024 16:39:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1711582744; cv=none; d=google.com; s=arc-20160816; b=ZoQhUbG3utXokhMZVRzaxTvPZ+nM8+/SoqswTXme6+0GGKQgVpKsWrE8M8ai8YCg30 ooECSjGwoyB2O4klT3I1IpZbiqzgZzFvES634/9XHNKtu7JTlhWvAvY9HOqvwZWSMijx LvOh0djZJZTywPT9m7ThnNgydS8QWy5gH4T4w4xCWrxfF4ZyBZ150v5G/mOrPQp1vfXT saeZ4jhtOevVQ8RbHsrcl8Yuh9M3kAnsLu6HD8PYqLjBRTbxyTIpDM1FnB+B6e9geP4S oiMWQ4CSXbMz8PgRVhj9bm3PvK58d24j/KrLFHODfzWtFW6nXdb7scavo/J8Djlx/7Sd tC3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:references:message-id:in-reply-to:subject:cc:to :reply-to:from:date:feedback-id:dkim-signature:dkim-signature; bh=KRfb+yxF3Lw969dqi7xUbdFxGsaUWzd2ynf6bDAQszs=; fh=foaZ9w3C3c5ltuXRyLrsJcSZd5F+/L4e8AHpKYxjE8o=; b=Buc6Fyymo1d+mqGlUxKTzu1dWfkfJeWG+Oethmza0Nxa4znBiKsNpKG7MKoi5cdKe6 aJ4NEh8e50TqlGHqVt1yOYR9htVDX7/zSSGZTb8qL0hh/glmgCd6RwnAS4eRWfU8XJ8e rEWcdcSZOfJdbIj9LNzIzE55Qd4uBg0qDo7bSguzxyuUal/JzJL9kvdpw3NE595GiJYm CC6sm3lt81uMLvSuYep+GqdI9lgF6iYd7YFSa/C4vBlTyzRCZucBDc50Le6GSxZ12G6m grwe1qrd/UDLPxy1CO5nH4qgsXxDe5mnanLqIIg9ZUGI3KpVKsjYDXUIIraVWy9AzsOz ZlzQ==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@netpurgatory.com header.s=fm2 header.b=YU4Cih9z; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=MjQk4I9A; spf=pass (google.com: domain of jcv@netpurgatory.com designates 66.111.4.27 as permitted sender) smtp.mailfrom=jcv@netpurgatory.com Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com. [66.111.4.27]) by gmr-mx.google.com with ESMTPS id m25-20020ae9e719000000b0078a45a5c896si18717qka.3.2024.03.27.16.39.04 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Mar 2024 16:39:04 -0700 (PDT) Received-SPF: pass (google.com: domain of jcv@netpurgatory.com designates 66.111.4.27 as permitted sender) client-ip=66.111.4.27; Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A09325C0066; Wed, 27 Mar 2024 19:39:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 27 Mar 2024 19:39:04 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledruddukedgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffohhmrghinhculdegledmne cujfgurhepfffhrhfvvefujgfkfhggtgesmhdtreertddtjeenucfhrhhomhepfdflohhh nhcuvedrucggvghrnhgrlhgvohdfuceojhgtvhesnhgvthhpuhhrghgrthhorhihrdgtoh hmqeenucggtffrrghtthgvrhhnpedvvddvhfetgfdtjeegkefhheehiedtveefgfefkeev geeikeefhefgledujeeljeenucffohhmrghinhepnhgvthhpuhhrghgrthhorhihrdgtoh hmpdhgohhoghhlvgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhep mhgrihhlfhhrohhmpehjtghvsehnvghtphhurhhgrghtohhrhidrtghomh X-ME-Proxy: Feedback-ID: i6b19477a:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 27 Mar 2024 19:39:04 -0400 (EDT) Date: Wed, 27 Mar 2024 19:39:03 -0400 (EDT) From: "John C. Vernaleo" Reply-To: jcv@netpurgatory.com To: Murch cc: bitcoindev@googlegroups.com Subject: Re: [bitcoindev] Re: Adding New BIP Editors In-Reply-To: <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> Message-ID: <84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com> References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org> <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="37792500-517051172-1711582744=:7420" X-Original-Sender: jcv@netpurgatory.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@netpurgatory.com header.s=fm2 header.b=YU4Cih9z; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=MjQk4I9A; spf=pass (google.com: domain of jcv@netpurgatory.com designates 66.111.4.27 as permitted sender) smtp.mailfrom=jcv@netpurgatory.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.8 (/) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --37792500-517051172-1711582744=:7420 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable For what it's worth, I strongly support Roasbeef as a candidate. That said, I would find it helpful if someone could go through the thread= =20 and list all the people who've been proposed so people know who they=20 should be thinking about. ------------------------------------------------------- John C. Vernaleo, Ph.D. www.netpurgatory.com jcv@netpurgatory.com ------------------------------------------------------- On Wed, 27 Mar 2024, Murch wrote: > Hey everyone, > > I wanted to check in on the topic adding BIP Editors. There seem to be a= =20 > number of candidates that are willing and able, and there seems to be bro= ad=20 > agreement among the current editor, the readers of the repository, and th= e=20 > contributors to the repository that additional help is desirable. > > I have seen some support and reservations raised for pretty much every=20 > candidate. A few weeks have passed since this topic was last active. So f= ar,=20 > there seems no clear path forward. > > If we are all just in a holding pattern, perhaps we could timebox this=20 > decision process: how about we invite arguments for and against any=20 > candidates in this thread until next Friday EOD (April 5th). If any=20 > candidates find broad support, those candidates could be added as new edi= tors=20 > to the repository on the following Monday (April 8th). If none get broad= =20 > support, at least we=E2=80=99d be able to move on and try something else. > > I propose that all editors share the same privileges, especially that any= =20 > editor may assign numbers to BIPs. If there is guidance to be provided on= the=20 > process of assigning numbers and number ranges for specific topics, it sh= ould=20 > be provided by then. If the editors decide on a single number authority a= mong=20 > themselves, that would also be fine as long as it doesn=E2=80=99t become = a=20 > bottleneck. > > As Tim and Chris have suggested, it seems reasonable to me that assessmen= t of=20 > the technical soundness can be left to the audience. BIPs have been publi= shed=20 > in the repository and set to the "rejected" status before, so it=E2=80=99= s not as if=20 > adding a BIP to the repository is treated as an unequivocal endorsement o= r=20 > implementation recommendation. > > Cheers, > Murch > > > On 3/14/24 07:56, Chris Stewart wrote: >> I agree with Tim's thoughts here. >>=20 >> I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make gre= at >> candidates. >>=20 >> On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffing = wrote: >>=20 >>> On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote: >>>> The hard part is evaluating >>>> if the new proposal meets the criteria - which definitely needs dev >>>> skills (mainly for technical soundness). >>>=20 >>> I'm aware that checking technical soundness is in accordance with BIP2 >>> [1], but I believe that this is one of the main problems of the current >>> process, and I can imagine that this is what eats the time of editors. >>>=20 >>> I'd prefer a BIP process in which the editors merely check that the >>> proposal is related to the Bitcoin ecosystem and meets some minimal >>> formal criteria that we already enforce now (i.e., is a full self- >>> contained document, has the required sections, etc...). This relieves >>> the editors not just from the effort, but also from the responsibility >>> to do so. Technical soundness should be evaluated by the audience of a >>> BIP, not by the editor. >>>=20 >>> Best, >>> Tim >>>=20 >>>=20 >>> [1] BIP2 says: >>> "For each new BIP that comes in an editor does the following: >>>=20 >>> - Read the BIP to check if it is ready: sound and complete. The ideas >>> must make technical sense, even if they don't seem likely to be >>> accepted. >>> [...]" > > --=20 > You received this message because you are subscribed to the Google Groups= =20 > "Bitcoin Development Mailing List" group. > To unsubscribe from this group and stop receiving emails from it, send an= =20 > email to bitcoindev+unsubscribe@googlegroups.com. > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/bitcoindev/52a0d792-d99f-4360-ba34-0b12= de183fef%40murch.one. > --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/= bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713%40netpurgatory.com. --37792500-517051172-1711582744=:7420--