Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70848
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender)
Message-ID: <52B80477.7050502@gmail.com>
Date: Mon, 23 Dec 2013 09:37:59 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <52B5522A.4040709@lsces.co.uk>	<CAJW__o0wzZsM07jaxXWoH6kjT6oRRnyzfKxiYMM0JK_YeJQ7Pg@mail.gmail.com>	<52B55E6D.6050602@lsces.co.uk> <CAFMT4Nqz=is2w6DmL5gzZ7+8fDyTR1QJfrB0SBj-eQxgL0Jb1w@mail.gmail.com> <52B6B587.4000107@lsces.co.uk>
In-Reply-To: <52B6B587.4000107@lsces.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Censorship in php
From: rowan.collins@gmail.com (Rowan Collins)

Lester Caine wrote (on 22/12/2013):
> But currently the website is promoting a new venue for discussion not 
> hosted by php.net as far as I can tell with no linkage back to the 
> project at all? It requires a separate login and it's the control and 
> administration of this which I am questioning. 

I think the idea is that the feedback area doesn't require any login at 
all, and is not really for co-ordination and planning, just gathering 
feedback. There are many many people who use the php.net website who 
would never think to sign up to a co-ordination list or file a bug, so 
it's a useful way of getting their opinions.

Looking at the open tickets yesterday, it seems to be gathering a range 
of opinions, both positive and negative.

> Like composer and php-fig it seems that the core project is happy to 
> let others take control of what I consider fundamental development 
> decisions

PHP is a programming language, not a framework, and that distinction is 
not new or unique to PHP. Composer is a package management tool, and 
php-fig is a set of coding standards; neither touch on the language 
itself, so for the core developers of the language to presume control of 
them would be unnecessary to the point of arrogance.

The php.net website is, obviously, fairly central to the language, but 
its design is hardly in the same category as, say, whether PHP should 
have a ** operator, so having a separate team with different expertise 
managing it makes perfect sense.

Regards,
-- 
Rowan Collins
[IMSoP]