Delivery-date: Thu, 07 Mar 2024 13:00:55 -0800
Sender: bitcoindev@googlegroups.com
Date: Thu, 7 Mar 2024 12:56:14 -0800 (PST)
From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <38e9e018-eb65-4950-b773-3fc1db218d86n@googlegroups.com>
In-Reply-To: <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
 <e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.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"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_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,<div><br /></div><div>&gt; For non-dev triaging, I=C2=A0<br />would sugg=
est we consider testing out the idea with perhaps Seccour</div><div><br /><=
/div><div>I can vet for Seccour.</div><div>Already met IRL, he's organizing=
 bitcoin meetups somewhere in the world.</div><div><br /></div><div>Best,</=
div><div>Antoine<br /><br /></div><div class=3D"gmail_quote"><div dir=3D"au=
to" class=3D"gmail_attr">Le jeudi 29 f=C3=A9vrier 2024 =C3=A0 16:55:52 UTC,=
 Tim Ruffing a =C3=A9crit=C2=A0:<br/></div><blockquote class=3D"gmail_quote=
" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); =
padding-left: 1ex;">On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:
<br>&gt; The hard part is evaluating=20
<br>&gt; if the new proposal meets the criteria - which definitely needs de=
v=20
<br>&gt; skills (mainly for technical soundness).
<br>
<br>I&#39;m aware that checking technical soundness is in accordance with B=
IP2
<br>[1], but I believe that this is one of the main problems of the current
<br>process, and I can imagine that this is what eats the time of editors.
<br>
<br>I&#39;d prefer a BIP process in which the editors merely check that the
<br>proposal is related to the Bitcoin ecosystem and meets some minimal
<br>formal criteria that we already enforce now (i.e., is a full self-
<br>contained document, has the required sections, etc...). This relieves
<br>the editors not just from the effort, but also from the responsibility
<br>to do so. Technical soundness should be evaluated by the audience of a
<br>BIP, not by the editor.=20
<br>
<br>Best,
<br>Tim
<br>
<br>
<br>[1] BIP2 says:=C2=A0
<br>&quot;For each new BIP that comes in an editor does the following:=20
<br>
<br>- Read the BIP to check if it is ready: sound and complete. The ideas
<br>must make technical sense, even if they don&#39;t seem likely to be
<br>accepted.
<br>[...]&quot;
<br></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/38e9e018-eb65-4950-b773-3fc1db218d86n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/38e9e018-eb65-4950-b773-3fc1db218d86n%40googlegroups.com</a>.=
<br />

------=_Part_65819_721951046.1709844974429--

------=_Part_65818_1495607620.1709844974429--