> Am 28.10.2014 um 14:50 schrieb Andrea Faulds <a...@ajf.me>:
> 
>> On 28 Oct 2014, at 13:43, Julien Pauli <jpa...@php.net> wrote:
>> 
>> When PHP 5.6 has been released, few weeks/months ago, I explicitely
>> stated Ferenc (RMing 5.6 together with me), that *it is not a normal
>> thing to have an external domain for phpdbg*
>> 
>> This has never happened before, FWIR
>> 
>> Every code that is part of PHP, that is merged into php.net repo ,
>> falls under the PHP licence *and* the PHP process of doing things.
>> 
>> One chance is that today the subject shows to everybody and not only
>> RM wondering about this. Cool.
>> I'm all +1 to merge phpdbg web site content into official php.net 
>> documentation.
>> 
>> Guys, from an external POV, phpdbg seems very strange for people. Why
>> the hell does it have its own github repo and its own website ? This
>> is something that has never been seen for *official* php.net content
>> and our users are asking questions / assuming things.
> 
> Yeah, I agree this is weird. There’s nothing wrong with keeping around the 
> github repo to provide phpdbg for older PHP versions, but the main site 
> should on php.net and it shouldn’t tell the user to go anywhere but php.net.
> --
> Andrea Faulds
> http://ajf.me/ <http://ajf.me/>
Just a tiny update on this subject: we’re working on it.

https://github.com/bwoebi/phpdbg-docs <https://github.com/bwoebi/phpdbg-docs>

is in markdown what’ll be at some point in the official docs, I hope. It may 
take some little time to finish this, but then we’ll probably redirect 
phpdbg.com <http://phpdbg.com/> page to php.net <http://php.net/>.

The phpdbg.com <http://phpdbg.com/> page is currently just horribly outdated 
and a relict from that time before phpdbg was merged into php-src.

Bob Weinand

Reply via email to