Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115779
MIME-Version: 1.0
References: <CADK1yXLZzoOjjNcpZ5ZtV9kSNgw4=SW9G74o26eLdAYV5cDzAQ@mail.gmail.com>
In-Reply-To: <CADK1yXLZzoOjjNcpZ5ZtV9kSNgw4=SW9G74o26eLdAYV5cDzAQ@mail.gmail.com>
Date: Mon, 23 Aug 2021 23:07:22 +0200
Message-ID: <CAP=4hCJa_pvxtpfi_+sY8B2pKjv_H2Wqh_4M2F_HrLwMa+1kig@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f80e6e05ca406776"
Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze
From: carusogabriel34@gmail.com (Gabriel Caruso)

--000000000000f80e6e05ca406776
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 23 Aug 2021, 22:49 Deleu, <deleugyn@gmail.com> wrote:

> Hello everyone!
>
> We recently had the Nullable Intersection Types RFC process in an
> unconventional way starting a new RFC post feature freeze. If memory serv=
es
> me right, another similar incident happened with the Attributes RFC which
> had a syntax that could not be implemented without a secondary RFC [1] an=
d
> went through a secondary RFC which proposed a different syntax [2].
>
> [1] https://wiki.php.net/rfc/namespaced_names_as_token
> [2] https://wiki.php.net/rfc/attributes_v2
>
> I would like to gather opinion on a potential Policy RFC that would defin=
e
> some guidelines for such a process. As Nikita pointed out [3], the abilit=
y
> to refine new features is both important for the developer and undocument=
ed
> for the PHP Project.
>
> In order to not be empty-handed, I started a gist that can be seen as the
> starting point for this discussion, available at
> https://gist.github.com/deleugpn/9d0e285f13f0b4fdcfc1d650b20c3105.
>
> Generally speaking, I'm first looking for feedback on whether this is
> something that deserves attention and an RFC or is it so rare that it's
> fine to leave it unchanged. If there is interest in moving forward, I wou=
ld
> then also be interested in suggestions on things that should be
> included/excluded in the RFC.
>
> Marco Aur=C3=A9lio Deleu


>
> Thank you for being this one up, and yes: we should be a little bit more
> strict with stuff coming in, post feature freeze period!


In PHP 8.0, Sara and I had the same problem :(

--000000000000f80e6e05ca406776--