[PHP-DOC] Doc Team Organization
Hello, I work on PHP-GTK docs and I want to get our team more organized. I'd like to have a way to track what work still needs to be done so that we can work more efficiently. I would like to know which docs pages are complete, started but not complete and haven't even been started yet. Also I'd like to keep track of what translations have been done. Since the PHP doc team has been around longer, I was hoping you might have some suggestions for getting organized. Is there a system you use? Or does the organized chaos theory (just find something that needs doccing and do it) work pretty well? Thanks, -- Scott Mattocks Author of the soon to be published: Pro PHP-GTK http://www.crisscott.com
[PHP-DOC] #37000 [NEW]: Suggestion for improving Database Security chapter
From: david at acz dot org Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Suggestion for improving Database Security chapter Description: It would be helpful for the Database Security chapter to discuss security in a shared hosting environment. Under a typical Apache / mod_php setup where PHP scripts all run as the Apache user, any user can read any other user's PHP scripts and thus capture any database authentication information. It may be possible to mitigate this with safe mode, but not if the server allows running other types of CGIs. -- Edit bug report at http://bugs.php.net/?id=37000edit=1 -- Try a CVS snapshot (PHP 4.4): http://bugs.php.net/fix.php?id=37000r=trysnapshot44 Try a CVS snapshot (PHP 5.1): http://bugs.php.net/fix.php?id=37000r=trysnapshot51 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=37000r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=37000r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=37000r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=37000r=needtrace Need Reproduce Script:http://bugs.php.net/fix.php?id=37000r=needscript Try newer version:http://bugs.php.net/fix.php?id=37000r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=37000r=support Expected behavior:http://bugs.php.net/fix.php?id=37000r=notwrong Not enough info: http://bugs.php.net/fix.php?id=37000r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=37000r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=37000r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=37000r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=37000r=dst IIS Stability:http://bugs.php.net/fix.php?id=37000r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=37000r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=37000r=float No Zend Extensions: http://bugs.php.net/fix.php?id=37000r=nozend MySQL Configuration Error:http://bugs.php.net/fix.php?id=37000r=mysqlcfg
Re: [PHP-DOC] Doc Team Organization
Hi, We have a couple of scripts to help us tracking the progress (missing functions, undocumented functions, outdated protos, missing examples, etc..). The undocumented functions are the proto-only pages. We can find them easily because of the entity used in those pages. You can use similar schemes. Take a look at http://doc.php.net/php/ The code of that site in the 'docweb' module in our cvs. Some other scripts are also available in the phpdoc/scripts dir. Nuno - Original Message - Hello, I work on PHP-GTK docs and I want to get our team more organized. I'd like to have a way to track what work still needs to be done so that we can work more efficiently. I would like to know which docs pages are complete, started but not complete and haven't even been started yet. Also I'd like to keep track of what translations have been done. Since the PHP doc team has been around longer, I was hoping you might have some suggestions for getting organized. Is there a system you use? Or does the organized chaos theory (just find something that needs doccing and do it) work pretty well? Thanks, -- Scott Mattocks Author of the soon to be published: Pro PHP-GTK http://www.crisscott.com
Re: [PHP-DOC] Doc Team Organization
Since there is already a PHP-GTK subsite in DocWeb, and I assume that the PHP-GTK also uses docbook, etc. would it be too much effort to simple modify the mentioned scripts to work for PHP-GTK as well - thus keeping all doc related stuff 'centralised'? M Nuno Lopes wrote: Hi, We have a couple of scripts to help us tracking the progress (missing functions, undocumented functions, outdated protos, missing examples, etc..). The undocumented functions are the proto-only pages. We can find them easily because of the entity used in those pages. You can use similar schemes. Take a look at http://doc.php.net/php/ The code of that site in the 'docweb' module in our cvs. Some other scripts are also available in the phpdoc/scripts dir. Nuno - Original Message - Hello, I work on PHP-GTK docs and I want to get our team more organized. I'd like to have a way to track what work still needs to be done so that we can work more efficiently. I would like to know which docs pages are complete, started but not complete and haven't even been started yet. Also I'd like to keep track of what translations have been done. Since the PHP doc team has been around longer, I was hoping you might have some suggestions for getting organized. Is there a system you use? Or does the organized chaos theory (just find something that needs doccing and do it) work pretty well? Thanks, -- Scott Mattocks Author of the soon to be published: Pro PHP-GTK http://www.crisscott.com
