Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78315
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
Message-ID: <544AA546.1010805@gmail.com>
Date: Fri, 24 Oct 2014 20:15:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAHpw9AfyLRPmD6Yr35WNDju83oozVNeu3WyAGJAygBO2SxisEw@mail.gmail.com>
In-Reply-To: <CAHpw9AfyLRPmD6Yr35WNDju83oozVNeu3WyAGJAygBO2SxisEw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Thoughts on the PHP.net website
From: rowan.collins@gmail.com (Rowan Collins)

Daniel Ribeiro wrote on 24/10/2014 19:52:
> *Disclaimer: *I wanted to bring this discussion inside the internals
> mailing list not only because of the fact that the PHP.net website's source
> code on GitHub doesn't have issues enabled, but especially because I think
> it's part of the PHP environment, just like the spec or the actual C code
> itself.

In case you hadn't seen it already, there's a list of all the mailing 
lists for PHP here: http://php.net/mailing-lists.php

In this case, I would have thought either php.webmaster or php.doc would 
be more appropriate than php.internals, which really does tend to focus 
on the internal implementation of the language, rather than how it used 
or documented.

Meanwhile, I agree with both Kris and Andrea's responses: you need to be 
specific about what problems you propose to fix, and you need to be 
extremely wary of breaking existing functionality just because it's 
"interesting" or "modern".

Regards,
-- 
Rowan Collins
[IMSoP]