We are restarting this project in December 2021.
What
i18n.tiki.org will permit Tiki community members to easily contribute translations.
Who
Site and Server Management
- Elvis and Nasser (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 on PHP and JS coding issues
Translators
We are hoping to assemble a team of 10-15 translators. Please add your name below.
- Urdu: Ramsha
- Swahili: Joel
- French: Elvis and Nasser
- You?
Why
This project is sponsored by EvoluData.com for reasons including:
- Foster an active community of translators, that also discuss how to improve translations (technical and coding, terminology, etc.)
- Improving state of translations in Tiki
- 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
- Those needing SSH access should supply their public key to Horia
- Get site going as it once was. Let's restore the robot that was committing translations: https://sourceforge.net/users/tikii18nbot
- Update docs of what is working
- Start getting merge requests to GitLab (which can be manually approved)
Medium term
- 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
Here is some background information explained in a meeting in 2018 (The project started but never really reached usefulness and was overidden by spam, and shut down.)
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 and Nasser will be responsive, translators should expect 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 and Nasser will not be responsible to address bugs that are unrelated to 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)
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.
Support
Here is the permanent chatroom: https://t.me/TikiTranslations
- The junior developers are responsible to take charge of all translation-related issues.
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.
Old content to be cleaned up
[+]
Todo: Move any still relevant to the section above, and delete the rest (it will live together in wiki page history)
Status as of 2021-10-31:
i18n.tiki.org was pulled offline because it was overridden by spam and we didn't have suitable people available to manage the project. I still believe it's a good idea though. {
}
This site is managed by the i18n Team
Background:
Tiki's multilingual features are already very good. It is possible to manage a site in 35+ languages. It is also possible to manage a multilingual site with a single Tiki install. However, there are still a lot of ideas to improve.
What:
- DogFood, debug, showcase and enhance all i18n features to improve Tiki as:
- an Open source Translation management system.
- a Multilingual wiki
- a Multilingual Content Management System
- To have an area dedicated to translations, multilingual, i18n and l10n issues.
- Translation upstream
- How can we have Tiki translated in 100 languages?
- Promote some little known scripts like:
Tasks:
- Identify & contact everyone that has ever translated for Tiki.
- Contact people for each language (with maps.tiki.org and from chosen language in User preferences) and put them in contact with each other.
- Coordinate TikiFests in various countries
- Participate to wiki-translation.com
Who:
Please add your name below if you want to participate. When 5 people are ready to go, we'll launch the project. We'll need a coordinator.
- Rodrigo
- Xavi de Pedro (I offer some time for testing, documenting...)
- Wesley Willians (i offer some time for testing, translating, etc)
- Jonathan Whitson Cloud (I am building a site with many languages, 42 requested so far) Documentation is my professional specialism but I also want to learn to contribute to the code base)
alias