Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116446 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97987 invoked from network); 18 Nov 2021 12:12:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Nov 2021 12:12:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 620141804B5 for ; Thu, 18 Nov 2021 05:07:49 -0800 (PST) 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.5 required=5.0 tests=BAYES_20, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS 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-ua1-f53.google.com (mail-ua1-f53.google.com [209.85.222.53]) (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 ; Thu, 18 Nov 2021 05:07:49 -0800 (PST) Received: by mail-ua1-f53.google.com with SMTP id l24so13537730uak.2 for ; Thu, 18 Nov 2021 05:07:48 -0800 (PST) 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:content-transfer-encoding; bh=j2ZiDHJo6Vbo73NU6iqzVtkaJmZU44fAwHe4X7eGiO4=; b=EAOrsIo2hoKrRaSG/mla+iVCYEnoYt5FH2H+3nKCcMLMB41S3BOBQtunntttGTlEsc mpWa+K6P2p8szHnLDoGE8zi0g5wX8to6x58yzqab+Wg8n8EzagwE5dBtPS4mpqEXgKN0 h6/10pKk4Qs67YNjLTEOWe3sHev98GUh8dDQKbl+0G6rH3da7caiA5K7gPipC0V5J1zZ tVEBWn86pNAp+xDaPzumtYE8W22XHgOi6ffpTViYhkKyXCt2g57H7XTJZw4O1Z7qJ2Hl oDkP7n+uznLNmWRTQTqDqT6QN33fQY9+QxzbQqO4gC5PKWdP4GMGDtE07MXQrH6QMaKG RrIA== X-Gm-Message-State: AOAM530/CK9u/ysEqPYoy7sOI4/85S+k7t2rOciIaMgKG07DlWCX5OkU WO6aHT6l766lEkz85/GRfcL2POVq/wpIaKc9EA== X-Google-Smtp-Source: ABdhPJyOv8hbzV6fHcmrvc98+td8+HQvUX9GvIQeECv13NMEEBsFhp4R2IRjH6UvVBbO2CZO3qg1NJC8tUANfWjlzXQ= X-Received: by 2002:ab0:7041:: with SMTP id v1mr36198324ual.95.1637240867038; Thu, 18 Nov 2021 05:07:47 -0800 (PST) MIME-Version: 1.0 References: <25f35ef5-7f86-9aa3-a069-195a1ed39a91@gmx.de> In-Reply-To: <25f35ef5-7f86-9aa3-a069-195a1ed39a91@gmx.de> Date: Thu, 18 Nov 2021 14:07:36 +0100 Message-ID: To: "Christoph M. Becker" Cc: Nikita Popov , =?UTF-8?Q?Bj=C3=B6rn_Larsson?= , PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: [RFC] Migrating to GitHub issues From: patrickallaert@php.net (Patrick ALLAERT) Le mer. 17 nov. 2021 =C3=A0 13:30, Christoph M. Becker = a =C3=A9crit : > Right. An alternative might be to let users report security issues to > the security mailing list, where, if the issue turns out not to be a > security issue, the reporter could still be asked to submit a GH issue > about the bug. In that case it might be useful to add more devs to the > security mailing list. I was thinking about the same. Can't we work with security issues with mailing list *only*? It doesn't feel optimal to keep bugs.php.net active for just security ones. I miss seeing the motivation for it. Patrick