Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116447 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 306 invoked from network); 18 Nov 2021 12:36:52 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Nov 2021 12:36:52 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5708E1804C4 for ; Thu, 18 Nov 2021 05:32:19 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, 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-ed1-f44.google.com (mail-ed1-f44.google.com [209.85.208.44]) (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:32:18 -0800 (PST) Received: by mail-ed1-f44.google.com with SMTP id l25so10590289eda.11 for ; Thu, 18 Nov 2021 05:32:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MA2CPoagRgy2glTMueDtnNBsiPcQMOnmVUJ8o/8NogQ=; b=eXMPK/cwUl1sVYVmpAEUB3FrMDDdMpUU9ANkgZumHk6KVFVF/mIBWLH4bCfYFCrcWE 6VkfmV9T2fQlJUshTEXbLU6IMN6VNDR2FHZ7ylZ7ubE0rkrPoLAnfI9YYjZPaZNkUl9d bWIRB/2icRI3y4jfRWWegD6aur7gJD9QwPkDg70SOqJxePmTQRcjHq97wrz5TTCuV9pM iN8G/C0XLLiPUpwEVsCfaXHelfUuV23DTs3oTodp+IWoVhI1lQyhi++vUJ2vMFmFds/Z DlFuDToRGEdd+y5A3rLNbk7GMs9g8U8CM9aJH5xmxdIdXt9fwUUs6mv3gn2yhArZsyP9 WDPQ== 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=MA2CPoagRgy2glTMueDtnNBsiPcQMOnmVUJ8o/8NogQ=; b=DZcjLz6J2wOYuk38NGUKNaFLM7Iiv5ZUmgixQBK5S0jT4UUQ4ny1OqO0xmwOlRHeW5 rzoC/+cCHKq5+ZTowAs/nsah86BwZoMpr57NQEDxS/+U5ebLT1gYWRfxQfgt04P7CYbG /cZ8vAcuD/9hLwejS7gxYaFWMpY8zQfNJGlNhrLahpJtYRF1Q51Up0B3ncKFNRqsd1OB il/C42FBZEZDLtNpUzrU4H3kx8WAWhtTAaO/8kjjo/Ih0tEgR+cMPG3aqFFEVVl0qbpH T+PSdWAdkzrmNP/0WV2lbvIPw5RUZITU4/kov3RWP7VX/DrPeqHEirPwB+hly9VP8YCw x13A== X-Gm-Message-State: AOAM530cLpv00OMtrUziVi3vFf0R9npLf46qCyyvMd13ic0QuXPXY7WU jdNUmpaQ+if+CpGOqYAfa/g01k+zK6KTXxBNSTU= X-Google-Smtp-Source: ABdhPJyu6lgROeQ6v4f4YW1KrleTWCSH5n5BMLaYtQGjnHTy9neE3hP9YiUUCj5HYSV1Q/jO37AmYwKUY8c5I/uYNrA= X-Received: by 2002:aa7:cb41:: with SMTP id w1mr11518112edt.327.1637242337452; Thu, 18 Nov 2021 05:32:17 -0800 (PST) MIME-Version: 1.0 References: <25f35ef5-7f86-9aa3-a069-195a1ed39a91@gmx.de> In-Reply-To: Date: Thu, 18 Nov 2021 14:32:00 +0100 Message-ID: To: Patrick ALLAERT Cc: "Christoph M. Becker" , PHP internals Content-Type: multipart/alternative; boundary="000000000000ef63d105d1102f56" Subject: Re: [PHP-DEV] Re: [RFC] Migrating to GitHub issues From: nikita.ppv@gmail.com (Nikita Popov) --000000000000ef63d105d1102f56 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Nov 18, 2021 at 2:07 PM Patrick ALLAERT wrote: > 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. > The problem with the security mailing list is that it's ephemeral -- someone new can't look at past discussions before they were subscribed. Additionally, it's not possible to make the issue and the whole conversation around it public after the issue has been fixed. Regards, Nikita --000000000000ef63d105d1102f56--