Archive:L10N/Admin/SOP

= FLP L10n Administration SOPs =

Following are Standard Operation Procedures for administrating services of the Fedora L10n Project.

Add a module in DL
1. A bug report like this one arrives: https://bugzilla.redhat.com/show_bug.cgi?id=443160

1. Add a corresponding section in your local DL instance.

cd /var/www/html/l10n/ cvs up gedit fedora-modules.xml.in releases.xml.in  make && python update-stats MODULENAME firefox http://l10n.yourdomain/MODULENAME/

Check if stats show correctly. If not, fix  file. You may find out more about the structure of the project somewhere in  etc.

1. Commit.

cvs diff cd po intltool-update -r cd .. cvs -n update cvs commit -m 'Added module MODULENAME (RHBZ #111111)' *.xml.in po/

1. Tag

cvs -n tag -F LIVE cvs tag -F LIVE

1. Now you probably want to go on and add this in Tx as well. Afterwards you can close the bug report.

Add a module in Tx
1. Auth at https://translate.fedoraproject.org/submit/login/ 1. Add module at https://translate.fedoraproject.org/submit/module/add/ 1. Do a "Refresh" at https://translate.fedoraproject.org/submit/module/MODULENAME/ 1. Test submissions: 1. Get your file from http://l10n.localhost/module/MODULENAME/. 1. Translate: 1. Submit it at https://translate.fedoraproject.org/submit/module/MODULENAME/. 1. Check that it was submitted successfully at the bottom of the module page and at the VCS (eg. http://hg.fedoraproject.org/hg/MODULENAME/). 1. Close bug report with a comment similar to #443160. If there are i18n errors, write a message similar to this one.