Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121172
MIME-Version: 1.0
References: <79C36252-921C-4D4C-9B1F-286DD5ABCBCA@php.net> <6515fc31.810a0220.69302.df44SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <6515fc31.810a0220.69302.df44SMTPIN_ADDED_MISSING@mx.google.com>
Date: Fri, 29 Sep 2023 08:42:25 -0500
Message-ID: <CAESVnVq_FaEnjMtya89iG4MVnbF3DHdnX-_AUxod+XcRRMqK6Q@mail.gmail.com>
To: Ben Ramsey <ramsey@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000e3132806067f98e6"
Subject: Re: [PHP-DEV] Add security.txt file to php.net
From: pollita@php.net (Sara Golemon)

--000000000000e3132806067f98e6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 28, 2023 at 5:20=E2=80=AFPM Ben Ramsey <ramsey@php.net> wrote:
> I've added documentation inline in the security.txt file
>

To add some nitpicky bikeshedding, I'd put those instructions elsewhere
(maybe php-src:docs/release-process.md ?) and only have a single line in
the security.txt file referring out to that.  The focus of the security.txt
file should BE the metadata.

+1 on the concept, and I do like the idea of making it part of the new
branch release process as well as having one of the new RMs being the ones
to sign it.

-Sara

--000000000000e3132806067f98e6--