MIME-Version: 1.0
References: <202104230209.05373.luke@dashjr.org>
In-Reply-To: <202104230209.05373.luke@dashjr.org>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Fri, 23 Apr 2021 11:34:53 -0400
Message-ID: <CALZpt+Hz3jFnA8z1w6yictdHWnnKReMK+6eEHg_jUZ7==xNZzQ@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000004d327c05c0a58af3"
Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm
Precedence: list

--0000000000004d327c05c0a58af3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Luke,

For the records and the subscribers of this list not following
#bitcoin-core-dev, this mail follows a discussion which did happen during
yesterday irc meetings.
Logs here : http://gnusha.org/bitcoin-core-dev/2021-04-22.log

I'll reiterate my opinion expressed during the meeting. If this proposal to
extend the bip editorship membership doesn't satisfy parties involved or
anyone in the community, I'm strongly opposed to have the matter sliced by
admins of the Bitcoin github org. I believe that defect or uncertainty in
the BIP Process shouldn't be solved by GH janitorial roles and I think
their roles don't bestow to intervene in case of loopholes. Further, you
have far more contributors involved in the BIP Process rather than only
Bitcoin Core ones. FWIW, such precedent merits would be quite similar to
lobby directly GH staff...

Unless we harm Bitcoin users by not acting, I think we should always be
respectful of procedural forms. And in the lack of such forms, stay patient
until a solution satisfy everyone.

I would recommend the BIP editorship, once extended or not, to move in its
own repository in the future.

Cheers,
Antoine


Le jeu. 22 avr. 2021 =C3=A0 22:09, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> a =C3=A9crit :

> Unless there are objections, I intend to add Kalle Alm as a BIP editor to
> assist in merging PRs into the bips git repo.
>
> Since there is no explicit process to adding BIP editors, IMO it should b=
e
> fine to use BIP 2's Process BIP progression:
>
> > A process BIP may change status from Draft to Active when it achieves
> > rough consensus on the mailing list. Such a proposal is said to have
> > rough consensus if it has been open to discussion on the development
> > mailing list for at least one month, and no person maintains any
> > unaddressed substantiated objections to it.
>
> A Process BIP could be opened for each new editor, but IMO that is
> unnecessary. If anyone feels there is a need for a new Process BIP, we ca=
n
> go
> that route, but there is prior precedent for BIP editors appointing new
> BIP
> editors, so I think this should be fine.
>
> Please speak up soon if you disagree.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--0000000000004d327c05c0a58af3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Luke,<br><br></div>For the records and t=
he subscribers of this list not following #bitcoin-core-dev, this mail foll=
ows a discussion which did happen during yesterday irc meetings.<br>Logs he=
re : <a href=3D"http://gnusha.org/bitcoin-core-dev/2021-04-22.log">http://g=
nusha.org/bitcoin-core-dev/2021-04-22.log</a><br><br></div>I&#39;ll reitera=
te my opinion expressed during the meeting. If this proposal to extend the =
bip editorship membership doesn&#39;t satisfy parties involved or anyone in=
 the community, I&#39;m strongly opposed to have the matter sliced by admin=
s of the Bitcoin github org. I believe that defect or uncertainty in the BI=
P Process shouldn&#39;t be solved by GH janitorial roles and I think their =
roles don&#39;t bestow to intervene in case of loopholes. Further, you have=
 far more contributors involved in the BIP Process rather than only Bitcoin=
 Core ones. FWIW, such precedent merits would be quite similar to lobby dir=
ectly GH staff...<br><br></div><div>Unless we harm Bitcoin users by not act=
ing, I think we should always be respectful of procedural forms. And in the=
 lack of such forms, stay patient until a solution satisfy everyone.<br><br=
></div><div>I would recommend the BIP editorship, once extended or not, to =
move in its own repository in the future.<br><br></div><div>Cheers,<br></di=
v><div>Antoine<br></div><div><br><br><br></div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0jeu. 22 avr. 2021 =
=C3=A0=C2=A022:09, Luke Dashjr via bitcoin-dev &lt;<a href=3D"mailto:bitcoi=
n-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&=
gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">Unless there are objections, I intend to add Kalle Alm as a BIP edi=
tor to <br>
assist in merging PRs into the bips git repo.<br>
<br>
Since there is no explicit process to adding BIP editors, IMO it should be =
<br>
fine to use BIP 2&#39;s Process BIP progression:<br>
<br>
&gt; A process BIP may change status from Draft to Active when it achieves<=
br>
&gt; rough consensus on the mailing list. Such a proposal is said to have<b=
r>
&gt; rough consensus if it has been open to discussion on the development<b=
r>
&gt; mailing list for at least one month, and no person maintains any<br>
&gt; unaddressed substantiated objections to it.<br>
<br>
A Process BIP could be opened for each new editor, but IMO that is <br>
unnecessary. If anyone feels there is a need for a new Process BIP, we can =
go <br>
that route, but there is prior precedent for BIP editors appointing new BIP=
 <br>
editors, so I think this should be fine.<br>
<br>
Please speak up soon if you disagree.<br>
<br>
Luke<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000004d327c05c0a58af3--