FAQ
Hi

I am wanting to update the install docs for Windows.

Currently, most of the info on those docs is for old versions of Windows
and is no longer relavent. It makes it hard to clearly communicate current
information, so I would like to get rid of it.

Rather that removing it, I would like to move it to a new folder,
install/windows/legacy and then create new docs in install/windows. That
info may still be useful to some users.


However, when I try to create the folder install/windows/legacy in the
docbook editor (edit.php.net), I get a popup titled `Forbidden` with no
msg, only an ok button.

Maybe I have permission to edit files, but no permission to create a folder.

Would someone create the folder install/windows/legacy for me, or else give
me the permission to do it: my username is `mattficken`.


Thanks
-M

Search Discussions

  • Christoph Becker at Mar 24, 2016 at 7:28 pm

    On 23.03.2016 at 08:19, Matt Ficken wrote:

    I am wanting to update the install docs for Windows.

    Currently, most of the info on those docs is for old versions of Windows
    and is no longer relavent. It makes it hard to clearly communicate current
    information, so I would like to get rid of it. +1
    Rather that removing it, I would like to move it to a new folder,
    install/windows/legacy and then create new docs in install/windows. That
    info may still be useful to some users.
    If that documentation will be moved, I strongly suggest to also move all
    existing translations. That would have to be done by somebody with
    general doc karma (I have only doc/en and doc/de).

    Anyhow, please consider that some of the information is duplicated in
    install.txt in php-src[1]. We should consider to get rid of this
    duplication if possible. At least we should try to keep both documents
    in sync.

    [1] <https://github.com/php/php-src/blob/master/win32/install.txt>

    --
    Christoph M. Becker
  • Josh Nemec at Mar 24, 2016 at 7:40 pm
    Please remove me from this list.
    On Thu, Mar 24, 2016 at 3:28 PM, Christoph Becker wrote:
    On 23.03.2016 at 08:19, Matt Ficken wrote:

    I am wanting to update the install docs for Windows.

    Currently, most of the info on those docs is for old versions of Windows
    and is no longer relavent. It makes it hard to clearly communicate current
    information, so I would like to get rid of it. +1
    Rather that removing it, I would like to move it to a new folder,
    install/windows/legacy and then create new docs in install/windows. That
    info may still be useful to some users.
    If that documentation will be moved, I strongly suggest to also move all
    existing translations. That would have to be done by somebody with
    general doc karma (I have only doc/en and doc/de).

    Anyhow, please consider that some of the information is duplicated in
    install.txt in php-src[1]. We should consider to get rid of this
    duplication if possible. At least we should try to keep both documents
    in sync.

    [1] <https://github.com/php/php-src/blob/master/win32/install.txt>

    --
    Christoph M. Becker
  • Christoph Becker at Mar 25, 2016 at 9:57 am

    Josh Nemec wrote:

    Please remove me from this list.
    You are supposed to be able to unsubscribe via the form at the bottom of
    <http://php.net/mailing-lists.php>. :)

    --
    Christoph M. Becker
  • Matt Ficken at Mar 24, 2016 at 8:17 pm
    I can update win32/install.txt in php-src. Good point.

    Good point about other languages too. Same outdated info for
    install/windows is in all languages and eventually should be updated.

    I can't update that document in all languages(just en, and maybe es or fr).

    For now, can we move just the `en` copy of install/windows to
    install/windows/legacy ? Then I can update that document

    Then, when others are ready to do the translation, they can update it for
    de, ru, etc...


    I don't have karma to do move those files for any language.

    On Thu, Mar 24, 2016 at 12:28 PM, Christoph Becker wrote:
    On 23.03.2016 at 08:19, Matt Ficken wrote:

    I am wanting to update the install docs for Windows.

    Currently, most of the info on those docs is for old versions of Windows
    and is no longer relavent. It makes it hard to clearly communicate current
    information, so I would like to get rid of it. +1
    Rather that removing it, I would like to move it to a new folder,
    install/windows/legacy and then create new docs in install/windows. That
    info may still be useful to some users.
    If that documentation will be moved, I strongly suggest to also move all
    existing translations. That would have to be done by somebody with
    general doc karma (I have only doc/en and doc/de).

    Anyhow, please consider that some of the information is duplicated in
    install.txt in php-src[1]. We should consider to get rid of this
    duplication if possible. At least we should try to keep both documents
    in sync.

    [1] <https://github.com/php/php-src/blob/master/win32/install.txt>

    --
    Christoph M. Becker
  • Christoph Becker at Mar 25, 2016 at 10:16 am

    On 24.03.2016 at 21:17, Matt Ficken wrote:

    I can update win32/install.txt in php-src. Good point.

    Good point about other languages too. Same outdated info for
    install/windows is in all languages and eventually should be updated.

    I can't update that document in all languages(just en, and maybe es or fr).

    For now, can we move just the `en` copy of install/windows to
    install/windows/legacy ? Then I can update that document

    Then, when others are ready to do the translation, they can update it for
    de, ru, etc...
    I'm note sure whether this is a good idea. Moving the en docs to a new
    folder and updating the old docs in place will cause additional
    translation work, if the translators are not aware of this change. The
    doc system[1] will report the install/windows/*.xml docs to be
    out-dated, so a translator would have to update them (what has to be
    done anyway – no problem here). However, the doc system will also tag
    the install/windows/legacy/*.xml docs as new files, and a translator
    might translate them *anew* (not being aware that those files only had
    moved).

    The best solution with regard to translations would be to *copy* all
    files under install/windows/ to the new folder. This way only those
    files that really will change will be tagged as being out-dated in the
    other languages.

    Anyhow, I have created en/install/windows/legacy/ right now.

    [1] <http://doc.php.net/> and <https://edit.php.net/>

    --
    Christoph M. Becker
  • Matt Ficken at Apr 5, 2016 at 5:09 am
    In the PHP Online Docbook Editor, I tried to move the old files to
    install/windows/legacy, which it appears to do, the file tree is updated
    and there is no error message. However, reloading the tree listing of
    files, the changes aren't made.

    I have created a new install/windows/index.xml. However, its currently
    modifying the existing index.xml which I don't want to do. I want to move
    the existing index.xml to legacy.


    Would someone with the karma or access to the repository move those files
    to install/windows/legacy?

    I have a few more changes I want to add to index.xml and I want to add
    Troubleshooting and Recommended Practices pages, but I don't want to do
    that until that is cleared up (and I do think its worth all this trouble to
    keep that legacy info).


    What causes someone to run the PHD docbook rendering system? and release
    the updated html files onto php.net?

    I can't find information about that. For other parts of php.net, I can just
    commit to git repository and wait 20 minutes. For win32/install.txt, I can
    just update php-src.git repository.

    The few changes I want to make, and changes to Troubleshooting page over
    time, what is involved in getting those changes onto php.net?


    Regards
    -M



    On Fri, Mar 25, 2016 at 3:16 AM, Christoph Becker wrote:
    On 24.03.2016 at 21:17, Matt Ficken wrote:

    I can update win32/install.txt in php-src. Good point.

    Good point about other languages too. Same outdated info for
    install/windows is in all languages and eventually should be updated.

    I can't update that document in all languages(just en, and maybe es or fr).
    For now, can we move just the `en` copy of install/windows to
    install/windows/legacy ? Then I can update that document

    Then, when others are ready to do the translation, they can update it for
    de, ru, etc...
    I'm note sure whether this is a good idea. Moving the en docs to a new
    folder and updating the old docs in place will cause additional
    translation work, if the translators are not aware of this change. The
    doc system[1] will report the install/windows/*.xml docs to be
    out-dated, so a translator would have to update them (what has to be
    done anyway – no problem here). However, the doc system will also tag
    the install/windows/legacy/*.xml docs as new files, and a translator
    might translate them *anew* (not being aware that those files only had
    moved).

    The best solution with regard to translations would be to *copy* all
    files under install/windows/ to the new folder. This way only those
    files that really will change will be tagged as being out-dated in the
    other languages.

    Anyhow, I have created en/install/windows/legacy/ right now.

    [1] <http://doc.php.net/> and <https://edit.php.net/>

    --
    Christoph M. Becker
  • Pasindu De Silva at Apr 5, 2016 at 5:21 am
    HI Matt
    Did you refer http://doc.php.net/tutorial/

    +1
    On Tue, Apr 5, 2016 at 1:09 PM, Matt Ficken wrote:

    In the PHP Online Docbook Editor, I tried to move the old files to
    install/windows/legacy, which it appears to do, the file tree is updated
    and there is no error message. However, reloading the tree listing of
    files, the changes aren't made.

    I have created a new install/windows/index.xml. However, its currently
    modifying the existing index.xml which I don't want to do. I want to move
    the existing index.xml to legacy.


    Would someone with the karma or access to the repository move those files
    to install/windows/legacy?

    I have a few more changes I want to add to index.xml and I want to add
    Troubleshooting and Recommended Practices pages, but I don't want to do
    that until that is cleared up (and I do think its worth all this trouble to
    keep that legacy info).


    What causes someone to run the PHD docbook rendering system? and release
    the updated html files onto php.net?

    I can't find information about that. For other parts of php.net, I can
    just commit to git repository and wait 20 minutes. For win32/install.txt, I
    can just update php-src.git repository.

    The few changes I want to make, and changes to Troubleshooting page over
    time, what is involved in getting those changes onto php.net?


    Regards
    -M



    On Fri, Mar 25, 2016 at 3:16 AM, Christoph Becker wrote:
    On 24.03.2016 at 21:17, Matt Ficken wrote:

    I can update win32/install.txt in php-src. Good point.

    Good point about other languages too. Same outdated info for
    install/windows is in all languages and eventually should be updated.

    I can't update that document in all languages(just en, and maybe es or fr).
    For now, can we move just the `en` copy of install/windows to
    install/windows/legacy ? Then I can update that document

    Then, when others are ready to do the translation, they can update it for
    de, ru, etc...
    I'm note sure whether this is a good idea. Moving the en docs to a new
    folder and updating the old docs in place will cause additional
    translation work, if the translators are not aware of this change. The
    doc system[1] will report the install/windows/*.xml docs to be
    out-dated, so a translator would have to update them (what has to be
    done anyway – no problem here). However, the doc system will also tag
    the install/windows/legacy/*.xml docs as new files, and a translator
    might translate them *anew* (not being aware that those files only had
    moved).

    The best solution with regard to translations would be to *copy* all
    files under install/windows/ to the new folder. This way only those
    files that really will change will be tagged as being out-dated in the
    other languages.

    Anyhow, I have created en/install/windows/legacy/ right now.

    [1] <http://doc.php.net/> and <https://edit.php.net/>

    --
    Christoph M. Becker

    --

    *Pasindu De Silva**ppasindud@gmail.com <ppasindud@gmail.com>*
  • Peter Cowburn at Apr 7, 2016 at 1:50 pm

    On 5 April 2016 at 06:21, Pasindu De Silva wrote:

    HI Matt
    Did you refer http://doc.php.net/tutorial/
    Hi all. Christoph moved the files today (r338941), so the "install/windows"
    directory is freed up for new files. What is your plan moving forward?

    Currently the docs will build such that nothing has changed (since the
    xml:id's weren't touched, hyperlinks aren't broken), which is good. Do you
    want to work in that directory for a while, until such a point that you're
    ready to "flip the switch" and have your install docs published? Or do you
    want http://php.net/manual/en/install.windows.php to point to your
    documentation? I'd advise against the latter unless you're already a
    significant way through the process.

    Keep us posted.


    +1
    On Tue, Apr 5, 2016 at 1:09 PM, Matt Ficken wrote:

    In the PHP Online Docbook Editor, I tried to move the old files to
    install/windows/legacy, which it appears to do, the file tree is updated
    and there is no error message. However, reloading the tree listing of
    files, the changes aren't made.

    I have created a new install/windows/index.xml. However, its currently
    modifying the existing index.xml which I don't want to do. I want to move
    the existing index.xml to legacy.


    Would someone with the karma or access to the repository move those files
    to install/windows/legacy?

    I have a few more changes I want to add to index.xml and I want to add
    Troubleshooting and Recommended Practices pages, but I don't want to do
    that until that is cleared up (and I do think its worth all this trouble to
    keep that legacy info).


    What causes someone to run the PHD docbook rendering system? and release
    the updated html files onto php.net?

    I can't find information about that. For other parts of php.net, I can
    just commit to git repository and wait 20 minutes. For win32/install.txt, I
    can just update php-src.git repository.

    The few changes I want to make, and changes to Troubleshooting page over
    time, what is involved in getting those changes onto php.net?


    Regards
    -M




    On Fri, Mar 25, 2016 at 3:16 AM, Christoph Becker <cmbecker69@gmx.de>
    wrote:
    On 24.03.2016 at 21:17, Matt Ficken wrote:

    I can update win32/install.txt in php-src. Good point.

    Good point about other languages too. Same outdated info for
    install/windows is in all languages and eventually should be updated.

    I can't update that document in all languages(just en, and maybe es or fr).
    For now, can we move just the `en` copy of install/windows to
    install/windows/legacy ? Then I can update that document

    Then, when others are ready to do the translation, they can update it for
    de, ru, etc...
    I'm note sure whether this is a good idea. Moving the en docs to a new
    folder and updating the old docs in place will cause additional
    translation work, if the translators are not aware of this change. The
    doc system[1] will report the install/windows/*.xml docs to be
    out-dated, so a translator would have to update them (what has to be
    done anyway – no problem here). However, the doc system will also tag
    the install/windows/legacy/*.xml docs as new files, and a translator
    might translate them *anew* (not being aware that those files only had
    moved).

    The best solution with regard to translations would be to *copy* all
    files under install/windows/ to the new folder. This way only those
    files that really will change will be tagged as being out-dated in the
    other languages.

    Anyhow, I have created en/install/windows/legacy/ right now.

    [1] <http://doc.php.net/> and <https://edit.php.net/>

    --
    Christoph M. Becker

    --

    *Pasindu De Silva**ppasindud@gmail.com <ppasindud@gmail.com>*
  • Christoph Becker at Apr 7, 2016 at 2:49 pm

    Peter Cowburn wrote:
    On 5 April 2016 at 06:21, Pasindu De Silva wrote:

    HI Matt
    Did you refer http://doc.php.net/tutorial/
    Hi all. Christoph moved the files today (r338941), so the "install/windows"
    directory is freed up for new files.
    Thanks, Peter, for posting this information. For some reason my reply
    sent the other day apparently didn't make it through to the list.

    --
    Christoph M. Becker
  • Christoph Becker at Apr 7, 2016 at 2:57 pm

    Matt Ficken wrote:

    In the PHP Online Docbook Editor, I tried to move the old files to
    install/windows/legacy, which it appears to do, the file tree is updated
    and there is no error message. However, reloading the tree listing of
    files, the changes aren't made.

    I have created a new install/windows/index.xml. However, its currently
    modifying the existing index.xml which I don't want to do. I want to move
    the existing index.xml to legacy.


    Would someone with the karma or access to the repository move those files
    to install/windows/legacy?
    I have moved all files except index.xml to the legacy/ folder (en plus
    all translations which had not been marked as broken), and fixed the
    included entities in index.xml (r338941).
    I have a few more changes I want to add to index.xml and I want to add
    Troubleshooting and Recommended Practices pages, but I don't want to do
    that until that is cleared up (and I do think its worth all this trouble to
    keep that legacy info).


    What causes someone to run the PHD docbook rendering system? and release
    the updated html files onto php.net?

    I can't find information about that. For other parts of php.net, I can just
    commit to git repository and wait 20 minutes. For win32/install.txt, I can
    just update php-src.git repository.

    The few changes I want to make, and changes to Troubleshooting page over
    time, what is involved in getting those changes onto php.net?
    As Pasindu had already pointed out, that is explained on
    <http://doc.php.net/>. What you're looking for is
    <http://docs.php.net/> which is updated every 6 hours.

    --
    Christoph M. Becker

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-doc @
categoriesphp
postedMar 23, '16 at 7:19a
activeApr 7, '16 at 2:57p
posts11
users5
websitedoc.php.net

People

Translate

site design / logo © 2019 Grokbase