Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:126174 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id ED3D31A00BD for ; Tue, 24 Dec 2024 19:11:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1735067320; bh=1cyHIJ4C01nUOccgr1X4vvtSDsLY4uF0+MKAz6lrdxk=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=GcasFCwHk2/sXQm8aUd3JGLpM0zYcL5t6vz74aTNw7EXn/V9VOE/8wGtWiFlwxcDA ij2tUowAv17V8LY1QIhKUurExw9WlGTWySQ0t6dWmWBcY6C+u/KFI1QcI2Cl65y8j0 2Z47KZeae0+LIXRhH/zKzJyUaBg8kp3U6+wz/P3RNCSuYWwRN+MbegjKy45XkdsY6D 2AHOIlhm2Es8qB77ZDX4GbbIJGcSZJGyB2zhqHC/mzN/t3rJVRmMbOXPrWOuTvx0/p K68e3m1n6bk1qTVf6wqo7qh5COOEiem42gqlR8t7QwKfdw7rq5jDXcins9JpOXFUgU ZM1t5yO+ekCFA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 18B7C18007E for ; Tue, 24 Dec 2024 19:08:40 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,HTML_MESSAGE, MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 24 Dec 2024 19:08:39 +0000 (UTC) Received: by mail-yb1-f181.google.com with SMTP id 3f1490d57ef6-e3a0acba5feso4268038276.2 for ; Tue, 24 Dec 2024 11:11:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benramsey.com; s=google; t=1735067499; x=1735672299; darn=lists.php.net; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=toVrRuDUSNWG8689ZBrv/btmB+SQhQnFQOpi0JJWXZM=; b=Y6Hj+P88PimtSv9hm8nVBGJqk01h+ozW7f49shbjEYTJZHdhx7cX/D9if3iEUhk/g2 BHnhoCcSR+8SJC2r0Vrcz1nSwhh0jVCx4Xr/f3XUVNtHc351S2d84v8+RMnpHj1CMibX hoAXqyTU1xA7Gu6dmKoi7rAiRE8DLDkMstZeK1JOD6L2CzpWnseq6GzElMMv8k1SGBqX cKi32x9LMcs58G8ybNzpzBOGmwjq3lw7PyeESeXDczWLCkkZMNaUO1mOXLYKtolZUlna IVPZF6puneDKgBtsM6DB8sv31s8E7rVT14ywlwukRGCI4nghFwHDYTjlBgQb0mhVWo6M OxuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735067499; x=1735672299; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=toVrRuDUSNWG8689ZBrv/btmB+SQhQnFQOpi0JJWXZM=; b=ey5BxahU0NTHm8zJvTfKQSGcdpB1r3JaKJIYbByZ6PLrhW1J0ADcCWMMFYpaq6JYKj 9jTsu7uDh4XK/27DHRZgxM6mCde1RByp0z+K441zWF6C/SfPjlzgSOOFD//D4oWciWVL u7WCNMu0xuOIXOBYeOGHUBN0tG7Wegp8Ngi3p4dTGKV2Kf91VgA+afX5CtX+Lb7+8o7T f+EezaGFsWN3nDDN7d+rKI5eLLOeHDfiua44/djSizp4jQ4A+r6zdFTbG3yCLsb82Oai CFtZ0Kd9/sQVBd9OjW+PFHWW154ae9JvF4SbadQdiTZFBHPks5pRaY86+GJ7XojJWzKI SYgQ== X-Gm-Message-State: AOJu0YzF8t2+NSVeTk5JgKEYDgwoHsJ5DINEqPC0+yGlzFcm0wIozOQ7 zV1l/QyHwZD27Migz6pUrruMpJYyiYS3ftIzt30Zw/+f9CFcrCUoFdqEeXF9OTUri14aHTdIz7Q = X-Gm-Gg: ASbGncvhaWW0X51CWWNTOLhV1qkW/vmpTFfIXQDUDkYLkhLJESnRCWfog15Wy/dzI+m ibzHF+rD7P7IIIA2napR7jd1FMG3tyolew6DFk7CBDb7AdCA77Fc+fuDDBcjz41te5MGDU98gqI qm0VfuWFWTdwHVKo158IGM8aZG7vP2AlwxVus40NJInwcuHIRa2+RSFSp3L1/7Vykn2s0uYziqB LV1SNPm8LL2sejek88955a++6ksGlGQu1XFkvHpSk55zfdLo/5jOUNFOJe84XsnasiMtqy3zPaR zIpBTiKWDYqINkuwTaZ68VBtZT03B89manBa9nZYlRvLaSUJ X-Google-Smtp-Source: AGHT+IHUpi1FSQRqLkCYD9PyLfJEdC8Lao/F2q6nd8KNrHBaVBaTovwXHIOTvqJOKBVtPPOqZwxhfw== X-Received: by 2002:a05:690c:6011:b0:6ef:710d:db08 with SMTP id 00721157ae682-6f3f80d910fmr139161907b3.1.1735067499390; Tue, 24 Dec 2024 11:11:39 -0800 (PST) Received: from smtpclient.apple (h96-61-170-179.lvrgtn.broadband.dynamic.tds.net. [96.61.170.179]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6f3e73e7733sm30079127b3.12.2024.12.24.11.11.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Dec 2024 11:11:38 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-ACAC9D06-15E3-48BC-A9A6-BAB03FF68B00 Content-Transfer-Encoding: 7bit Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow Mime-Version: 1.0 (1.0) Subject: Re: [PHP-DEV] [RFC] Consolidate Coding Standards Policy Document Date: Tue, 24 Dec 2024 13:11:27 -0600 Message-ID: References: <28123d01-c86d-bcbc-eefb-a364eefd64d2@php.net> Cc: internals@lists.php.net In-Reply-To: <28123d01-c86d-bcbc-eefb-a364eefd64d2@php.net> To: Derick Rethans X-Mailer: iPhone Mail (22C152) From: ben@benramsey.com (Ben Ramsey) --Apple-Mail-ACAC9D06-15E3-48BC-A9A6-BAB03FF68B00 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Dec 23, 2024, at 19:06, Derick Rethans wrote: >=20 > =EF=BB=BFOn Sun, 22 Dec 2024, Ben Ramsey wrote: >=20 >>> On Wed, Dec 18, 2024 at 11:39 Derick Rethans wrote: >>>=20 >>> 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. >>>=20 >>> 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: >>>=20 >>> https://wiki.php.net/rfc/consolidate-coding-standard-policy-document >>>=20 >>> [1] https://wiki.php.net/rfc/policy-repository >>=20 >> Nitpick: >>=20 >> It might be more correct to reference BCP 14[1] instead of RFC 2119 >> (which is part of BCP 14). >>=20 >> [1] https://www.rfc-editor.org/info/bcp14 >=20 > 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? >=20 > Many (if not most) documents I have seen still reference to RFC 2119 > though... The latest RFCs from the IETF standards track use language like this: > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOUL= D", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in= this document are to be interpreted as described in BCP 14 [RFC2119] [RFC81= 74] when, and only when, they appear in all capitals, as shown here. See here for an example: https://www.rfc-editor.org/rfc/rfc9697.html#section= -1.1 Cheers, Ben --Apple-Mail-ACAC9D06-15E3-48BC-A9A6-BAB03FF68B00 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
= On Dec 23, 2024, at 19:06, Derick Rethans <derick@php.net> wrote:
<= br>
=EF=BB=BFOn Sun, 22 Dec 2024, Ben Ramsey wrote:

On Wed, Dec 18, 2024 at 11:39 Derick Rethans <d= erick@php.net> wrote:

I would like to propose the "Consolidate Coding Standards Policy <= /span>
Document" RFC, which follows up from the Policy Repository= RFC[1]'s
future scope section.
=
This proposal suggests adopting the changes to the Coding Standa= rds
and Naming document, and to integrate the CODING_STAN= DARDS.md file
from the php-src repository:

https://wiki.php.net/rfc/consolidate-coding-standard-= policy-document

[1] https://wiki.php.ne= t/rfc/policy-repository

Nitp= ick:

It might be more correct to referenc= e 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 upda= te it,
wouldn't I just mention RFC 8174, as it updates 2119= ?

Many (if not most) documents I have seen s= till reference to RFC 2119
though...


The latest RFCs from the IETF standards track= use language like this:

The key words "MUST", "MUST NOT", "REQUIRED", "SH= ALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",= "MAY", and "OPTIONAL" in this document are to be interpreted as described i= n BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capital= s, as shown here.


Cheers,
Ben


= --Apple-Mail-ACAC9D06-15E3-48BC-A9A6-BAB03FF68B00--