From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 27 Mar 2024 17:21:48 -0700 Received: from mail-oa1-f60.google.com ([209.85.160.60]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rpdWe-0006Jh-FD for bitcoindev@gnusha.org; Wed, 27 Mar 2024 17:21:48 -0700 Received: by mail-oa1-f60.google.com with SMTP id 586e51a60fabf-22a0b3896a3sf391127fac.2 for ; Wed, 27 Mar 2024 17:21:47 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1711585302; cv=pass; d=google.com; s=arc-20160816; b=vEAfSU913y4WbGCIRljc/PQa7VcC7TySk3dDpAm8V0zyvkulfqQmuSzD6lNE4dfrTE LahuTpssr+yAQqOO9E/wIEJecZ19lpGU4pMRsYwFZADEfftZ/avAMAiXkAaoVom9Kmon ihdNAmdqGBHmufeA2lHGaSJ0HQm9nRVo6Z7Qc175RE9SD1QmbTutcQ8VltgkoNGB0kDt PNmVPjxeRxek+TLOtdRSh25Tszk/fS/S97wuHronhYy/7C8vmSktvY36UvSS26BLnJ1c cBI6GYTnSW8Wrs99+vt0lfmZVvYFFxxPMY7qtOfrPnqAZggnUT1ULXYTyfQ24Xs48iQN 5x/w== 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:content-transfer-encoding :in-reply-to:from:content-language:references:to:subject :mime-version:date:message-id:sender:dkim-signature; bh=JO0HbEhcXnAaYPFVXZ6tyyU3JVtg9+UHcig+2dSrOZ0=; fh=XmuebnY7+xK6cIehils//m/dz/g39w0b3W1FzZAz+oY=; b=bszpZJ9OVU6ZleOdn39mMliwAFchw7ON3aXyTdMLY3Ui59IgVCcZw1s6MMEoOih4nM SqX3qm7dP6JCuprexCopA22RBJEpuNiN5SsYuhhiUvBXyfxxgBmoa9gn+NifRrAC4TN4 q4DY9Urhl/YC44Zsm7LrL4Jk9bhDTZdtwQImwpn+2hLELfwd77AUHsM8AkeAWhc+5A5/ WtaGSX1ti3nDmfhhps25s7BHIZT8/0xNDIZ36c5g8/dXnysSGlhDmKaURCA1XXeLZMxb 324NtIzdgUFgX2PEhTKvTCPfgIcGc8lvLa1GWq1zOFIFsyADOycrAo+BNtnTbtzIfzmH vrKQ==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@mattcorallo.com header.s=1711581662 header.b=EwQ2WtmI; dkim=pass header.i=@clients.mail.as397444.net header.s=1711581664 header.b=UiN4iEA8; spf=pass (google.com: domain of lf-lists@mattcorallo.com designates 69.59.18.99 as permitted sender) smtp.mailfrom=lf-lists@mattcorallo.com; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=mattcorallo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1711585302; x=1712190102; 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:content-transfer-encoding:in-reply-to:from :content-language:references:to:subject:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=JO0HbEhcXnAaYPFVXZ6tyyU3JVtg9+UHcig+2dSrOZ0=; b=VK572ke9uRrVjmAmVF8U7AuJ5iTcvJKOEhKxIMYLiEH/sqeiwW/pNwvUTwndpGsEhP GB9x3Fq4S8hlMEjDxSyuMoRN+XT35AFBnI9k6aPXDHVrdIsvEvmbzdJ6Bff+GCE9TgCi 1KkhibIjHy5VDs08L/QHwhnWg375H5f+RGqR36CQJuS5/CPeWUtUP7yXN00tOMk6sB2m 8FABw04+W+4MGaIl6qPkd2CpRydi0iYe2XKOvvUDis7qj53nYNLVbrc2phOBaT6VGb2Y C9Iox+RWdhAl68lgexE4xbsbM71tsjpq1asxSFib3EUnukdy+3Jr/vHBTSwfGaVNAQZT yJLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711585302; x=1712190102; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:in-reply-to:from :content-language:references:to:subject:mime-version:date:message-id :x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date :message-id:reply-to; bh=JO0HbEhcXnAaYPFVXZ6tyyU3JVtg9+UHcig+2dSrOZ0=; b=vYo39gOAattPlQcdHYh/2gWIqr8T2S0LvK1ffdQUJIQi0qE8EFhhaiATn2MSY9eseJ rASCtCgPlJ2y04Ap8yo4BzoNCEAxlTc9GAyldMudt/89XbvaG8MsXHh0r4tyoOWYrhWy e6Af7MtTr4QeGj3HJaooc4y13ARJY8etdV0c076Se+cPnFkTT9lyT7+viE0j8AkfYXw7 dtGuPHqdwSzmzm6nJtYAWsI0jFTed2HLODqewT0g8NYaXP7AwzHLcC6DRwmOXmyBiOme XJ6fiWcpYSnPWKCNfKGejhWLHc/Ov/Tq8stAcfD0kTAuc+v7mEuHaBAgyIAIEYT6Xcih 0cSA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCUaIYALHRNR1tVLjDy6ZBEIka7oJgzkRzhQvjPzPIM44aMRXq+D8bbGP73mGnYNK8k+j8NTNaqp8sbP9ZvB82BAhVZj/h8= X-Gm-Message-State: AOJu0YxKCxr60H9B4771IpDsppbL7lZ1aNEJbryfQVZX+vQx7xJmZ50D PRbzbNpiO1eS/iDHk/rk5dbVxxa11ClJzJX2/SgZFf/hh7wVgF80 X-Google-Smtp-Source: AGHT+IEu+nxESY++CA7qnRmvVeGrDpaNgGCk1Wbe3uAJL1irGWlBTTCDY1gTxzYw8vA4FFLxODSVWg== X-Received: by 2002:a05:6871:72a:b0:21f:412a:87a8 with SMTP id f42-20020a056871072a00b0021f412a87a8mr1377414oap.41.1711585302074; Wed, 27 Mar 2024 17:21:42 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:6871:4398:b0:22a:550c:8d05 with SMTP id lv24-20020a056871439800b0022a550c8d05ls607483oab.0.-pod-prod-07-us; Wed, 27 Mar 2024 17:21:41 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCUHVEIrnGM626A+LV27Xf3Q5fKTvWCbsMf/mkCMo01rs0JGYtwZLH2Pde7x2xBWxHrYM2eQz+TPe0eGlAMRfpyax/Cn5KbIiGQ2Xro= X-Received: by 2002:a05:6870:5690:b0:221:c9ef:54 with SMTP id p16-20020a056870569000b00221c9ef0054mr3802oao.5.1711585300923; Wed, 27 Mar 2024 17:21:40 -0700 (PDT) Received: by 2002:a05:6808:1526:b0:3c3:c0e6:782f with SMTP id 5614622812f47-3c3de74db1dmsb6e; Wed, 27 Mar 2024 16:54:58 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWzFFRyhw74q0b5G48RwuNTRHNbBe0iHrEKQvvq3yCayy5MsmuiVrbbUEwYKUZdD1mQ30vmd8iVz4w/7RKncF0wYO7QsOzJ4hHQbLk= X-Received: by 2002:a05:6808:2117:b0:3c3:de94:7d2c with SMTP id r23-20020a056808211700b003c3de947d2cmr1972650oiw.52.1711583697530; Wed, 27 Mar 2024 16:54:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1711583697; cv=none; d=google.com; s=arc-20160816; b=punNIdAviBbldDCacemthMogspq2qCJ1vcHXdLNZgz5k+7P1H90UF1jzGG9NvBhTmT Ngt+UUNGyLdic8seNtW8L2HeV8W8VHcTVlrmyVSqDFJa16kBluR7MSVzKKsTYcJ8LREk c+VA92FN47dm05mb4G7KSFtMe+tSkTq9yYyDHc7TQcph2sgzz9QeOGtz9Pe6FnHgthr9 PpOYtIg4lu/ICVuMo9uWNwtVcVZD4S1Wau0AebYsG5furepVoEEfnG0ncEHUSQqv//je JZnnhXcgKIeEilNOGBrsECLB8chsloRo1sWrz+OL0EFaGxKR2BBWvFKPtXlx+CWeY7Oj iXbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:mime-version:date:message-id:dkim-signature :dkim-signature; bh=CKkLbkaclY7DHRULaqEaXiAlwIYHmQhFtJ33GODcL0A=; fh=TJPiHndWgZLp4Nh/TfbBdrnPh+l+KbAXZZIH4GC8D3A=; b=YCYSotJM8woX9U5x8a7ZHo5fjBoXQwLcJWwLWFuvmo6Dq/fY6xkd8pLg8ulCwrX3/c znD61EOKVfILfox7SqAU2WUjJwNk0+/tGnLRPlOdjQO9TzC9bxz9vDqbG1v6Ovpw6u9m 6A8Ey/ew28Sy0FUBBX0kFrTl5JGvewMgLuoVCF3fjz7uCy36TE0sSAGRdt10jTZO87zV 8api7+6rC+kT3zY1BSAzGiyWgWK8cwtac/OihCvPgM2FuhB1RY+TYkGTjME0OAaxP0U1 v44YTF+QkM6aHc+hA/zZ7DnhZkpC33d/8rVVAE+tS7G+cbv1VcoBBq6McMxzkhnILPAX bijw==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@mattcorallo.com header.s=1711581662 header.b=EwQ2WtmI; dkim=pass header.i=@clients.mail.as397444.net header.s=1711581664 header.b=UiN4iEA8; spf=pass (google.com: domain of lf-lists@mattcorallo.com designates 69.59.18.99 as permitted sender) smtp.mailfrom=lf-lists@mattcorallo.com; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=mattcorallo.com Received: from mail.as397444.net (mail.as397444.net. [69.59.18.99]) by gmr-mx.google.com with ESMTPS id ec26-20020a05622a5b9a00b0043138879c53si19167qtb.1.2024.03.27.16.54.57 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Mar 2024 16:54:57 -0700 (PDT) Received-SPF: pass (google.com: domain of lf-lists@mattcorallo.com designates 69.59.18.99 as permitted sender) client-ip=69.59.18.99; X-DKIM-Note: Keys used to sign are likely public at X-DKIM-Note: https://as397444.net/dkim/mattcorallo.com and X-DKIM-Note: https://as397444.net/dkim/clients.mail.as397444.net X-DKIM-Note: For more info, see https://as397444.net/dkim/ Received: by mail.as397444.net with esmtpsa (TLS1.3) (Exim) (envelope-from ) id 1rpd6c-00GOJd-2y; Wed, 27 Mar 2024 23:54:55 +0000 Message-ID: Date: Wed, 27 Mar 2024 19:54:53 -0400 MIME-Version: 1.0 Subject: Re: [bitcoindev] Re: Adding New BIP Editors To: Murch , bitcoindev@googlegroups.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> Content-Language: en-US From: Matt Corallo In-Reply-To: <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Original-Sender: lf-lists@mattcorallo.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@mattcorallo.com header.s=1711581662 header.b=EwQ2WtmI; dkim=pass header.i=@clients.mail.as397444.net header.s=1711581664 header.b=UiN4iEA8; spf=pass (google.com: domain of lf-lists@mattcorallo.com designates 69.59.18.99 as permitted sender) smtp.mailfrom=lf-lists@mattcorallo.com; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=mattcorallo.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 (/) Seems reasonable to me. While there are plenty of competent technical folks who would make fine BIP= editors, I'd suggest=20 Kanzure and Murch as clear candidates over others: * Kanzure has been around for longer than any other candidate as far as I= can tell, and has=20 certainly seen more proposals for changes to Bitcoin than anyone. This make= s him a great candidate=20 to point new BIP authors to appropriate citations. Similarly, he has a long= history of being very=20 responsive, which I believe is part of the goal in appointing new editors h= ere. * Murch similarly has lots of experience dealing with lots of various ide= as around Bitcoin, but=20 importantly here also has worked extensively to document appropriate termin= ology for all things=20 Bitcoin [1]. This makes him an excellent copy editor of Bitcoin technical p= roposals, which is=20 basically the only thing the BIP editors are supposed to do. While there are a handful of other candidates mentioned in this thread who = are technically quite=20 competent, that isn't really the relevant criteria for BIP editors. Matt [1] https://github.com/murchandamus/bips/pull/1/files On 3/27/24 5:25 PM, Murch wrote: > Hey everyone, >=20 > I wanted to check in on the topic adding BIP Editors. There seem to be a = number of candidates that=20 > are willing and able, and there seems to be broad agreement among the cur= rent editor, the readers of=20 > the repository, and the contributors to the repository that additional he= lp is desirable. >=20 > I have seen some support and reservations raised for pretty much every ca= ndidate. A few weeks have=20 > passed since this topic was last active. So far, there seems no clear pat= h forward. >=20 > If we are all just in a holding pattern, perhaps we could timebox this de= cision process: how about=20 > we invite arguments for and against any candidates in this thread until n= ext Friday EOD (April 5th).=20 > If any candidates find broad support, those candidates could be added as = new editors to the=20 > repository on the following Monday (April 8th). If none get broad support= , at least we=E2=80=99d be able to=20 > move on and try something else. >=20 > I propose that all editors share the same privileges, especially that any= editor may assign numbers=20 > to BIPs. If there is guidance to be provided on the process of assigning = numbers and number ranges=20 > for specific topics, it should be provided by then. If the editors decide= on a single number=20 > authority among themselves, that would also be fine as long as it doesn= =E2=80=99t become a bottleneck. >=20 > As Tim and Chris have suggested, it seems reasonable to me that assessmen= t of the technical=20 > soundness can be left to the audience. BIPs have been published in the re= pository and set to the=20 > "rejected" status before, so it=E2=80=99s not as if adding a BIP to the r= epository is treated as an=20 > unequivocal endorsement or implementation recommendation. >=20 > Cheers, > Murch >=20 >=20 > On 3/14/24 07:56, Chris Stewart wrote: >> I agree with Tim's thoughts here. >> >> I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make gre= at >> candidates. >> >> On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffing = wrote: >> >>> 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). >>> >>> 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. >>> >>> 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. >>> >>> Best, >>> Tim >>> >>> >>> [1] BIP2 says: >>> "For each new BIP that comes in an editor does the following: >>> >>> - 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 --=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/f9435999-42df-46b5-86e2-7ba0336a9bf2%40mattcorallo.com.