Re: [PHP-DOC] [HEADSUP] Call for help
2009/7/5 Daniel Brown paras...@gmail.com: Still, there are a couple of minor changes and some typofixes herein. I also made a few, very minor changes in an effort to make sentences flow a little better (for me at least) and to fix an existing typo (explaination). My only real question is if we want to leave the kick-ass portion in there, since it's going on the main page, or if we'd want to approach it with a slightly more professional tenor. I don't think it's inappropriate to a level of being obscene, but maybe a bit abrasive. For what it's worth, I'd rather see kick-ass awesome in there than it being left out. :) Regardless, the new XML is attached. Ditto. ?xml version=1.0 encoding=utf-8? entry xmlns=http://www.w3.org/2005/Atom; titleThin documentation?/title idhttp://www.php.net/archive/2009.php#id2009-07-05-1/id published2009-07-05T01:40:12+02:00/published updated2009-07-05T01:40:12+02:00/updated category term=frontpage label=PHP.net frontpage news/ link href=http://www.php.net/index.php#id2009-07-05-1; rel=alternate type=text/html/ link href=http://www.php.net/archive/2009.php#id2009-07-05-1; rel=via type=text/html/ content type=xhtml div xmlns=http://www.w3.org/1999/xhtml; pSince the inception of PHP it has been known for having _the_ strongbest/strong, kick-ass awesome documentation./p pIn recent years, some have commented on the fact that the documentation of new features is insufficient, and lacks in-detail explanations and descriptions of common what-if scenarios./p pEffective immediately, we are placing an open call for volunteers to help the project to get up to speed with the massive changes PHP has undergone in recent years, and to catch up with all the new features the language has to offer./p pObviously any and all contributions to the project are very much appreciated and getting a CVS account along with the appropriate karma is a very simple task./p pIf you are interested in helping out, please contact the documentation team at a href=mailto:phpdoc@lists.php.netphpdoc@lists.php.net/a today./p /div /content /entry
Re: [PHP-DOC] [HEADSUP] Call for help
On Jul 5, 2009, at 10:25 AM, Peter Cowburn wrote: For what it's worth, I'd rather see kick-ass awesome in there than it being left out. :) I agree! Ted S-R http://tedmasterweb.com
[PHP-DOC] Notes Status, 21855 total
Following are the top 20 pages of the manual, sorted by the number of user notes contributed. These sections could use a polish, those notes represent 6.5% of the 21855 total user notes. Notes | Page ---+- 82 | http://php.net/manual/en/function.curl-setopt.php 75 | http://php.net/manual/en/features.http-auth.php 75 | http://php.net/manual/en/function.number-format.php 74 | http://php.net/manual/en/function.session-start.php 74 | http://php.net/manual/en/ref.com.php 73 | http://php.net/manual/en/function.serialize.php 73 | http://php.net/manual/en/function.array-merge.php 72 | http://php.net/manual/en/function.xml-parse-into-struct.php 72 | http://php.net/manual/en/function.date.php 71 | http://php.net/manual/en/features.file-upload.php 71 | http://php.net/manual/en/install.windows.php 70 | http://php.net/manual/en/ref.exec.php 70 | http://php.net/manual/en/function.array-unique.php 69 | http://php.net/manual/en/function.exec.php 69 | http://php.net/manual/en/function.session-set-save-handler.php 68 | http://php.net/manual/en/language.oop5.overloading.php 68 | http://php.net/manual/en/function.imagejpeg.php 68 | http://php.net/manual/en/function.strtotime.php 68 | http://php.net/manual/en/ref.mysql.php 66 | http://php.net/manual/en/function.array-search.php
[PHP-DOC] Re: [HEADSUP] Call for help
Hannes Magnusson hannes.magnus...@gmail.com wrote in message news:7f3ed2c30907041706k70395232nbe677b06588a0...@mail.gmail.com... Hi all The PHP documentation used to be known to be fckingeyh kickass awesome documentations, but since PHP 5 we have been struggling with keeping up with all the new features and extensions that have been implemented. I would like to place an open call for contributions, of noone objects, as of tomorrow (July 6th). Attached is an NEWS entry I will be committing tomorrow morning - but I would really appreciate if an native-English speaker could read over it. Any and all suggestions for improvements would be very appreciated! -Hannes With the documentation moving to PO files soon (as well as changes around the PhD editor GSoC project), wouldn't it be wiser to wait until at least one of them has been implemented? From what I understand the gettext-conversion will be completed later this month. Thanks, Peter
Re: [PHP-DOC] What can go in a package's Introduction?
Hi Eddie: 3) Why use Reflection? - an analysis of realistic cases where Reflection is useful, perhaps linking ot external resources for further research (wikipedia, probably) And basically, I've not seen (not that it doesn't exist), an example of #3 in use in the PHP manual any where, nor can I find any sort of RFC or guideline forbidding it. So, my question is whether or not that sort of documentation is allowed or not. You're making a very good point. It makes a lot of sense to have a Purpose section. A simple paragraph or two telling folks how this class/extension/whatever can make your life better. Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
Re: [PHP-DOC] Re: [HEADSUP] Call for help
On Jul 5, 2009, at 2:57 PM, Peter Beverloo wrote: With the documentation moving to PO files soon (as well as changes around the PhD editor GSoC project) I follow this list pretty closely but I must have missed this (rather important) news item. When will the documentation move to PO files? How will this change the translation process and source files? Is this move documented somewhere? In short, is there an other list where such decisions are made that I'm unaware of? Thanks in advance. Ted Stresen-Reuter http://tedmasterweb.com
Re: [PHP-DOC] Re: [HEADSUP] Call for help
On Jul 5, 2009, at 2:53 PM, G. T. Stresen-Reuter wrote: On Jul 5, 2009, at 2:57 PM, Peter Beverloo wrote: With the documentation moving to PO files soon (as well as changes around the PhD editor GSoC project) I follow this list pretty closely but I must have missed this (rather important) news item. When will the documentation move to PO files? How will this change the translation process and source files? Is this move documented somewhere? In short, is there an other list where such decisions are made that I'm unaware of? Several translation related discussions have taken place on the subject although typically they have been short threads. The English documentation process will not change as PO files are only used by translations. The process has been poorly documented (by me) but is moving forward. It's a bit chaotic especially considering the rush to get it done before the project moves to SVN but here are a few recent threads on the topic: - http://markmail.org/thread/iqxkiekmvz6h43lt - http://markmail.org/thread/kidqiimuglh2tmfh - http://markmail.org/message/fduqvora3lef4cit A test repository with PO files are in CVS although they are only English (POT) and Japanese as it's purely for testing purposes: - http://cvs.php.net/viewvc.cgi/phpdoc-po/ How PO files will be managed is still up in the air but we're in the midst of testing out several systems including: - http://www.transifex.net/projects/php/ - http://translate.php.net/ Neither of the above work today as our project appears too large for transifex.net to handle (today, they are discussing how to solve this) but they offer a system that could coincide with whatever else we choose as it offers help from an additional translation community. And our Pootle setup (at translate.php.net) is sketchy with a strange bug (thanks to me) but once Michael has time he'll look into it as my sysadmin skills sit right around null. So that's the situation. Given the mere size of this move, the SVN rush, and my lack of knowledge (but it's interesting to learn this) I'm afraid it won't go smoothly. All help is desired, as are questions and/or answers. Regards, Philip
