Confirmed users, Bureaucrats and Sysops emeriti
2,976
edits
mNo edit summary |
No edit summary |
||
| Line 52: | Line 52: | ||
===== Required tooling ===== | ===== Required tooling ===== | ||
* TBD | * TBD | ||
=== Transifex === | |||
Developers publish their strings on transife, and export the localized strings into their app. | |||
===== Tooling ecosystem ===== | |||
* transifex | |||
* tx (transifex commandline client) | |||
* no version control, no attribution in source code | |||
===== Lock-ins ===== | |||
* transifex is the only editor | |||
* transifex db is the only source of contribution metrics | |||
* transifex is closed source, future development can be negotiated by anyone | |||
===== Existing tooling ===== | |||
* transifex, tx | |||
===== Required tooling ===== | |||
* TBD | |||
=== The Gaia Way === | |||
For gaia, we have a repository per locale per branch that's holding the strings, including one for en-US. | |||
===== Tooling ecosystem ===== | |||
* hg repositories | |||
* loads of them | |||
* involved build process | |||
* extraction process for strings from gaia into gaia-l10n/en-US | |||
===== Lock-ins ===== | |||
* hg | |||
** for the string extraction code | |||
** for elmo | |||
===== Existing tooling ===== | |||
* elmo | |||
===== Required tooling ===== | |||
* set up and lead time are huge, don't scale | |||
* ending the life time of a project is undefined | |||
* most teams don't work on hg directly, but on a pootle instance | |||
** more setup | |||
** more tooling to move data back and forth | |||
* can benefit from Aisle | |||
=== TBD === | |||
===== Tooling ecosystem ===== | |||
===== Lock-ins ===== | |||
===== Existing tooling ===== | |||
===== Required tooling ===== | |||