Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99491 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92859 invoked from network); 11 Jun 2017 06:59:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jun 2017 06:59:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 77.244.243.82 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 77.244.243.82 mx101.easyname.com Received: from [77.244.243.82] ([77.244.243.82:33988] helo=mx101.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 25/6B-01593-43AEC395 for ; Sun, 11 Jun 2017 02:59:01 -0400 Received: from cable-81-173-132-37.netcologne.de ([81.173.132.37] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1dJwpq-0006Nx-U9; Sun, 11 Jun 2017 06:58:56 +0000 References: <28ca1459-ceb4-872f-62a8-f0616f229ddb@fleshgrinder.com> <1975642a-957c-7946-0903-ab7afe46e1f4@fleshgrinder.com> To: Dan Ackroyd , php-internals Message-ID: Date: Sun, 11 Jun 2017 08:58:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5JCvDt5gTPemDEI1p5SBQRrAjXPKc0KPq" X-DNSBL-PBLSPAMHAUS: YES Subject: Re: [PHP-DEV] [RFC] [Discussion] Class Naming From: php@fleshgrinder.com (Fleshgrinder) --5JCvDt5gTPemDEI1p5SBQRrAjXPKc0KPq Content-Type: multipart/mixed; boundary="78qTFsKWwjpI9IacQsLIaSG8DXiFUc0jr"; protected-headers="v1" From: Fleshgrinder To: Dan Ackroyd , php-internals Message-ID: Subject: Re: [PHP-DEV] [RFC] [Discussion] Class Naming References: <28ca1459-ceb4-872f-62a8-f0616f229ddb@fleshgrinder.com> <1975642a-957c-7946-0903-ab7afe46e1f4@fleshgrinder.com> In-Reply-To: --78qTFsKWwjpI9IacQsLIaSG8DXiFUc0jr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/11/2017 12:35 AM, Dan Ackroyd wrote: > On 10 June 2017 at 21:57, Fleshgrinder wrote: >> >> This RFC is only >=20 > "When collaborating with others =E2=80=93 especially when designers and= > programmers are part of the mix =E2=80=93 watch out for these dirty fou= r > letter words: Need Must Can=E2=80=99t Easy Just Only Fast" > https://signalvnoise.com/posts/439-four-letter-words >=20 > It's actually setting a rule for a project, that has gone 23 years > without needing that rule, which doesn't sound completely trivial. >=20 It is a clarification of an existing rule. A rule that already exists for 16 years. On 6/11/2017 12:35 AM, Dan Ackroyd wrote: >> Hence, one week seems sensible. >=20 > It doesn't seem sensible to me. >=20 > The minimum discussion period is for when there is an urgent problem > that ought to be addressed but there is disagreement about the best > way to resolve it. >=20 The existing rules are pretty explicit about their intend and applicability. Not sure where this is coming from. On 6/11/2017 12:35 AM, Dan Ackroyd wrote: > We should be taking longer periods to think about committing to coding > standards, rather than just the bare minimum. >=20 Here I agree in general, but the RFC's question is trivial and its choices are obvious. That is why I believe that it does not require much though. On 6/11/2017 12:35 AM, Dan Ackroyd wrote: > People (in general) have better things to do than read internals. Some > of the discussions over the past couple of weeks have been even more > demotivating than usual, which is probably one of the reasons why > people haven't responded yet. >=20 >> We can of course wait if there is a serious issue. >=20 > We can of course wait anyway. >=20 > This RFC isn't going to affect 7.2, so the first release it will > affect is 7.3 - so we could wait 12 months to vote before it became > critical. >=20 > cheers > Dan >=20 Seems like people have serious issues, so let's wait. --=20 Richard "Fleshgrinder" Fussenegger --78qTFsKWwjpI9IacQsLIaSG8DXiFUc0jr-- --5JCvDt5gTPemDEI1p5SBQRrAjXPKc0KPq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJZPOorAAoJEOKkKcqFPVVrzZgP/jyBS+pogF379N/D5MmzRMuw RbaiZxc8mRbYC93iasI/swN9wIFxw4OjHvw/AQ/Pm8q4yOWb9VuuORuAiPcIPXBa U/VmjQRV+g0TjqP93y89KyMtYdscrOMfiWQ92zx3qB76Sl4wBzwHiBDdv4BEuv9m lNwKed03B1BCu4y3pEaNApnH1uK4wYPkfT33Bw5Nk4i9D4Fah8cKboe7koW6rz63 oobSjFVy0TQ+fOi/P5yvSbSoaBn0igQunk9NdmmY7UaBQK+gS1aR42dKsdamlnGm MHNpLPG46+4A3xrKjYr7+C66kuA2hTR2fFJ6xMRgBYGYn1W+zVoLznz5+x5NqGKf bv8heDOab8KjOlecEwCXd2SMZNGTXLKzyyhpWP7bDWon3fTZuM6i2byKjipWfOOk GvfJn0B70yOcPAmpM20JntzOWBxx8tOqy46hVzaJCfaHggHDTgLQ2xnik7Y76FDV L/hNGfnSwgXiHzuZXO64ve90b0DfEGQ3MIV6c6rVB9SNyZIimHFb5iFDkvYvvJC9 0dWKAWlDQ/D2jcD6S4Qxr0jeRJbs3VWeHSXOAsvczAteXBbmh5HfFZACG1583jvz Ev+XhbNoTfJ7a6HOvy95aDk2VRZM5eMEq0RoNr7SR/bie6QgFvSSVZLXBhF5beIV ebjUxRtKJWZEqHYLO4tJ =JdkT -----END PGP SIGNATURE----- --5JCvDt5gTPemDEI1p5SBQRrAjXPKc0KPq--