Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64293
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain strojny.net from 46.4.40.248 cause and error)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
In-Reply-To: <CAKOpQSwOBQdUDgww0fvnWsVvk5cUcfzx7yhM-J2WB67tVVaT7g@mail.gmail.com>
Date: Sun, 16 Dec 2012 12:42:33 +0100
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <813193D8-4278-4C52-A5E6-9E26300D4DBC@strojny.net>
References: <EAA1F7DF-374E-4AB4-9ACD-F2C0CC3AE821@strojny.net> <CAKOpQSwOBQdUDgww0fvnWsVvk5cUcfzx7yhM-J2WB67tVVaT7g@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: lars@strojny.net (Lars Strojny)

Hi Kris,

thanks for your response. Just a short note: I'm not in any ways =
officially related to PHP FIG, except that I find it personally to be a =
good initiative. Rest of the answers below.

Am 16.12.2012 um 11:50 schrieb Kris Craig <kris.craig@gmail.com>:

> My one concern with this idea is that it could give the erroneous =
impression that the coding style standards your group advocates are =
endorsed, implicitly or otherwise, by the PHP Group.  There is no =
"official" standard when it comes to spaces vs. tabs and whether to =
place brackets on the same line, for example.  Given how many different =
competing standards there are out there, I fear that we could run the =
risk of showing favoritism by "legitimizing" one standards group but not =
others.

I see what you mean. On the other hand though, a majority of important =
PHP projects are organized there. We (as core developers) can=92t ignore =
what these projects are discussing and I don't think we should. And if =
we have a saying in that, why shouldn=92t we endorse such an initiative.

> Personally, and I'm just speaking for myself here, I think you guys =
over-reached with your PSR-2 style guidelines.  I totally agree with =
your goal of aiding consistency, but these standards are inherently =
arbitrary and it makes me very uneasy to see anyone proclaim that =
such-and-such is the "correct" style of doing something in PHP.  The =
only solution I can see is to create several different style rulesets to =
reflect all the noteworthy styles in popular use.  Of course, then you =
run the risk of undermining the whole consistency goal.

I, again, can=92t speak for PHP FIG, but it seems to me like the survey =
technique worked out pretty well. So PSR-1 and PSR-2 are what most =
projects are doing anyway.

> I wouldn't be adverse to us linking to your project, so long as we do =
the same for any others that crop-up and we make it clear that these =
third-party standards are not officially endorsed by the PHP Group.  I =
also think it's cool if anyone here wants to join your project and =
contribute, so long as that person is representing him/her self.

See point above. We can=92t ignore what major players in the ecosystem =
do and I don't think we should. I would much rather see PHP core have a =
saying in their decisions than standing by the lines and letting things =
happen (which might even be counter-productive for core).

cu,
Lars=