I use transifex to submit the translation every time.
Recently I want to learn how to do this through CVS.
But I failed.
First I used command: cvs -z9 up
then the imformation was as follows:
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /home/tt/.ssh/known_hosts to get rid of this message.
Offending key in /home/tt/.ssh/known_hosts:2
RSA host key for cvs.fedoraproject.org has changed and you have
requested strict checking.
Host key verification failed.
cvs [update aborted]: end of file from server (consult above messages if any)
I am so puzzled. So , I need your help, also who can tell me how to
check my ssh key or some other keys on my machine.
Thanks a lot :-)
Hello to everybody. My name is Victor and I live in Malaga (Spain). I would contribute to fedora translation project, turning any English text into my mother tongue, Spanish. Spanish from Spain may differ from Spanish from Mexico or Argentina, but in essence we speak the same language as US American and Albion English do. In computer and linux matters I will have to be helped, so I hope your help in that.
Hello, my name is Jorge Izaac Zavaleta Escalante I'm from Los Mochis
Sinaloa, México where the timezone is GMT-6 and my FAS username is izaac.
I introduce myself to let you know my intentions to join the cvsl10n
group to help translate Fedora Project documentation to my native
language which is Spanish.
I'm a Systems Engineer from the Hermosillo Institute of Technology and i
got 8+ years of experience in management of Unix based systems like
Linux and HP-UX. And I got some skills in the Python programming language.
My work experience includes network administration, datacenter
technician, and web applications development (back-end area) on some
government institutions of my country.
And in 2005 I used to translate the Gentoo Weekly News for almost a
year. Right now I'm in the Ambassadors Group in the Fedora Project for
my local area participating in some local user groups events. But I
realize that I can help the project in a more direct way joining the
About the translation project, what really got my attention is the
collaborative software called Transifex, which I think is a really great
tool and loved to read is built on Django.
Greetings and thank you all for your time.
ub 1024D/E79BBCAD 2009-02-20
Key fingerprint = 9250 994C B916 FE2B 9A51 3815 32CD 0D66 E79B BCAD
uid Izaac Zavaleta <izaac(a)fedoraproject.org>
sub 1024g/EEDC0B3A 2009-02-20
- Seyyed Mohsen Saeedi
- Tehran, Iran
- FAS username: Saeedi
- Linux instructor and B.S Industrial engineering
- University: Iran university of science and technology(IUST).
- I'm using fedora when fedora 1 released and i teach it to student.
- I'm intersting to work in docs and websites.
- Anything else you'd like to do? helping to infrastructure team.
- Comments, Suggestions about the L10N project
- I have worked with Linux when RedHat 7.3 released. I have a good
knowledge about Network Administration and many different services in Linux.
I teach Linux for many years in iran.
- I helped to farsiweb translation team in the past.
- What level and type of computer skills do you have?I have a good skill
in linux and cisco infrastructure.
- What other skills do you have that might be applicable? network
- GPG KEYID and fingerprint
[mohsen@mohsen ~]$ gpg --fingerprint 842337B9
pub 2048R/842337B9 2009-02-20
Key fingerprint = 2A81 EF23 DF6A B9D6 A2BA A264 E89A 0EDB 8423
uid Mohsen Saeedi <mohsen.saeedi(a)gmail.com>
Full name: Belko Peter
FAS username and language to translate: belkop; Slovak (SK)
I would like to help with the Fedora translation into Slovak language.
GPG KEYID and fingerprint:
[peter@localhost ~]$ gpg --fingerprint 02622EA7
pub 1024D/02622EA7 2009-02-19
Key fingerprint = 62B9 73CD 5817 F7EA 8B23 00BD A463 F40D 0262
uid Peter Belko <belkop(a)zoznam.sk>
sub 2048g/56FCE583 2009-02-19
----- "Dimitris Glezos" <dimitris(a)glezos.com> wrote:
> I'm very happy to announce that we've now landed support for
> statistics in Transifex.
> Lately we've been working heavily in re-writing Transifex and getting
> v0.5 in
> the best shape possible for Fedora 11. Being 3 weeks ahead of the
> freeze, we have plenty of time to test statistics on Transifex
> For Fedora 11, my plan is to switch the old DL for Tx 0.5-devel for
> statistics, and continue to use the proven Tx 0.3 for submissions.
> requested  a publictest instance from the Infrastructure Group to
> it and start putting data and testing it.
> : https://fedorahosted.org/fedora-infrastructure/ticket/1191
> To allow 2 weeks of testing, the instance should be ready by 23/2.
> When we
> see that everything works out as it should, we can discontinue the old
> Our goal with Transifex 0.5 is to include support for both submissions
> statistics, and this way we can put aside our old version of Damned
> Lies which
> is presenting outdated translations. Since only the commits are
> missing from
> Tx 0.5-final, it'll be out in 3-4 weeks, and at that point we go on
> and test
> submissions too, while having Tx 0.3 as a backup solution.
> Some of the advantages of this approach is that using the statistics
> from Tx
> 0.5-devel does not even require hook-up with FAS (only submissions
> authentication), we have a smoother upgrade path for Django/v0.5 and
> we have a
> codebase we know inside-out to build/invest on.
First of all, setting up a test-instance of Transifex 0.5alpha is a good start, so a big +1 from me. You should probably think of a migration script for transferring the data as well. I would suggest  as a good starting point for this, as it is based on Django and gets you quickly up and running.
That said, I have a number of concerns with this approach. Just a few weeks back you noted that 0.5 wouldn't be ready in time for F11, and that a good approach would be to migrate to the new Django-based Damned Lies for F11. Hence, I have spent roughly a week worth of development on this now, and I am announcing a public test period for this by the end of this week. The changes we have made to the upstream Gnome version include Fedora-theming (similar to the existing instance), FAS authentication for translators in the cvsl10n group, proper VCS locking and improvements to the way vcs sandboxes are managed, and now the last bit involves support for publican statistics (for e.g. release notes and selinux-guide).
However, I have no issue with throwing that work away if we can demonstrate that Tx 0.5 will serve the needs of the L10N project better in the given time-frame. My main concern is the translators and their work flow, and for F11 we owe translators a less crap system than what we've been using for the last two releases. My secondary concern is maintainability, and the core of my changes to DL has been ensuring that it doesn't fail as often, and providing better information when it fails.
Some of the benefits with the new Django-based DL:
- Translation teams can be better organized (Does Tx even have team pages?)
- Translators can indicate that they are working on a specific file
- Options of using a Translator->Reviewer->Committer work flow, I suspect linking up the actual commit functionality (migrating it from Tx 03 to DL) is less than a day's work.
- Django based DL has been in production upstream (Gnome L10N) for more than 3 months
So the gist of my message is that we should first look at the how the translation work flow changes by using these two tools. As I see it, we have four options:
1) Tx 0.5 for stats, Tx 0.5 for commits (not implemented yet)
2) Tx 0.5 for stats, Tx 0.3 for commits
3) DjL for stats, Tx 0.3 for commits
4) DjL for stants, DjL for commits (not implemented yet)
So far I'm a few days away from completing (3), and should also be able to get (4) done by early next week. If I can be convinced of a clear roadmap for (1) I'd be happy to help out with that, provided I can see the benefit to the translators with this approach. However, I am a bit afraid that option (2) might hurt Tx more than it gains in the long run. Why not focus on getting Tx 0.5 production ready and in shape to become a great translation platform, rather than simply rushing it in in time for F11?
Maybe I'm missing something obvious, but *it is* great to finally see a test instance of Django-based Tx, so don't get me wrong, and I'm guessing a test instance of both systems will make it easier for us to find the best approach for F11 L10N. I know there have been plans of merging the Django-based Tx with DL as well, perhaps this might be a way of developing a migration-path in that direction as well, as I'm worried that the longer these applications stay separate with active development on both sides, the harder it's going to be to get e.g. Tx accepted for use in Gnome.
I'm very happy to announce that we've now landed support for translation
statistics in Transifex.
Lately we've been working heavily in re-writing Transifex and getting v0.5 in
the best shape possible for Fedora 11. Being 3 weeks ahead of the string
freeze, we have plenty of time to test statistics on Transifex 0.5-devel.
For Fedora 11, my plan is to switch the old DL for Tx 0.5-devel for
statistics, and continue to use the proven Tx 0.3 for submissions. I've
requested  a publictest instance from the Infrastructure Group to install
it and start putting data and testing it.
To allow 2 weeks of testing, the instance should be ready by 23/2. When we
see that everything works out as it should, we can discontinue the old DL.
Our goal with Transifex 0.5 is to include support for both submissions and
statistics, and this way we can put aside our old version of Damned Lies which
is presenting outdated translations. Since only the commits are missing from
Tx 0.5-final, it'll be out in 3-4 weeks, and at that point we go on and test
submissions too, while having Tx 0.3 as a backup solution.
Some of the advantages of this approach is that using the statistics from Tx
0.5-devel does not even require hook-up with FAS (only submissions require
authentication), we have a smoother upgrade path for Django/v0.5 and we have a
codebase we know inside-out to build/invest on.
On our roadmap post v0.5:
- 0.5: Submissions to email,VCSs, probably bugzilla
- Comments everywhere
- Full API
- Integration with Bugzilla eg. for auto-closing of bugs
- Workflow functionality (lock a file, resolve bugs, request translation
review and others, comments)
- Fine-grained permissions on a per collection, release, projects, component,
language and file basis
- Support for people Teams and user groups
- Support for additional i18n formats (mozilla)
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
----- "Piotr Drąg" <piotrdrag(a)gmail.com> wrote:
> Please just note that DL is working perfectly in last few days after
> cache rebuild and it should display correct and updated statistics
and since last week Asgeir has been busy working on updating Fedora's DL to the latest Django codebase from upstream, which is already running well for Gnome.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Piotr Drąg <piotrdrag(a)gmail.com> changed:
What |Removed |Added
| |m, piotrdrag(a)gmail.com
Component|Farsi [fa] |l10n-requests
--- Comment #3 from Piotr Drąg <piotrdrag(a)gmail.com> 2009-02-17 17:05:33 EDT ---
Added, committed and tagged as LIVE. Should be here in a few hours.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
To Team Coordinators,
To make the approval process faster for cvsl10n group, it is requested
to each team coordinator to provide your FAS user-name. So that you will
be upgraded to 'Sponsor' to sponsor you local language translator.
If you are not team coordinator but willingly to sponsor, this is the
chance to step forward with your FAS user-name:)
Currently only 16 languages' teams have their sponsors ..
Punjabi, Gujarati, Dutch, Brazilian Portguese, Greek, Spanish, German,
Italian, Slovak, Balochi, Japanese, French, Polish, Bengali India,
To All Existing Sponsors and Administrators,
Please encourage yourself to sponsor new translator with no team
coordinator and new translator whose coordinator not in the Sponsors
list yet ..