Newsgroups: php.internals,php.webmaster Path: news.php.net Xref: news.php.net php.internals:116217 php.webmaster:29634 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28671 invoked from network); 4 Oct 2021 14:45:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Oct 2021 14:45:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8368F18053B for ; Mon, 4 Oct 2021 08:29:25 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vs1-f46.google.com (mail-vs1-f46.google.com [209.85.217.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 4 Oct 2021 08:29:25 -0700 (PDT) Received: by mail-vs1-f46.google.com with SMTP id g10so2524649vsb.8 for ; Mon, 04 Oct 2021 08:29:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bb0pLbKRYHSFowOCz2xsLEZIXsZma8aEH1Xqz36TBhE=; b=1JDni+GsOHHqraR9ERKrwIDiLw9GR+uJC3p3+FSXK0tVsjkwwaPMdysWI23QMnbDMr zUz0SiGiZuwWSUf0em/qLCm1sz933jYj2HUWivZu/OYhy91SkN7AxE9ZsPElRloYa+IL +ArDUZmGBlLflS/9usZw5gGQ38CcyfC74E3aIc5+oYn8fLZyepvER7ohtIQE9ljetmYb LXbq4Wxt9/c8gnZPxV/z5GIbszy6g4XKkE3wuALWTbuJqlori5fKTSbVJ1asHhS7cboW 3nPKToANEUhqogXlgRczHuYUlbLMzxvkKsbA2VAaISHE11DMTs/mkrAL/JwLF6upSIXi OYLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bb0pLbKRYHSFowOCz2xsLEZIXsZma8aEH1Xqz36TBhE=; b=j9b3kP+XfJ8IaWkOsmdoaC6y06FV5JTdXEk50j+rW+2nusz8rzwR3yRqSPOKnVYA3q hhSxan3faTCQUhUEo5XUVFIecwhG9Q+APHcsQkcCSEH+Dt5Z0eIuUenw73m4HgcQVavN jgXIXjxcD4JD2iNMeYDoNJ+LbrW7K3FFwhYQmI8+jEaT93KWgQgq5d1uAJMqHxf9qeU5 8PeRJDm+aDWXtTX7l7txWp4XNRI86TlBOncezySHkuo5DoRaMlyUPYZvGDfxqLynGGX8 o5H2JvczhKg29YLHxO+m8gYdr9pwGL2oqZOsZVw4ky/nV3Kr8r9OI0YS+46o2WaiV+IR S0kA== X-Gm-Message-State: AOAM530wQxFskQ5E+dYaSTPcJ19qFRcXJG3ZeEIcnbDHVKf3UZXumqBZ 6VWL8P2su8DVSU7LS8fXdXR4vSG9q63nxXrTikKb6A== X-Google-Smtp-Source: ABdhPJyU8RPe+f7k6pr+5TdY7gJ4lv/hzMC+60ZxdVoLEhsxwDLeQD34Xg13I1oO50x7elT+2oS03Or0IkkSBaJlWfk= X-Received: by 2002:a67:c088:: with SMTP id x8mr13185458vsi.45.1633361364426; Mon, 04 Oct 2021 08:29:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 4 Oct 2021 16:29:11 +0100 Message-ID: To: Nikita Popov Cc: Stanislav Malyshev , PHP Internals , php-webmaster ML Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Spam on bugs.php.net From: Danack@basereality.com (Dan Ackroyd) On Mon, Oct 4, 2021 at 1:20 AM Stanislav Malyshev > 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 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