We are restarting this project in December 2021. Here is the Telegram.org chatroom: https://t.me/TikiTranslations
What
i18n.tiki.org will permit Tiki community members to easily contribute interface translations.
Who
Site and Server Management
- Elvis, Nasser and Rodrigue (junior devs) lead the project
- Coaching from Bernard for Tiki configurations and UX.
- Coaching from Horia for sysadmin issues
- Coaching from Fabio for Git issues.
- Coaching from Adrien and Jonny Bradley on PHP and JS coding issues
Translators
We are hoping to assemble a team of 10-15 translators. Please add your name below.
- Swahili: Joel
- French: Elvis, Nasser and Rodrigue
- Romanian: Horia, Lavi
- Croatian: Gour
- You?
Why
This project is sponsored by EvoluData.com for reasons including:
- Foster an active community of translators, that translate of course, but that also discuss how to improve the translation system and process (technical and coding, harmonize source terminology in English, etc.)
- Translators will be able to easily get to work as soon as code lands in trunk (No need to wait for a stable release)
- Training junior developers to manage a real project, but that is not mission-critical
- A way to continuously test trunk, acting as a "canary in a coalmine"
- Serves as a demo to promote Tiki
- Serves as a place to test translation-related bugs (ex.: hman reports an issue in 18.x and we can quickly check if it's still an issue in trunk)
When
Short term
- Horia will supply a new Virtualmin Virtual Server with backups, GlitchTip and monitoring (Zabbix)
- Those needing SSH access should supply their public key to Horia
- Get site going as it once was.
- We had a bot committing translations. Here is an example. We should update this to getting merge requests to GitLab (which can be manually approved)
- Update Translation documentation to 2022
Medium term
- How to prioritize translations with for example back-end vs front-end? (A suggestion from Ed): Translation Priorities
- Send activity/alerts to the chatroom
- New translations
- Zabbix alerts
- Major errors in GlitchTip
- Review if/how translations can be attributed to the translator (and not tikii18nbot)
- Review and improve translation workflow
- A more automatic system with GitLab
- Investigate how translations could be backported to supported branches (ex.: 21x)
How
Scope
- i18n.tiki.org will be a standard WikiSuite installation so anyone can reproduce with Open Source
- It will be hosted on a so-called dogfood server
- While Elvis, Nasser and Rodrigue will be responsive, translators should expect some periods of mediocre stability and uptime because
- site will be updated daily from trunk
- site will be managed by junior developers
- all translators will have full admin access
Out of scope
- Elvis, Nasser and Rodrigue will not be responsible to address bugs that are unrelated to interface translations. They can help report the bug and rollback the site to an earlier known-working version.
- This project has no relation with Transifex or any other such platform.
- This project is for Interface Translations and not content translations (That would be a distinct project)
- As of 2021-12-12, only lang/xx/language.php are covered and not lang/xx/language.js
Implementation
- We use a vanilla install of Tiki trunk
- There should not by any customizations to the code or themes because translators need access to a standard Tiki instance
- We set Tiki Manager on daily cron for instance update.
- Translators have admin rights and leverage the Interactive Translation feature
- Translations are saved to language.php via https://gitlab.com/tikiwiki/tiki/-/merge_requests/717/diffs
- Translations are proposed as https://gitlab.com/tikiwiki/tiki/-/merge_requests/
Support
Here is the permanent chatroom: https://t.me/TikiTranslations
- The junior developers are responsible to take charge of all translation-related issues.
- They will try to fix themselves, and if they can't, they will log a wish on https://dev.tiki.org
Questions
- Do we let create users on i18n.tiki.org or use InterTiki or Remote Auto-login? Keep in mind that all translators need full admin permissions so they can translate the admin panels.
- Given we'll be running trunk, and translations will be upstreamed frequently and preferences will often change (translators need to adjust to see various strings to be translated): Should we plan for the Tiki instance to be periodically reset? And we use System Configuration to maintain preferences necessary to the translation workflow. We could also create a profile with the benefit to make it easy for anyone to create their own Tiki instance for translations.
- Marc has an archive of the old i18n.tiki.org server (machine shut down on Linode): Is there anything on this to recuperate?
- Names and emails of translators?
- Scripts in development?
Related links
- Recent translation-related commits: https://gitlab.com/tikiwiki/tiki/-/commits/master/lang
- https://tiki.org/article190-Interactive-Multilingual-Crowdsourcing-translations-with-Tiki (video is missing as it was uploaded to a platform which later died)
;){kind=link}
;){kind=link}