Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64301
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <6604BA43-3688-4C67-A5BE-22E662D0FEF5@strojny.net>
References: <EAA1F7DF-374E-4AB4-9ACD-F2C0CC3AE821@strojny.net>
	<CAEZPtU4C1PibCQbthcgYsdPhqyac6i4rQf+0bHgd3WwESuqCJw@mail.gmail.com>
	<6604BA43-3688-4C67-A5BE-22E662D0FEF5@strojny.net>
Date: Sun, 16 Dec 2012 15:50:08 +0100
Message-ID: <CAEZPtU4gb6ML1LXqpo7tLv-_xNXCHiHm7xFTFLeBUyVMMOna8w@mail.gmail.com>
To: Lars Strojny <lars@strojny.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: pierre.php@gmail.com (Pierre Joye)

hi Lars,

On Sun, Dec 16, 2012 at 1:20 PM, Lars Strojny <lars@strojny.net> wrote:
> Hi Pierre,
>
> Am 16.12.2012 um 13:08 schrieb Pierre Joye <pierre.php@gmail.com>:
>
>> This is something we have seen in the past, "legacy" core developers
>> were not really in sync with the community needs or wishes. That's why
>> we need them to work with the core instead of the other way 'round. It
>> will create more bridges between FIG, the various leading PHP projects
>> and the language development and design.
>
> I couldn=92t agree more, this is and was a problem. Still, the modus oper=
andi of PHP FIG is "people representing projects" and I don=92t see any cor=
e developers participating there (which is obviously nobodies fault). If no=
body else is interested, would anybody object me representing core at PHP F=
IG?

Nobody will object if you join this group, however I do not see how
anyone could represent php.net. The PHP group could be there, but I
don't see that happening anytime soon, not very representative anymore
either.

If there is something that should be implemented in core, coming from
the FIG, then a RFC should be written, discussed and proposed. That's
the right and easy way.


Cheers,
--
Pierre

@pierrejoye