Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » Spam on bugs.php.net »

Spam on bugs.php.net

php.internals

Stas Malyshev

4 years ago
Hi! I notice that we have increased amount of spam coming in to bugs.php.net. I'm not sure if anyone is maintaining it right now - but it'd be nice to have changes to counter that - I see that anti-spam measures exist on some forms but not on adding comments to closed bugs for some reason. And also maybe add ability to delete comments at least for some people, so it can be cleaned up. Thanks,
-- Stas Malyshev smalyshev@gmail.com

Nikita Popov

4 years ago
On Mon, Oct 4, 2021 at 1:20 AM Stanislav Malyshev <smalyshev@gmail.com> wrote:
> Hi! > > I notice that we have increased amount of spam coming in to > bugs.php.net. I'm not sure if anyone is maintaining it right now - but > it'd be nice to have changes to counter that - I see that anti-spam > measures exist on some forms but not on adding comments to closed bugs > for some reason. And also maybe add ability to delete comments at least > for some people, so it can be cleaned up. >
Yes, our spam problem on bugs.php.net is getting worse over time. It's already possible to delete comments (feel free to add yourself to https://github.com/php/web-bugs/blob/master/include/trusted-devs.php to enable it) and I tend to delete a handful on a good day (on one particularly bad day, I had to do a mass delete from the DB). I don't think anyone maintains bugs.php.net -- the spam problem (both link spam and actively malicious users) is part of the motivation to switch to GitHub Issues (which requires authentication and thus can be moderated effectively). Regards, Nikita

Dan Ackroyd

4 years ago
On Mon, Oct 4, 2021 at 1:20 AM Stanislav Malyshev <smalyshev@gmail.com>
> I'm not sure if anyone is maintaining it right now - but > it'd be nice to have changes to counter that
The code for bugs.php.net has a huge amount of tech debt and is a scary thing to touch. On Mon, 4 Oct 2021 at 09:46, Nikita Popov <nikita.ppv@gmail.com> wrote:
> part of the motivation to switch to > GitHub Issues (which requires authentication and thus can be moderated > effectively).
When this was raised before, people seemed to have two concerns: * not having a single linear history of bugs. * having to risk losing a whole load of bug reports if the PHP project ever moves away from using Github. If we: * Close bugs.php.net to all new bugs, except maybe those created by logged in php.net accounts. * Prevent any non-logged in users from commenting. * Mirror any new bugs created on github to bugs.php.net with the appropriate packages etc. * Mirror comments + updates from github to bugs.php.net. that would address both those concerns. Github now supports Templates* for issue forms, these could be setup so users still select "Package affected", "PHP version" etc I'm prepared to do that work...if it sounds like a sensible plan to others and the work wouldn't be wasted. cheers Dan Ack * https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

Rowan Collins

4 years ago
On 04/10/2021 16:29, Dan Ackroyd wrote:
> Github now supports Templates* for issue forms, these could be setup > so users still select "Package affected", "PHP version" etc
More interesting than templates is the overhauled Issues system Github have in beta, where you can define custom fields, then sort and filter by them: https://github.com/features/issues That would fix my main concern, which is that every sizeable project I've seen using Github for bug tracking has dozens of custom labels, and a bunch of bots to keep them all consistent. See for instance the examples which came up last time we had this conversation: https://externals.io/message/114300#114320 Regards,
-- Rowan Tommins [IMSoP]