Utilities, assets and configurations used by I18n team
4120e834f2
- Describes that release activities are mainly related with cycle-with-milestone release model projects and translation targets - Documentation in openstack-manuals follows independent release model and project repositories can have stable branch documents. Let's describe this. - Also, explains that other official project can be a release target to I18n team upon request assuming that there is a cross-project liaison to I18n team. Change-Id: Ibbcf797b11a58fb57b7dd044d1d6948ce5b06cbc |
||
---|---|---|
checksite | ||
doc/source | ||
glossary/locale | ||
playbooks | ||
resources/mascot | ||
tools | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
ansible-requirement.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
OpenStack I18n
Internationalization (I18n) is essential to make OpenStack ubiquitous. The mission of OpenStack I18n team is to make OpenStack ubiquitously accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for better quality of outcomes.
About this repository
This repository maintains useful assets for the I18n team, including the contribution guide, the terminologies and so on.
Getting in touch
- Mailing List
-
We use openstack-i18n@lists.openstack.org as the mailing list.
- IRC
-
We all hang out on #openstack-i18n IRC channel on freenode.
- Team Meeting
-
We have a bi-weekly meeting on Thursdays at alternating times.