Fixing Help typos and other errors
Help contents are in XML and most of the editions carried by editing XML text. This is not error-prone and actually typos and small corrections exists as well as linguistic issues. Thanks to translators, many errors are detected and reported.
Fixing Help content issues
However the process currently is:
- Translator pick the typo and report to pootle admin
- Pootle admin forward to documentation list
- Doc coordinator pick the issue and
- locate pootle page
- identify project/application/xhp page/string
- edit the xhp file in his local copy
- compile help
- verify correction in local build of help, locating subject
- once verified, commit to local git copy
- submit to git/gerrit
- wait approval or approve himself
- write to doc list, the issue is fixed.
Furthermore, the master help is ahead of the uploaded pootle templates, which means an issue may be reported more than once and be fixed already. This is another waste of time.
Let the translator/volunteer correct the issue himself
- install a VM for Help XML edition
- clone helpcontent2/
- install a PHP text editor (e.g. codiad or any other good text editor).
- control access to editor through username and password
- Log-in to editor
- Locate the page (ideally a link between pootle UI and the help editor)
- edit changes
Daily or weekly task
- Check the git diff of the corrections (under shell access)
- commit changes to local copy
- submit to gerrit with his key under "l10n team" authorship
- report to doc list
- No way to compile the Help, but a skilled committer can inspect diff'ed and correct or approve
- Committer handle git issues (pull, rebase, etc..