Red Hat Bugzilla – Bug 435412
Add virt-manager to transifex
Last modified: 2013-07-02 20:48:30 EDT
Description of problem:
It would be useful to send translation to virt-manager using transifex.
Module name: virt-manager
VCS: Mercurial (hg.et.redhat.com)
Francesco thanks for bringing this up. The steps needed to be taken are
documented at http://fedoraproject.org/wiki/L10N/FAQ#add-transifex.
We need the maintainer's permission for this (CCing berrange).
Also, we'll need a contact point for an admin to create a VCS user on
hg.et.redhat.com for Transifex (CCing mmcgrath).
Shouldn't virt-inst also be added to Transifex?
We are not able to allow transiflex direct commit access to hg.et.redhat.com
because the firewall does not allow SSH traffic from the place where Transiflex
The best that we can do is allow Transiflex read-only repository access so that
it can obtain the up to date .pot and .po files. We would then have to
periodically pull Transiflex data into the SCM repo ourselves.
And yes, virtinst needs to be managed the same way as virt-manager
Roger that. Currently we only support pushes, however the feature "Manually pull
from Tx periodically, instead of having it automatically push" is indeed a
popular one (yum wants it too, among others). Since this involves some serious
thinking and engineering work (auto merging, or, or...), its implementation
might take some time.
Until then, the simplest solution would be for your group to have a public hg
repo created at fedorahosted which Tx can write to, and use that to pull from
and Tx to push to. A second one would be to add support to just email the
Is there any progress on this bug, so far?
Fedora 10 translation submission due date is 21st October...
It is Software Translation Deadline tomorrow, 12-Oct.
Translators would like to pass their translated PO files of virt-*, and move on other translations such as documentation.
How would you like to receive them?
I can open new bugs for file submission against virt-manager, virt-df, virt-mem and virt-top components respectively. Others such as virt-ctrl, virt-inst and virt-p2v have not appeared in the component section, so those can be attached here.
Or can you specify the bug to attach or any alternate way?
(In reply to comment #6)
> I can open new bugs for file submission against virt-manager, virt-df, virt-mem
> and virt-top components respectively. Others such as virt-ctrl, virt-inst and
> virt-p2v have not appeared in the component section, so those can be attached
virt-inst package name is python-virtinst. Also I believe virt-p2v is a kind of Live CD, so it won't appear in Bugzilla.
Any translated files for virt-ctrl and virt-p2v will be attached here.
Rest I am creating new bugs.
Since there is no chance to add virt tools to Transifex, and we still have to do everything by hand, I'm closing this report.
Have you guys considered developing virt-manager in a more community friendly / open way? fedorahosted.org immediately comes to mind and supports transifex. Just 2 cents.
Mass change of component from Transifex to Website, since all our websites are handled by Transifex now.