4:37 p.m.
Hey all.
Today we had a lengthy discussion on IRC about the way we should handle
translations in Fedora. The plan is basically to move applications (and their PO
files) that are being developed on elvis (a RH server) over to
'cvs.fedoraproject.org'. It seems that this will not happen before the F7
release.
We have already created a CVS group 'cvsl10n' and all translators will be asked
to open Fedora accounts and will be added to this group.
As a Docs project, we have the choice *not* to wait for F7 and migrate the
translation process right away. The 'fp.org -> i18n -> fp' process for PO
files
is tedious for quaid and stickster. This means that translations for Docs will
happen in the Docs repository, which is much easier for translators (as long as
they have a Fedora account).
If there is no objection, we can apply the 'cvsl10n' ACLs on the po directory
right away and test the translator's access. The L10n team will try its best to
make sure we get as much translations as possible, even if our po files will be
hosted on a different SCM than the rest of the Fedora apps.
Comments?
-d
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
4:48 p.m.
Dimitris Glezos wrote:
Hey all.
Today we had a lengthy discussion on IRC about the way we should handle
translations in Fedora. The plan is basically to move applications (and their PO
files) that are being developed on elvis (a RH server) over to
'cvs.fedoraproject.org'. It seems that this will not happen before the F7
release.
We have already created a CVS group 'cvsl10n' and all translators will be asked
to open Fedora accounts and will be added to this group.
As a Docs project, we have the choice *not* to wait for F7 and migrate the
translation process right away. The 'fp.org -> i18n -> fp' process for PO
files
is tedious for quaid and stickster. This means that translations for Docs will
happen in the Docs repository, which is much easier for translators (as long as
they have a Fedora account).
If there is no objection, we can apply the 'cvsl10n' ACLs on the po directory
right away and test the translator's access. The L10n team will try its best to
make sure we get as much translations as possible, even if our po files will be
hosted on a different SCM than the rest of the Fedora apps.
I can get started on this soon, are there any objections / questions?
-Mike
6:52 p.m.
On Wed, 2007-03-07 at 22:37 +0000, Dimitris Glezos wrote:
Hey all.
Today we had a lengthy discussion on IRC about the way we should handle
translations in Fedora. The plan is basically to move applications (and their PO
files) that are being developed on elvis (a RH server) over to
'cvs.fedoraproject.org'. It seems that this will not happen before the F7
release.
We have already created a CVS group 'cvsl10n' and all translators will be asked
to open Fedora accounts and will be added to this group.
As a Docs project, we have the choice *not* to wait for F7 and migrate the
translation process right away. The 'fp.org -> i18n -> fp' process for PO
files
is tedious for quaid and stickster. This means that translations for Docs will
happen in the Docs repository, which is much easier for translators (as long as
they have a Fedora account).
If there is no objection, we can apply the 'cvsl10n' ACLs on the po directory
right away and test the translator's access. The L10n team will try its best to
make sure we get as much translations as possible, even if our po files will be
hosted on a different SCM than the rest of the Fedora apps.
Comments?
+1
Many translators have made the move to get a Fedora account already. We
risk losing a few people who might have translated through elvis/i18n
CVS, but IMO it is a low risk. We also may gain some translators
because of the publicity or the move-toward-fedoraproject.org (which
matters to some people.)
We have agreement to completely migrate off elvis when F7 is out, so the
translators are doing themselves a favor to get a FAS account now.
- Karsten
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
11:06 p.m.
O/H Karsten Wade έγραψε:
On Wed, 2007-03-07 at 22:37 +0000, Dimitris Glezos wrote:
> Hey all.
>
> Today we had a lengthy discussion on IRC about the way we should handle
> translations in Fedora. The plan is basically to move applications (and their PO
> files) that are being developed on elvis (a RH server) over to
> 'cvs.fedoraproject.org'. It seems that this will not happen before the F7
release.
>
> We have already created a CVS group 'cvsl10n' and all translators will be
asked
> to open Fedora accounts and will be added to this group.
>
> As a Docs project, we have the choice *not* to wait for F7 and migrate the
> translation process right away. The 'fp.org -> i18n -> fp' process for
PO files
> is tedious for quaid and stickster. This means that translations for Docs will
> happen in the Docs repository, which is much easier for translators (as long as
> they have a Fedora account).
>
> If there is no objection, we can apply the 'cvsl10n' ACLs on the po
directory
> right away and test the translator's access. The L10n team will try its best to
> make sure we get as much translations as possible, even if our po files will be
> hosted on a different SCM than the rest of the Fedora apps.
>
> Comments?
+1
Done and tested: Members of the 'cvsl10n' group now have read-write access in
`/cvs/docs/*/po/` but read-only access in the rest of the Docs dirs.
I believe it would be good if we give translators a list of recommendations on
what to translate and the priority of that translation. For example, `homepage`
is of very high priority (highly visible, small), one should translate the PO
inside the `devel` directory but also FC-6 (and notify us if we really need to
push an update) and it would be OK to do it now because it will get very few
changes before the release. These are a lot of information for each of our docs,
but I think such a page with detailed information for all our Docs would be
highly beneficial for all. The only page related to what I mention is
'/wiki/Docs'.
Here's a list of things we might want to consider listing for each of our Docs:
* Name
* Short name
* Target audience
* Maintained at
* Published at
Translation-specifics:
* Exposure / priority
* Need to translate also non-devel branch? (ie, will it be republished?)
* Start translating at
* Stop translating at
Do you think this is unnecessary, not rational? Comments?
I've also prepared a very quick page for new translators, over at:
http://fedoraproject.org/wiki/L10N/Join
Please make any corrections & suggestions before we announce it.
did-you-know-that Q of the day
------------------------------
Did you know that...
...probably more than 2500 people have contributed translations to the Fedora
Project? People with access on Fedora CVS are about 1200.
-d
Many translators have made the move to get a Fedora account already.
We
risk losing a few people who might have translated through elvis/i18n
CVS, but IMO it is a low risk. We also may gain some translators
because of the publicity or the move-toward-fedoraproject.org (which
matters to some people.)
We have agreement to completely migrate off elvis when F7 is out, so the
translators are doing themselves a favor to get a FAS account now.
- Karsten
--
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
8:11 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK WITH ME
- --
- - --
Nicolas A. Corrarello, RHCE c: +54 (911) 6398-5974
Fedora Ambassador Argentina e: ncorrare(a)fedoraproject.org
GPG Key: DFC893EE h:
http://www.fedoraproject.org/wiki/NicolasCorrarello
GPG Fingerprint: 5C93 42DA 98E1 4EEF B24B 7F8C E145 B2F9 DFC8 93EE
Import my key: $ gpg --keyserver pgp.mit.edu --recv-key 0xDFC893EE
Learn. Network. Experience open source.
Red Hat Summit San Diego | May 9-11, 2007
Learn more: http://www.redhat.com/promo/summit/2007
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFF8BmJ4UWy+d/Ik+4RAo+ZAJ9ZSG0KlHf+EvJGpjwkSuYhezdV4wCgxjQ4
HFUQqB2C34kjugNkuck3p6E=
=6GGR
-----END PGP SIGNATURE-----
6244
days inactive
6254
days old
4 comments
4 participants
participants (4)
-
Dimitris Glezos -
Karsten Wade -
Mike McGrath -
Nicolas A. Corrarello