> -----Original Message-----
> From: John Mertic [mailto:jmer...@gmail.com]
> Sent: Monday, September 14, 2009 11:59 AM
> To: Hannes Magnusson
> Cc: Ruslan Yakushev; John Mertic; PHP Documentation ML
> Subject: Re: [PHP-DOC] Re: [PHP-WIN] 32bit PHP on 64bit Vista.
> 
> Ruslan, if you want to send me your suggested edits I can review them
> and update the manual ( I created the original pages related to the
> MSI based Windows installer ).
> 
> John Mertic
> jmer...@gmail.com
> 
> 
> 
> On Sep 14, 2009, at 2:49 PM, Hannes Magnusson wrote:
> 
> > Couple of "rules" :)
> > - Please do not top-post (makes the post hard to read)
> > - Always CC the mailinglist (phpdoc@lists.php.net)
> > - Preferably tell your mail client to wrap lines after ~80 chars
> >
> >
> > On Mon, Sep 14, 2009 at 19:35, Ruslan Yakushev
> > <rusl...@microsoft.com> wrote:
> >> Hi Hannes,
> >>
> >> I have written and have been maintaining all the PHP related
> >> documentation on http://php.iis.net/. I can help out with updating
> >> the windows/IIS specific docs on php.net.
> >>
> >> Here are some of the ideas I have about the updates. The following
> >> are the existing topics under
> http://www.php.net/manual/en/install.windows.php
> >>  that can be updated as well as new topics that can be added:
> >>
> >> 1. http://www.php.net/manual/en/install.windows.installer.msi.php -
> >> For this article it would be good to change the title to "Windows
> >> Installer (Thread Safe PHP 5.2 and later)" and update the content
> >>
> >
> > Sounds good. John (CCed) could probably help you out there (as the
> > author and maintainer of the installer).
> >
> >> 2. Add new article "Windows Installer (Non Thread Safe PHP 5.2 and
> >> later)"
> >
> > I didn't know we had a non-thread-safe installer?
> >
> >
> >> 3. http://www.php.net/manual/en/install.windows.manual.php - Update
> >> the content
> >>
> >> 4. Remove this: http://www.php.net/manual/en/install.windows.iis.php
> >>
> >> 5. Add "Microsoft IIS 5.1 and IIS 6.0" - this will list manual
> >> installation steps to configure IIS; similar to what is described
> >> here: http://learn.iis.net/page.aspx/247/using-fastcgi-to-host-php-
> applications-on-iis-60/
> >>
> >
> > Since the "What is FastCGI", "configuring FastCGI" and those sections
> > aren't specific to installing PHP on Windows and therefore shouldn't
> > be part of the Windows install guide. Its however a great idea to
> make
> > it its own generic section in the top-level-install guide.
> >
> > As for the download section in the article, the notes and links to
> > zend platform are inappropriate for the manual
> >
> > The phpBB sections are obviously out-of-scope for the PHP manual.
> >
> >
> >> 6. Add "Microsoft IIS 7.0 and later" - this will list manual
> >> installation steps to configure IIS; similar to what is described
> >> here: http://learn.iis.net/page.aspx/246/using-fastcgi-to-host-php-
> applications-on-iis-70/
> >>
> >
> > Looks good. There is a slight information overlap with the previous
> > chapter. If you chunk it out into "best practices" (or something) and
> > cross link it.. I think that would be awesome.
> >
> >> What do you think? Do these make sense to you?
> >>
> >
> > Sounds like a great plan.
> >
> >
> >> I have couple of questions:
> >>
> >> 1. I can provide the content for the updates. Is it possible for me
> >> to get an account to be able to check in the updated content?
> >
> > Yes. Once you have "something to show for it" (i.e. patches) you can
> > request for an SVN access and documentation karma at
> > http://php.net/svn-php (make sure you read the page carefully,
> > especially the form questions).
> >
> >
> >> 2. If the content of the existing article is changed or removed,
> >> what happens to all the user contributed notes for that article?
> >>
> >
> > We have a system on master
> > (https://master.php.net/manage/user-notes.php) which can reallocate
> > them, modify and/or delete user notes. Everyone with php.net (SVN)
> > account has access to it.
> >
> > -Hannes
> 

Ok. Sounds good. I will start working on preparing the content patches.

Reply via email to