Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95603
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
To: internals@lists.php.net
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com>
 <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk>
Message-ID: <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com>
Date: Sat, 3 Sep 2016 17:11:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
 composer/pickle
From: rowan.collins@gmail.com (Rowan Collins)

On 03/09/2016 16:02, Lester Caine wrote:
> A starting point for a replacement for PEAR might well be a style guide
> that lays out just how one should build a modern suite of code. My
> stumbling block deciphering owncloud is just how one does work out
> exactly what code has been loaded and from what files. Irrelevant if
> things just work, but when debugging an installation, the code flow
> should be easy to establish!

As mentioned, that's exactly what PHP-FIG is doing; what you're talking 
about is exactly what PSR-1, PSR-2, and PSR-4 describe.

You may not agree with the choices they made, like the people that made 
them, or approve of the processes they used, but all that would be just 
as likely if they happened to be hosted on a sub-domain of php.net.

Regards,

-- 
Rowan Collins
[IMSoP]