8:37 a.m.
Hi Dimitris,
I've read your answer about the zanata project.
I am still trying to clean our Fedora projects at TXN[1].
I've some bugzilla ticket around that would help. I still need to fill
lots about maintainers missing, but I don't have so much time ;).
I still have one question:
For projects not under any fedora releases (-web, -docs, -upstream nor
-main), should we create an other release like "fedora-archive" for
all projects under the Fedora Project hub but not currently in
translations? That would be projects under[2]. Those projects are for
example old guide really out to date that we don't want/need
translators to translate. of course, one project should be only in one
release.
Moreover, is there a quick way to go straight to the project page once
we are browsing a release? I mean, at [3] for example, we have all
resources in one page. It's far better if we want to translate the
burning iso guide for example to go at its own page[4]. In idea, on
the "actions_popup" div, that would be great to have a direct link to
its project page. (I should probably ask that with the suggestion
tool…).
[1] https://fedoraproject.org/wiki/User:Shaiton/trans
[2] https://fedoraproject.org/wiki/User:Shaiton/trans#Projects_under_the_F...
[3] https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/l/en/
[4] https://fedora.transifex.net/projects/p/fedora-readme-burning-isos/
--
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2
8:56 a.m.
On Fri, Mar 30, 2012 at 3:37 PM, Kévin Raymond
<shaiton(a)fedoraproject.org> wrote:
Hi Dimitris,
I've read your answer about the zanata project.
I am still trying to clean our Fedora projects at TXN[1].
I've some bugzilla ticket around that would help. I still need to fill
lots about maintainers missing, but I don't have so much time ;).
I still have one question:
For projects not under any fedora releases (-web, -docs, -upstream nor
-main), should we create an other release like "fedora-archive" for
all projects under the Fedora Project hub but not currently in
translations? That would be projects under[2]. Those projects are for
example old guide really out to date that we don't want/need
translators to translate. of course, one project should be only in one
release.
Moreover, is there a quick way to go straight to the project page once
we are browsing a release? I mean, at [3] for example, we have all
resources in one page. It's far better if we want to translate the
burning iso guide for example to go at its own page[4]. In idea, on
the "actions_popup" div, that would be great to have a direct link to
its project page. (I should probably ask that with the suggestion
tool…).
My bad :) Reading the source code of the page I just found that the
title is actually a link to this project… So nice, forget about this
last request ;)
[1] https://fedoraproject.org/wiki/User:Shaiton/trans
[2] https://fedoraproject.org/wiki/User:Shaiton/trans#Projects_under_the_F...
[3] https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/l/en/
[4] https://fedora.transifex.net/projects/p/fedora-readme-burning-isos/
--
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2
--
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2
9:06 a.m.
On Fri, Mar 30, 2012 at 4:37 PM, Kévin Raymond
<shaiton(a)fedoraproject.org> wrote:
I've read your answer about the zanata project.
I am still trying to clean our Fedora projects at TXN[1].
I've some bugzilla ticket around that would help. I still need to fill
lots about maintainers missing, but I don't have so much time ;).
Hi Kévin,
I think what you're doing is admirable. So important. {deep bow}
I still have one question:
For projects not under any fedora releases (-web, -docs, -upstream nor
-main), should we create an other release like "fedora-archive" for
all projects under the Fedora Project hub but not currently in
translations? That would be projects under[2]. Those projects are for
example old guide really out to date that we don't want/need
translators to translate. of course, one project should be only in one
release.
It's not clear to me what types of projects these are. If they are
projects which Fedora is not upstream for but are translated through
FTP, then maybe fedora-external is a good name. Stuff which are not
being translated because they are obsolete could be simply removed.
Moreover, is there a quick way to go straight to the project page
once
we are browsing a release? I mean, at [3] for example, we have all
resources in one page. It's far better if we want to translate the
burning iso guide for example to go at its own page[4]. In idea, on
the "actions_popup" div, that would be great to have a direct link to
its project page. (I should probably ask that with the suggestion
tool…).
Actually, translators probably just want to click one of the rows of
the table and not go to the project page. For example:
https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/l/el/
Furthermore, as you found out, the resource_action popup has a link to
the project details page, at the top side.
-d
[1] https://fedoraproject.org/wiki/User:Shaiton/trans
[2]
https://fedoraproject.org/wiki/User:Shaiton/trans#Projects_under_the_Fedo...
[3] https://fedora.transifex.net/projects/p/fedora/r/fedora-docs/l/en/
[4] https://fedora.transifex.net/projects/p/fedora-readme-burning-isos/
--
Dimitris Glezos
Social Localization Crowdsourcing
http://www.transifex.com/ -- http://angel.co/transifex
9:23 a.m.
On Fri, Mar 30, 2012 at 4:06 PM, Dimitris Glezos <glezos(a)transifex.com> wrote:
On Fri, Mar 30, 2012 at 4:37 PM, Kévin Raymond
<shaiton(a)fedoraproject.org> wrote:
> I've read your answer about the zanata project.
> I am still trying to clean our Fedora projects at TXN[1].
> I've some bugzilla ticket around that would help. I still need to fill
> lots about maintainers missing, but I don't have so much time ;).
Hi Kévin,
I think what you're doing is admirable. So important. {deep bow}
> I still have one question:
> For projects not under any fedora releases (-web, -docs, -upstream nor
> -main), should we create an other release like "fedora-archive" for
> all projects under the Fedora Project hub but not currently in
> translations? That would be projects under[2]. Those projects are for
> example old guide really out to date that we don't want/need
> translators to translate. of course, one project should be only in one
> release.
It's not clear to me what types of projects these are. If they are
projects which Fedora is not upstream for but are translated through
FTP, then maybe fedora-external is a good name. Stuff which are not
being translated because they are obsolete could be simply removed.
Ok, the fact are:
How one translator find something to translate? By browsing Fedora
releases (-docs, -websites, -main, -upstream). I don't think that
translators have to got to the "All resources" page[1], there are too
much projects there.
The problem about projects sourcing the Fedora Project Hub, is:
- An empty project which is not under any release could one day become
active. Ex with[2]. Then, maintainers would have to tell us that they
have updated their project and ask to join the fedora-docs release.
But we can't ask them to remember, they won't. Then the project would
be active and up to date but nobody would know about it.
- An obsolete project should be removed from the release. If we don't
track it, the above point is true, we won't know when it is going to
be alive again.
But then we will loose the difference between -uptream and -main… It
is not the best solution.
I have just came with a clever suggestion:
Keeping all projects under their respective release, and setting the
"under translation" flag to obsoleted projects. Then, we should have a
filter on the release page to filter out projects not currently under
translations (the statistics should also care about that, actually we
could see 12% translated when in fact 100% of the up to date resources
are translated).
Would it be possible? Do you think of an actual transifex feature that
could be used in that way?
[1] https://fedora.transifex.net/projects/p/fedora/r/all-resources/
[2] https://fedora.transifex.net/projects/p/fedora-software-mgmt-guide/
--
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2
4402
days inactive
4402
days old
3 comments
2 participants
participants (2)
-
Dimitris Glezos -
Kévin Raymond