Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75938
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <53CF7DFC.7030203@lsces.co.uk>
Date: Wed, 23 Jul 2014 10:18:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAESVnVq5P26Yi=w1yF3ETBEPe+PwJdEAuJ3-8Yw5vsQBy7ofDw@mail.gmail.com> <53CEE5A4.6080701@sugarcrm.com>
In-Reply-To: <53CEE5A4.6080701@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP Language Specification
From: lester@lsces.co.uk (Lester Caine)

On 22/07/14 23:28, Stas Malyshev wrote:
> I would propose choosing some collaborative platform for managing it,
> something like Google Docs (suggestions about best platform ever for
> that are welcome :) so that people could comment on specific parts and
> keep track of what is the current state and what has been discussed.
> 
> Alternatively, we could do a wiki maybe but the problem there is that it
> is hard to export (unless anybody knows wiki setups that can be easily
> exported into single document).

This is another can of worms, and perhaps an example of why the current
php website structure is such a problem :(

Using different tools for different areas of the website, laying off
elements to third party services and then relying on other third party
services to provide a usable 'website' search ... which only partially
works when you select a different language.

Moving elements of the website into a more coherent whole is yet another
project that is long overdue and since we are DESIGNING the very
software that creates these facilities, it should not be difficult?

The current user manual should be a wiki with sections for rfc
management, adding comments, managing history of changes and so on. The
Language Specification is simply an extension of that as is the sort of
internal code documentation we are currently asking for.

DokuWiki is sort of functional, but as has been indicated, cloning a
copy of the history on another machine is not possible! Keeping the
material in a DVCS sort of works, but these are not designed for
document maintenance? I keep looking at importing the whole lot into a
database which can the be provided as a daily backup, which adds the
ability to search both current views of the material and back through
history for changes. Moving everything into a framework which can manage
both translations and integral cross linking, and gives a single front
end to everything on the website ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk