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