Ability to flag docs comments as outdated or off-topic

Jamison Bryant <[email protected]> Fri, 29 May 2026 10:06:31 -0400
Newsgroups gmane.comp.php.documentation.general
Message-ID <CAP4fLeNqrcGDKpcd9ABjbDDsvY1ghvW8_2AbBqiG17-3BWRkQA@mail.gmail.com>
--000000000000bc2e6a0652f55a74
Content-Type: text/plain; charset="UTF-8"

Hello,

I had an idea to improve the docs that I was discussing with Larry Garfield
and he suggested I bring it to this list.

Something I think could benefit the PHP docs is *the ability for users to
mark comments as out-of-date or off-topic*, when they have clearly gone
stale or contain erroneous info.

Here is a concrete example, see the top comment on this page:

https://www.php.net/manual/en/function.curl-multi-init.php

The most-upvoted comment contains this link:
http://arguments.callee.info/2010/02/21/multiple-curl-requests-with-php/ which
is a DEAD link. Also, all of the comments on that page are nearly a decade
old, with the youngest being posted 8 years ago.

The upvote system alone doesn't fully solve this kind of issue. With so few
comments on the page, even if the broken-link comment were voted to the
bottom, it would still be visible and still mislead readers. A "flag as
outdated" or "flag as off-topic" mechanism would give the community a
lightweight way to surface stale comments for maintainer review.

Warm regards,

Jamison

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

<div dir=3D"auto"><span style=3D"font-family:-apple-system,sans-serif">Hell=
o,</span><br></div><div><div class=3D"gmail_quote gmail_quote_container"><d=
iv><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div d=
ir=3D"ltr"><br></div><div dir=3D"ltr">I had an idea to improve the docs tha=
t I was discussing with Larry Garfield and he suggested=C2=A0I bring it=C2=
=A0to this list.=C2=A0</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Som=
ething I think could benefit the PHP docs is <b>the ability for users to ma=
rk comments as out-of-date or off-topic</b>, when they have clearly gone st=
ale or contain erroneous info.=C2=A0</div><div dir=3D"ltr"><br></div><div d=
ir=3D"ltr">Here is a concrete example, see=C2=A0the top comment on this pag=
e:</div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><a href=3D"https://www.=
php.net/manual/en/function.curl-multi-init.php" target=3D"_blank">https://w=
ww.php.net/manual/en/function.curl-multi-init.php</a>=C2=A0<br></div><div d=
ir=3D"ltr"><br></div><div dir=3D"ltr">The most-upvoted comment contains thi=
s link: <a href=3D"http://arguments.callee.info/2010/02/21/multiple-curl-re=
quests-with-php/" target=3D"_blank">http://arguments.callee.info/2010/02/21=
/multiple-curl-requests-with-php/</a>=C2=A0which is a DEAD link. Also, all =
of the comments on that page are nearly a decade old, with the youngest bei=
ng posted 8 years ago.</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">The=
 upvote system alone doesn&#39;t fully solve this kind of issue. With so fe=
w comments on the page, even if the broken-link comment were voted to the b=
ottom, it would still be visible and still mislead readers.=C2=A0A &quot;fl=
ag as outdated&quot; or &quot;flag as off-topic&quot; mechanism would give =
the community a lightweight way to surface stale comments for maintainer re=
view.</div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><span style=3D"font-=
family:-apple-system,sans-serif">Warm regards,</span><br></div><div dir=3D"=
ltr"><br></div><div dir=3D"ltr">Jamison</div><div dir=3D"ltr"><br></div></d=
iv></div>
</div></div>

--000000000000bc2e6a0652f55a74--