Open Stack

Hi Daisy,

I think .tx/config in the repository is still useful even if it is not
directly related
.tx/config is not only for the gate but also for translators.

Assume that we want to generate translated document locally.
We need to setup .tx/config manually without .tx/config in the repo.
If we have .tx/config in the repo, translators do not need to setup .tx/config.
The same applies to Horizon.
Setting up .tx/config in Jenkins jobs does not help translators.
This is the reason that I think having .tx/config in repositories is useful.

An alternative way is to provide an example .tx/config somewhere like I18N wiki.

Thought?

Thanks,
Akihiro

On Thu, Jan 23, 2014 at 6:17 PM, Ying Chun Guo <guoyingc at cn.ibm.com> wrote:
> Hello
>
> I noticed some repositories contain .tx folder but some don't.
> The repositories that contain .tx include: openstack-manuals,
> operations-guide, horizon and django_openstack_auth.
> The others, like nova, swift, and etc, don't.
>
> .tx contains some configuration information used by Transifex client.
> It could be created by command: tx init ...
> Since it has no relationship with the source codes of OpenStack,
> I'm thinking if we could remove .tx from git repositories.
>
> And what's more, there is a risk that the changes to .tx in script
> "propose_translation_update_manuals.sh"
> would break this script.
>
> Thoughts?
>
> Best regards
> Ying Chun Guo (Daisy)
>
>
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>