1) Translation bugs
Theres many translation bugs reported [1] reported to the bug tracker
and I don't think that many translators check for bugs in there. So I
propose we add a link to the docweb site for when you're focusing on a
specific translation to eg. say:

Project (documentation) bugs
53 open bugs
4 open translation bugs

Aswell as sending a perhaps monthly email to their mailing list, like
the bug summary being sent to internals.

Unfortunately our bug system is not equipped for this task so the coding and maintaining of this currently wouldn't be the most fun... but it's a fine idea and certainly doable.

A few options that come to mind:
- Add new feature to bugs web, which would involve changes to the db schema - Parse the subjects on the docweb server (via RSS downloaded from bugs web)
- Add slow queries on bugs web that parses the subject (not a good idea)
- Add new "Type of Bug" for each language (not a good idea)
- ...

Note: We've been pretty good about maintaining [LANG] in subjects for the translation bugs.

2) Many of the reported translation bugs as said above are related to
outdated versions of a file, I think we should put a notice on the
manual pages if a page is outdated so people don't miss information or
features that may be useful to them aswel as a link to the english
version of the page.

This is a good idea and on the table, specifically the following bug report:

  http://bugs.php.net/44903

Regards,
Philip

Reply via email to