Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128196
Precedence: bulk
MIME-Version: 1.0
References: <b0d97beef95862524b329922522bbefe@bastelstu.be> <26c4161a-1520-4134-8fc1-74dc4a27c463@heigl.org>
In-Reply-To: <26c4161a-1520-4134-8fc1-74dc4a27c463@heigl.org>
Date: Wed, 23 Jul 2025 17:21:45 +0200
Message-ID: <CAMzRQTfVM=uOvA7-3CHV6AcO-Y-xPJV5QuSEueFO1iohMFdhKg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] "Abstain" voting option for RFCs
To: Andreas Heigl <andreas@heigl.org>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000fbcf2b063a9a44ac"
From: volker@tideways-gmbh.com (Volker Dusch)

--000000000000fbcf2b063a9a44ac
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 23, 2025 at 4:30=E2=80=AFPM Andreas Heigl <andreas@heigl.org> w=
rote:

> Adding an Abstain in combination with one of these changes
>
> * Introducing a certain amount of minimum votes (including abstains)
> * Connecting voting karma to actual particiation in votes
>
> sounds very reasonable and worthwile in my opinion.
>
> Adding an abstain just so one can see that one abstained on the other
> hand seems to me rather pointless.
>

There are two immediate benefits for me:

1) I get a couple of messages per week asking about a certain RFC, if I've
seen it, etc. For RFCs where I don't want to vote, it would be nice to
communicate that.

I don't vote on RFCs where I haven't read the implementation and tested
things, so for some topics I choose not to spend the time. Getting asked
about it by multiple people gets draining. Totally a "me" problem, sure,
but something that would be solved by allowing me to communicate that I've
seen the thing, publicly.

2) Looking back, when going over the RFC list, it would be nice to see
which things I've read and engaged with. Not just what I voted on.

And I don't think it makes sense to tie future-looking policy changes into
this; that would require a way bigger scoped discussion.

Cheers,
Volker



--=20
Volker Dusch
Head of Engineering
Tideways GmbH
K=C3=B6nigswinterer Str. 116
53227 Bonn
https://tideways.io/imprint

Sitz der Gesellschaft: Bonn
Gesch=C3=A4ftsf=C3=BChrer: Benjamin Au=C3=9Fenhofer (geb. Eberlei)
Registergericht: Amtsgericht Bonn, HRB 22127

--000000000000fbcf2b063a9a44ac
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jul 23, 2025 at 4:30=E2=80=AFPM A=
ndreas Heigl &lt;<a href=3D"mailto:andreas@heigl.org">andreas@heigl.org</a>=
&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Adding an Abstain in combination with one of these changes<br>
<br>
* Introducing a certain amount of minimum votes (including abstains)<br>
* Connecting voting karma to actual particiation in votes<br>
<br>
sounds very reasonable and worthwile in my opinion.<br>
<br>
Adding an abstain just so one can see that one abstained on the other <br>
hand seems to me rather pointless.<br></blockquote><div><br></div><div clas=
s=3D"gmail_quote"><div>There are two immediate benefits for me:</div><div><=
br></div><div>1) I get a couple of messages per week asking about a certain=
 RFC, if I&#39;ve seen it, etc. For RFCs where I don&#39;t want to vote, it=
 would be nice to communicate that.</div><div><br></div><div>I don&#39;t vo=
te on RFCs where I haven&#39;t read the implementation and tested things, s=
o for some topics I choose not to spend the time. Getting asked about it by=
 multiple people gets draining. Totally a &quot;me&quot; problem, sure, but=
 something that would be solved by allowing me to communicate that I&#39;ve=
 seen the thing, publicly.</div><div><br></div><div>2) Looking back, when g=
oing over the RFC list, it would be nice to see which things I&#39;ve read =
and engaged with. Not just what I voted on.</div></div><div><br></div><div>=
And I don&#39;t think it makes sense to tie future-looking policy changes i=
nto this; that would require a way bigger scoped discussion.</div><div><br>=
</div><div>Cheers,</div><div>Volker</div><font color=3D"#888888"><div><br><=
/div></font><div><br></div></div><div><br></div><span class=3D"gmail_signat=
ure_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div d=
ir=3D"ltr"><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;f=
ont-size:12.8px">Volker Dusch</div><div style=3D"color:rgb(34,34,34);font-f=
amily:arial,sans-serif;font-size:12.8px">Head of Engineering</div><div styl=
e=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px"><di=
v>Tideways GmbH</div><div>K=C3=B6nigswinterer Str. 116</div><div>53227 Bonn=
</div><div><a href=3D"https://tideways.io/imprint" style=3D"color:rgb(17,85=
,204)" target=3D"_blank">https://tideways.io/imprint</a><br></div><div><br>=
</div><div>Sitz der Gesellschaft: Bonn</div><div>Gesch=C3=A4ftsf=C3=BChrer:=
 Benjamin Au=C3=9Fenhofer (geb. Eberlei)</div><div>Registergericht: Amtsger=
icht Bonn, HRB 22127</div></div></div></div></div>

--000000000000fbcf2b063a9a44ac--