Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114302
MIME-Version: 1.0
References: <CAOwTYAtOti3+Tv9Cu5fK6bQ3tjAibRHUWOctnQFfGJyaoQYExw@mail.gmail.com>
In-Reply-To: <CAOwTYAtOti3+Tv9Cu5fK6bQ3tjAibRHUWOctnQFfGJyaoQYExw@mail.gmail.com>
Date: Sun, 9 May 2021 10:17:55 +0300
Message-ID: <CAJW__o11QbvE4jZqT6w=p7HgPsraPYDHkNNuqY3UZBOSJcNJAA@mail.gmail.com>
To: Joe Watkins <krakjoe@php.net>
Cc: PHP internals <internals@lists.php.net>, 
	PHP Release Managers <release-managers@php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Bugsnet
From: kalle@php.net (Kalle Sommer Nielsen)

Den s=C3=B8n. 9. maj 2021 kl. 09.49 skrev Joe Watkins <krakjoe@php.net>:
>
> Morning internals,
>
> We have a spam problem on bugsnet, it's not a new problem. Nikita had to
> waste time deleting 20 odd messages from bugsnet yesterday and this is a
> common, daily occurrence. We clearly don't have time for this.

Big +1 from my side. Much like Joe, I have tried a couple of times
over the years to keep the old bugsnet up to date, but it is simply
not possible to do in its current state -- for example, there is still
open feature requests from 2001 there. One can also open that it can
keep other spammers and abusers away from the platform such as the
ever so recurring abuse of Reindl Harald.

I only think the transition period will be difficult, but it should
iron itself out after a year or so (hopefully) and I assume that by
then, we could perhaps have a better medium or idea of how to deal
with security bugs based on the tools available to us after some time
of using Github on a project of the scale of PHP.

I also fully agree that it is not something we should vote on, it is
one of those things that those who actively work on PHP should decide
(to semi quote Rasmus) -- Let's make it happen.

--=20
regards,

Kalle Sommer Nielsen
kalle@php.net