Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126173
Date: Tue, 24 Dec 2024 01:06:27 +0000 (GMT)
To: Ben Ramsey <ben@benramsey.com>
cc: PHP Developers Mailing List <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Consolidate Coding Standards Policy Document
In-Reply-To: <CAJOjSBjuY9hDUsGfwjJT8R+onKST-CPgnixf5Nqb6JtcOEiNvg@mail.gmail.com>
Message-ID: <28123d01-c86d-bcbc-eefb-a364eefd64d2@php.net>
References: <025c4f90-7cbf-5f0c-7b1e-30420ded822e@php.net> <CAJOjSBjuY9hDUsGfwjJT8R+onKST-CPgnixf5Nqb6JtcOEiNvg@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
From: derick@php.net (Derick Rethans)

On Sun, 22 Dec 2024, Ben Ramsey wrote:

> On Wed, Dec 18, 2024 at 11:39 Derick Rethans <derick@php.net> wrote:
> 
> > I would like to propose the "Consolidate Coding Standards Policy 
> > Document" RFC, which follows up from the Policy Repository RFC[1]'s 
> > future scope section.
> >
> > This proposal suggests adopting the changes to the Coding Standards 
> > and Naming document, and to integrate the CODING_STANDARDS.md file 
> > from the php-src repository:
> >
> > https://wiki.php.net/rfc/consolidate-coding-standard-policy-document
> >
> > [1] https://wiki.php.net/rfc/policy-repository
> 
> Nitpick:
> 
> It might be more correct to reference BCP 14[1] instead of RFC 2119 
> (which is part of BCP 14).
> 
> [1] https://www.rfc-editor.org/info/bcp14

Either works really? I think that if I would feel inclined to update it, 
wouldn't I just mention RFC 8174, as it updates 2119?

Many (if not most) documents I have seen still reference to RFC 2119 
though...

cheers,
Derick