From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 07 Mar 2024 13:00:55 -0800 Received: from mail-yw1-f191.google.com ([209.85.128.191]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1riKrG-0000xI-Ka for bitcoindev@gnusha.org; Thu, 07 Mar 2024 13:00:55 -0800 Received: by mail-yw1-f191.google.com with SMTP id 00721157ae682-609ff3206c3sf9086567b3.2 for ; Thu, 07 Mar 2024 13:00:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1709845248; x=1710450048; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=lff4rJyJPlLRFG8AIVxMTTemH3rUkoUmtpj7h9nnRDU=; b=czAHq3SzfcFP9k+jl6ad6eMcuJq7aeiArKM+Ysx2ZSdgJEB8vvsV6f0HNwtW0VjgFI 5wJgYKkB426IlBLaBfV02u5XnqqZlk7bfO4IhwnBy0YyBlFf6ynI+X6wzNUEcdp97e3C 7zMHjAy54lkbb1kSaGajr8eI+h5DYZ5wICDi7jszwLoNh26Je2oLBHtwlTJqpHU0up2t 11QJTrooWWvXjxqYLwDAT73FYYnZyeRdrKaJRYzAVsXrYLtlrmOLlQW7V2rT9sitgdFy qKIrCg46RP9w8P7vpRnIhwHWCLSg1hBlFD0onKvQUUc5yHDZkkGcHa9DzsdK89WX10UM NUmw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709845248; x=1710450048; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=lff4rJyJPlLRFG8AIVxMTTemH3rUkoUmtpj7h9nnRDU=; b=Vn4qZjCM0sypJpgztf0qh+73DchhgoXFD/XKMzzSjp2IRVaeIWv5CIvNgz/AVN/iTK xjKFrVYxaeGTQSWk4WR2dHInAw9eGg/bvq82DwlcyWJwzd+Aspc6VfXNyJyldDwcYWjC nwaK3h8AOG6zaKch4FBSISFya6d9LIy8JIIvWA4z47FohEsBr0Gr974V/gXp2jKDOc8I gMdXJIEdwwfChpAVNj0SspYzOWZS2d12KepYRshzFL9O98j8u7uRaduclDXl3s9ZFv/r +c8vg0tCn+nrcB4QsXkQ3887mAgQQEZ61Qkb3SIzACXzrQ5ki4fBOnz1idr2mkpBGpT8 0Z2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709845248; x=1710450048; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=lff4rJyJPlLRFG8AIVxMTTemH3rUkoUmtpj7h9nnRDU=; b=uXpof7Kw2jrNsssMDGTsR1KsKa0pqgjuFvpqgCAx/ZlZUKnpp1HwOlLg11F4cXc/RU gIeE6ogDEmQAxwzXhaxkheqJF3NQ6PSJmwfMmEevEMI4LruBzGsC1KBacCcV9NqBh2Wm i8GmKM/hdrussjVPI/7Q20zoDu6vb4FpIM+MqYrpTX9j9sR4105VgfuJD3+MAdGYe9oj 14XoZ8WQCiKzV37GPX1XeC9uLEUO28KbCp9i5ls5U7pL5T/19wkjmgShVdIlpLxmfAPl cGsL/r+2y+adQO45lLPYUngM/iRn4GyjSwsqTt3BYJ87zUhZIal+1jXtU7rnfujCq60/ mgBQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCU2vZMQvtqIKEED6JfERoeUZPl8ajc2xVtNmmpVngA4RwHi8sh546cOunK13rdWOvOZMexGplP0QK3jbeiM9OP0nWG/azM= X-Gm-Message-State: AOJu0YwN7BkU4kUYOmz7hxNiE3hOqroJjh011fr8u9HqtORCA7oo6WGH 7CKVJFMMsE0zHYiL93Cpu9mOh8flfyZWlR2XS7Dc0JOBucsVuGZX X-Google-Smtp-Source: AGHT+IE8gtqWhoGHj+6Bjg80c+RUOMsi0JLSfogvEp3mzzt/JiAbj7is5yBtQFecrmTEzqUmvAzhiA== X-Received: by 2002:a05:6902:2492:b0:dc6:19ea:9204 with SMTP id ds18-20020a056902249200b00dc619ea9204mr16894882ybb.61.1709845248156; Thu, 07 Mar 2024 13:00:48 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:b20c:0:b0:dcc:4b24:c0df with SMTP id i12-20020a25b20c000000b00dcc4b24c0dfls742835ybj.0.-pod-prod-03-us; Thu, 07 Mar 2024 13:00:46 -0800 (PST) X-Received: by 2002:a81:4c48:0:b0:609:371:342b with SMTP id z69-20020a814c48000000b006090371342bmr3968719ywa.1.1709845246790; Thu, 07 Mar 2024 13:00:46 -0800 (PST) Received: by 2002:a81:a0d5:0:b0:609:de42:876f with SMTP id 00721157ae682-60a00b7fd6dms7b3; Thu, 7 Mar 2024 12:56:15 -0800 (PST) X-Received: by 2002:a05:6902:1009:b0:dbe:387d:a8ef with SMTP id w9-20020a056902100900b00dbe387da8efmr652286ybt.1.1709844974858; Thu, 07 Mar 2024 12:56:14 -0800 (PST) Date: Thu, 7 Mar 2024 12:56:14 -0800 (PST) From: Antoine Riard To: Bitcoin Development Mailing List Message-Id: <38e9e018-eb65-4950-b773-3fc1db218d86n@googlegroups.com> In-Reply-To: <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org> <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> Subject: Re: [bitcoindev] Re: Adding New BIP Editors MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_65818_1495607620.1709844974429" X-Original-Sender: antoine.riard@gmail.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.5 (/) ------=_Part_65818_1495607620.1709844974429 Content-Type: multipart/alternative; boundary="----=_Part_65819_721951046.1709844974429" ------=_Part_65819_721951046.1709844974429 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, > For non-dev triaging, I=20 would suggest we consider testing out the idea with perhaps Seccour I can vet for Seccour. Already met IRL, he's organizing bitcoin meetups somewhere in the world. Best, Antoine Le jeudi 29 f=C3=A9vrier 2024 =C3=A0 16:55:52 UTC, Tim Ruffing a =C3=A9crit= : > On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote: > > The hard part is evaluating=20 > > if the new proposal meets the criteria - which definitely needs dev=20 > > 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.=20 > > Best, > Tim > > > [1] BIP2 says:=20 > "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 "= 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/38e9e018-eb65-4950-b773-3fc1db218d86n%40googlegroups.com. ------=_Part_65819_721951046.1709844974429 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi,

> For non-dev triaging, I=C2=A0
would sugg= est we consider testing out the idea with perhaps Seccour

<= /div>
I can vet for Seccour.
Already met IRL, he's organizing= bitcoin meetups somewhere in the world.

Best,
Antoine

Le jeudi 29 f=C3=A9vrier 2024 =C3=A0 16:55:52 UTC,= Tim Ruffing a =C3=A9crit=C2=A0:
On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:
> The hard part is evaluating=20
> if the new proposal meets the criteria - which definitely needs de= v=20
> skills (mainly for technical soundness).

I'm aware that checking technical soundness is in accordance with B= IP2
[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.=20

Best,
Tim


[1] BIP2 says:=C2=A0
"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.
[...]"

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/38e9e018-eb65-4950-b773-3fc1db218d86n%40googlegroups.com.=
------=_Part_65819_721951046.1709844974429-- ------=_Part_65818_1495607620.1709844974429--