On Sat, 2007-09-08 at 14:55 +0100, Dimitris Glezos wrote:
Στις 08-09-2007, ημέρα Σαβ, και ώρα 12:36 +0200, ο/η Nils Philippsen
> On Sat, 2007-09-08 at 00:58 +0200, Xavier Conde Rueda wrote:
> > Hi,
> > 2007/8/30, Domingo Becker <domingobecker(a)gmail.com>:
> > > > I've already built the system-config-samba-1.2.48-1.fc8 package
> > > > know that would violate policy). This contains a new dialog which
> > > > about unknown Samba configuration options instead of throwing a
> > > > traceback, see: https://bugzilla.redhat.com/show_bug.cgi?id=247541
> > > >
> > > > IMO, it would be better to keep the new string in without it being
> > > > translated than throwing it out again.
> > > >
> > > > Thanks,
> > > > Nils
> > >
> > > There is no problem for spanish locale.
> > > But I seen yesterday that all po files vanished !
> > > By the way, this module is not in i18n status page while it is in its cvs
> > > Translate.fpo status page seems to be showing a wrong state of this
> > >
> > Same as Domingo: where is this module, please?
> all system-config-* modules of mine as well as hwbrowser were moved from
> CVS on elvis/rhlinux to Mercurial repositories on
. This is not to annoy or confuse you, the
> translators but part of a "bigger" plan to move wholesale to Fedora
> infrastructure, not only for my packages but for all where we are
> upstream (in the long run), and thus allowing for different source code
> management (SCM) systems than CVS. I very much hope that this plan was
> outlined in the translators circles as well.
> I've moved my stuff sometime in July upon receiving notice of this plan
> by Dimitris Glezos (on Cc). Another part of that plan was to move to a
> better translation infrastructure where you translators don't need to
> know about how to use all the SCM systems used in the various projects
> (some still use CVS and I believe you can still commit your changes
> directly for those, some use Subversion, some Mercurial (Hg), some git),
> but can do the translating with one (web-based) tool ("Transifex") that
> would deal with the projects' SCMs in the background. Much to my dismay,
> it doesn't seem that we're there yet.
> Dim, can you please expand on this, correct my mistakes ;-) and tell us
> when we can expect Transifex to be in production?
Thanks for the recap Nils. Better communication with the translation
team means more clear ideas on what's happening.
Ditto here, I wasn't aware that I needed to do anything else beyond
getting my stuff moved away from elvis CVS to hosted Hg. I just assumed
it would be implicitly clear that the translation source would have to
be moved as well...
The work the Fedora Infrastructure folks have done concerning the
"move" (in quotes because it was more a copy than a move) is mentioned
Translators know about the above page, but that's almost all we know. We
track the modules we are contributing to and their respective repos at:
This list needs to be updated immediately when the development of
modules moves away from a repo, otherwise translators don't know where
the development for a module takes place. We need to be notified
(preferably with a mail and a bug report) if/when/which of the modules
mentioned in the elvis move did actually move their development on the
... but I guess I just didn't make this connection because the first
mail about the subject was from you -- I somehow thought the rest would
fall in place automatically.
I'll send right now an email to the other owners mentioned on
ElvisMove page to remind them to notify us where they want us to commit
translations to. Concerning your modules Nils: Should we update the
website and make all the modules listed under your name on the ElvisMove
page to point to the new repos?
Yes please, but I'll send a reply to your second mail right away so you
don't have to make exceptions for my modules.
(I've been extremely busy with my work lately and I have given
as much attention as I am able to. There's only so much one can do and
take care of. A big "Thanks!" to Diego and Piotr who have helped a lot
lately with our statistics config files.)
I didn't want to criticize, just point out that there are some loose
I've created the following ticket to keep a better track on
I would very much like to have it as soon as possible. But having a
software like transifex in production is a sensitive process in terms of
security and we better be safe than sorry.
Is there anything particular with which I can help? I don't know the
Transifex code but if it's not too overwhelming I should be able to find
my way around after a short intro. I'm not sure about that ticket #147,
but there are some new strings in -samba and -users that needs
translation, so feel free to use them as guinea pigs (once I've
submitted the mail officially notifying translators about the VCS move).
The worst case scenario in terms of deploying will be to *not*
and copy the modules in question somewhere in `/cvs/l10n/` for
translators to commit there.
Ugh ;-). That would smell like much manual labour.
Best case would be: Have the VCS users created in the weekend by
Monday have access to smolt, revisor; at least 4-6 translators show up
on IRC and help test; Until Wednesday add all the modules mentioned on
the ticket. If many people help out and let us know what should happen,
then even this tight schedule could work.
Hope I helped clarifying some things.
Yes. Again, please tell me if there is anything else I can help out
with, code-wise or have-fun-with-my-modules-wise or else ;-).
Nils Philippsen / Red Hat / nphilipp(a)redhat.com
"Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011