I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
As an added bonus I've also created a combined view with the Documentation schedule (notice the overlay in different colors). The intention if this version is to place the Translation tasks in the context of the rest of the release: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.ht...
And if that wasn't enough, I'm also generating iCal files for this release that are team specific. So pop this into to your favorite calendar application and tell me which additional tasks you'd like to see or have removed. To keep the presentation clean it only includes the more important tasks/milestones. --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-translation.ics
It would be most helpful to get your feedback as soon as possible. If I don't hear anything by Friday I will assume these are done.
One other question... who is representing the Translation team at the "Release Readiness Meetings" for Fedora 12? It was disappointing not to have representation from the translation team for the Fedora 11 preview and final release readiness meeting or the Fedora 11 retrospective.
Thank you, John
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
John, thanks for taking the initiative to do this! Here are some notes:
- Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
- 16 Translate Release Notes (POT to PO): We better name this "Translate Beta Release Notes" for clarity.
Besides the fact that we have too many translation periods for the various project components, which is definitely hard to track, I think the schedule rocks.
-d
On Tue, Jul 21, 2009 at 05:23:38PM +0300, Dimitris Glezos wrote:
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
John, thanks for taking the initiative to do this! Here are some notes:
Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only
requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
- 16 Translate Release Notes (POT to PO): We better name this
"Translate Beta Release Notes" for clarity.
Besides the fact that we have too many translation periods for the various project components, which is definitely hard to track, I think the schedule rocks.
Dimitris, thanks for your input on the schedule. I was hoping that we would also have someone from the L10n team who could commit to being present at the release readiness meetings. If you want to do that, fantastic -- but I'd also understand if you wanted to make way for someone else in the group to step up into this liaison role.
There are only a few of these meetings per cycle. The meetings help us ensure that all the teams working on a Fedora release have everything they need from each other, and that no one is blocked (knowingly or not) by something unforeseen. We would really appreciate having someone from the L10n group there to make sure this team's needs are being considered and met!
Paul W. Frields さんは書きました:
On Tue, Jul 21, 2009 at 05:23:38PM +0300, Dimitris Glezos wrote:
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
John, thanks for taking the initiative to do this! Here are some notes:
Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only
requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
- 16 Translate Release Notes (POT to PO): We better name this
"Translate Beta Release Notes" for clarity.
Besides the fact that we have too many translation periods for the various project components, which is definitely hard to track, I think the schedule rocks.
Dimitris, thanks for your input on the schedule. I was hoping that we would also have someone from the L10n team who could commit to being present at the release readiness meetings. If you want to do that, fantastic -- but I'd also understand if you wanted to make way for someone else in the group to step up into this liaison role.
There are only a few of these meetings per cycle. The meetings help us ensure that all the teams working on a Fedora release have everything they need from each other, and that no one is blocked (knowingly or not) by something unforeseen. We would really appreciate having someone from the L10n group there to make sure this team's needs are being considered and met!
I wished to attend the last meeting and I am sorry missed it. On that date I got personal matter and unable to change the schedule. Thank you for reminding us! noriko
Dimitris Glezos さんは書きました:
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
John, thanks for taking the initiative to do this! Here are some notes:
Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only
requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
- 16 Translate Release Notes (POT to PO): We better name this
"Translate Beta Release Notes" for clarity.
Sorry coming late, John, could you please check these as well?
* Please add "Software" at the beginning for easy identification 6. Start Rebuild all translated packages => Software Start Rebuild all translated packages 7. Rebuild all translated packages => Software Start Rebuild all translated packages
* Just to be consistent the above mentioned by Dimitris, this entry also better to include "Beta". 8. Translation Deadline: Release Notes (PO Files complete) => Translation Deadline: Beta Release Notes (PO Files complete)
* Which team is in charge to send off 'Banner'? This can make us to track the schedule in case the file is not coming on time. 18. Translate Final Release Banners (POT to PO)
* I am suspecting that this is part of "15 Translation Period for Website". If so then it has deadline and review entries with 19 and 20, so this entry can be removed. 22. Translation Deadline: fedoraproject.org (PO done)
Now let me be a little greedy for F12, is there any translation task from Ambassadors Team?
noriko
Besides the fact that we have too many translation periods for the various project components, which is definitely hard to track, I think the schedule rocks.
-d
Noriko Mizumoto said the following on 07/23/2009 07:24 PM Pacific Time:
Sorry coming late, John, could you please check these as well?
- Please add "Software" at the beginning for easy identification 6. Start Rebuild all translated packages => Software Start Rebuild all translated packages 7. Rebuild all translated packages => Software Start Rebuild all translated packages
Done
- Just to be consistent the above mentioned by Dimitris, this entry also
better to include "Beta". 8. Translation Deadline: Release Notes (PO Files complete) => Translation Deadline: Beta Release Notes (PO Files complete)
Done
- Which team is in charge to send off 'Banner'? This can make us to
track the schedule in case the file is not coming on time. 18. Translate Final Release Banners (POT to PO)
The design team creates the banners.
- I am suspecting that this is part of "15 Translation Period for
Website". If so then it has deadline and review entries with 19 and 20, so this entry can be removed. 22. Translation Deadline: fedoraproject.org (PO done)
I changed a few other things since the original version was published. Does something still need to be fixed?
Now let me be a little greedy for F12, is there any translation task from Ambassadors Team?
I'm not sure I understand your question. Does the Ambassadors team help with translations? We do not currently have the Ambassadors group as part of the master schedule.
I think I've addressed everyone's comments now. Please continue to let me know what isn't working or what needs to be fixed. As I hope you are seeing... this gets less and less painful each release because of the iterative changes we make :)
John
John Poelstra さんは書きました:
- I am suspecting that this is part of "15 Translation Period for
Website". If so then it has deadline and review entries with 19 and 20, so this entry can be removed. 22. Translation Deadline: fedoraproject.org (PO done)
I changed a few other things since the original version was published. Does something still need to be fixed?
Checked. Please remove this entry, it is confusing. This date is not deadline. 20. Translation Deadline: Website 2009-10-27
Please rename this entry, this is the deadline for Websites. 24. Translation Deadline: fedoraproject.org (PO done) 2009-11-02 => Translation Deadline: Websites (POs done) 2009-11-02
F11 Websites translation included 'fedoraproject.org', 'fedorahosted' and 'talk.fedoraproject.'.
Now let me be a little greedy for F12, is there any translation task from Ambassadors Team?
I'm not sure I understand your question. Does the Ambassadors team help with translations? We do not currently have the Ambassadors group as part of the master schedule.
Software translation comes from Devel team, Rel-note & Guides translation come from Docs team, Websites translation comes from Web team and Banner translation comes from Design team. So just I was wondering if any translation needs around in Ambassadors team :-)
I think I've addressed everyone's comments now. Please continue to let me know what isn't working or what needs to be fixed. As I hope you are seeing... this gets less and less painful each release because of the iterative changes we make :)
Yes, indeed. Thank you so much for you great work!
Thanks a lot noriko
Noriko Mizumoto said the following on 07/27/2009 08:35 PM Pacific Time:
John Poelstra さんは書きました:
- I am suspecting that this is part of "15 Translation Period for
Website". If so then it has deadline and review entries with 19 and 20, so this entry can be removed. 22. Translation Deadline: fedoraproject.org (PO done)
I changed a few other things since the original version was published. Does something still need to be fixed?
Checked. Please remove this entry, it is confusing. This date is not deadline. 20. Translation Deadline: Website 2009-10-27
Done
Please rename this entry, this is the deadline for Websites. 24. Translation Deadline: fedoraproject.org (PO done) 2009-11-02 => Translation Deadline: Websites (POs done) 2009-11-02
Done
F11 Websites translation included 'fedoraproject.org', 'fedorahosted' and 'talk.fedoraproject.'.
Dimitris Glezos said the following on 07/21/2009 07:23 AM Pacific Time:
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
I have built the Fedora 12 Translation schedules using the same methodology from Fedora 11.
Please tell me what needs to be corrected, added, or changed by referencing the task number here: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-trans-tasks.html
John, thanks for taking the initiative to do this! Here are some notes:
Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only
requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
I believe we've always had string freeze happen on the same day as Beta Freeze (starting in Fedora 12, Alpha Freeze).
What dates would you suggest instead for Fedora 12?
- 16 Translate Release Notes (POT to PO): We better name this
"Translate Beta Release Notes" for clarity.
Done
Besides the fact that we have too many translation periods for the various project components, which is definitely hard to track, I think the schedule rocks.
-d
On Mon, Jul 27, 2009 at 10:31 PM, John Poelstrapoelstra@redhat.com wrote:
Dimitris Glezos said the following on 07/21/2009 07:23 AM Pacific Time:
On Tue, Jul 21, 2009 at 5:11 AM, John Poelstrapoelstra@redhat.com wrote:
- Software String Freeze 2009-08-04
This decision is up to RelEng probably (or FESCo). The only requirement from L10n is that it should be 1 month before the Software Translation Deadline (PO Files complete) Tue 2009-09-15. Now its almost 1.5 months, and I think it's too much for developers to handle.
I believe we've always had string freeze happen on the same day as Beta Freeze (starting in Fedora 12, Alpha Freeze).
What the heck, let's keep it then.
I'd send an email to fedora-devel, just in case.
-d
John Poelstra wrote:
As an added bonus I've also created a combined view with the Documentation schedule (notice the overlay in different colors). The intention if this version is to place the Translation tasks in the context of the rest of the release: --> http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.ht...
There are basically five different Fedora projects FLP team work on: - Software localization - Guides localization - Release Notes localization - Website localization - Release banner localization
We got good results in the previous releases of Fedora with respect to localization as we got aligned properly with the master Fedora schedule and worked together with other teams. So, the schedule prepared for Fedora 12 using the same methodology from earlier releases is currently meeting FLP teams expectations, no doubt about that! However, during Fedora 11, I realized (after getting feedbacks from colleagues working on translations of Fedora projects) a need to get few more things modified to the Translation (or master) schedule that can ease FLP members' job to meet their goal to provide quality localization of Fedora projects. I think FLP schedule will require (if all FLP members agree) following modifications:
* For software localization - We have got 42 days for translation before package rebuild starts. Is it possible to split this translation task in two phases (Translation - 30 days and Review - 12 days)? If we split it this way and put the package rebuild step between these two tasks, FLP members will get a chance to test and review Fedora packages on their local machine and can provide a better localization during the Review period. So, the concern here is to concentrate on *review* of Fedora software applications. - Another important thing is, we (FLP members) are most of the time clueless whether our translations has got in or not. We get to know only after the package rebuilds, if we find time on thorough testing. So, how about having some automated mechanism to notify FLP team that their translations has been included in the latest package rebuild? This could be done if we setup some automation that can send a notification e-mail to fedora-trans-announce list *at the end of the package rebuild period* that abc, xyz packages has been rebuilt in the period from *start package rebuild* to *end package rebuild*.
* For Guides localization - We need some time for the review say 5 days at least (not sure that's enough though) and we might want to follow same steps for guide packages as we do in software application packages
* For Release Notes & Website localization - as Dimtris said "beta release notes" at some places for better clarity - and we need HTMLs built automatically and should be available from some staging url where we can review the localization. (however, this may not be part of the schedule)
All are welcome to provide their inputs on the above modifications, so the concluded once can be brought to the fedora schedule meeting...
Regarding the presence of FLP representative in the meeting, I can join in if none of the FLSCo members are able to make it.
Thanks!
Ankitkumar Rameshchandra Patel said the following on 07/22/2009 11:01 PM Pacific Time:
<cut>
- For software localization
- We have got 42 days for translation before package rebuild starts. Is
it possible to split this translation task in two phases (Translation - 30 days and Review - 12 days)? If we split it this way and put the package rebuild step between these two tasks, FLP members will get a chance to test and review Fedora packages on their local machine and can provide a better localization during the Review period. So, the concern here is to concentrate on *review* of Fedora software applications.
- Another important thing is, we (FLP members) are most of the time
clueless whether our translations has got in or not. We get to know only after the package rebuilds, if we find time on thorough testing. So, how about having some automated mechanism to notify FLP team that their translations has been included in the latest package rebuild? This could be done if we setup some automation that can send a notification e-mail to fedora-trans-announce list *at the end of the package rebuild period* that abc, xyz packages has been rebuilt in the period from *start package rebuild* to *end package rebuild*.
Changed. Let me know if something is wrong.
- For Guides localization
- We need some time for the review say 5 days at least (not sure that's
enough though) and we might want to follow same steps for guide packages as we do in software application packages
I think there used to be a "review guides task" but nobody could tell me what it was so I dropped it. There was room in the schedule so I tacked the review period on to the initial translation period.
- For Release Notes & Website localization
- as Dimtris said "beta release notes" at some places for better clarity
- and we need HTMLs built automatically and should be available from
some staging url where we can review the localization. (however, this may not be part of the schedule)
Please tell me exactly which task numbers you would like me to change the descriptions on.
If HTML files need to be built for your work they should be on the schedule. 1) Who builds the HTML files? 2) When do they need to be built? 3) Which task (task number) comes after building the files? --if it is not already on the schedule please tell me the correct description so I can add it.
Thanks, John
All are welcome to provide their inputs on the above modifications, so the concluded once can be brought to the fedora schedule meeting...
Regarding the presence of FLP representative in the meeting, I can join in if none of the FLSCo members are able to make it.
Thanks!
<snip>
- For Release Notes & Website localization
- as Dimtris said "beta release notes" at some places for better clarity
- and we need HTMLs built automatically and should be available from
some staging url where we can review the localization. (however, this may not be part of the schedule)
Please tell me exactly which task numbers you would like me to change the descriptions on.
If HTML files need to be built for your work they should be on the schedule.
- Who builds the HTML files?
- When do they need to be built?
- Which task (task number) comes after building the files? --if it is not already on the schedule please tell me the correct
description so I can add it.
Ankit and John Thank you for being eagle eyes! For Websites, review is scheduled here. Ricky usually takes care of us. 21. Review and correct Websites translations 27-Oct to 02-Nov
For Rel-note, the request has been sent in separate mail. Once we confirm the detail with docs team, it should go back to John for inclusion.
thanks noriko
Thanks, John
All are welcome to provide their inputs on the above modifications, so the concluded once can be brought to the fedora schedule meeting...
Regarding the presence of FLP representative in the meeting, I can join in if none of the FLSCo members are able to make it.
Thanks!
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 07/22/2009 11:01 PM Pacific Time:
<cut>
Thanks John for looking into this, otherwise the suggestions were almost lost in the threads. :)
I refer this schedule: http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.ht... in my reply.
- For software localization
- We have got 42 days for translation before package rebuild starts.
Is it possible to split this translation task in two phases (Translation - 30 days and Review - 12 days)? If we split it this way and put the package rebuild step between these two tasks, FLP members will get a chance to test and review Fedora packages on their local machine and can provide a better localization during the Review period. So, the concern here is to concentrate on *review* of Fedora software applications.
- Another important thing is, we (FLP members) are most of the time
clueless whether our translations has got in or not. We get to know only after the package rebuilds, if we find time on thorough testing. So, how about having some automated mechanism to notify FLP team that their translations has been included in the latest package rebuild? This could be done if we setup some automation that can send a notification e-mail to fedora-trans-announce list *at the end of the package rebuild period* that abc, xyz packages has been rebuilt in the period from *start package rebuild* to *end package rebuild*.
Changed. Let me know if something is wrong.
Well, I was expecting task 19 and 20 to be *repeated* somewhere between task 5 and 11. Basically, I want the package rebuilds to happen before we start to review software translations, then only there is a point in dividing the translation task into Translation and Review.
- For Release Notes & Website localization
- as Dimtris said "beta release notes" at some places for better clarity
- and we need HTMLs built automatically and should be available from
some staging url where we can review the localization. (however, this may not be part of the schedule)
Please tell me exactly which task numbers you would like me to change the descriptions on.
If HTML files need to be built for your work they should be on the schedule.
- Who builds the HTML files?
- When do they need to be built?
- Which task (task number) comes after building the files? --if it is not already on the schedule please tell me the correct
description so I can add it.
Actually building of HTML files should happen every hour (or two or four or half a day) automatically through some cronjob. I think Ricky might be able to help us with it. It will not require to be there in the schedule I guess since it's going to be automated cronjob running periodically.
Ankitkumar Rameshchandra Patel said the following on 07/28/2009 04:48 AM Pacific Time:
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 07/22/2009 11:01 PM Pacific Time:
<cut>
Thanks John for looking into this, otherwise the suggestions were almost lost in the threads. :)
I refer this schedule: http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.ht... in my reply.
- For software localization
- We have got 42 days for translation before package rebuild starts.
Is it possible to split this translation task in two phases (Translation - 30 days and Review - 12 days)? If we split it this way and put the package rebuild step between these two tasks, FLP members will get a chance to test and review Fedora packages on their local machine and can provide a better localization during the Review period. So, the concern here is to concentrate on *review* of Fedora software applications.
- Another important thing is, we (FLP members) are most of the time
clueless whether our translations has got in or not. We get to know only after the package rebuilds, if we find time on thorough testing. So, how about having some automated mechanism to notify FLP team that their translations has been included in the latest package rebuild? This could be done if we setup some automation that can send a notification e-mail to fedora-trans-announce list *at the end of the package rebuild period* that abc, xyz packages has been rebuilt in the period from *start package rebuild* to *end package rebuild*.
Changed. Let me know if something is wrong.
Well, I was expecting task 19 and 20 to be *repeated* somewhere between task 5 and 11. Basically, I want the package rebuilds to happen before we start to review software translations, then only there is a point in dividing the translation task into Translation and Review.
I'm still not following.
Forgive me if I tweaked something that threw off the task numbers... task 19 and 20 is: Translate Final Release Banners (POT to PO) and Translation Deadline: Website
The best way for me to update/change the schedule is for you tell me explicitly what the tasks names are and what their dates should be (even if it repeats other parts of the schedule).
Thanks, John
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 07/28/2009 04:48 AM Pacific Time:
Well, I was expecting task 19 and 20 to be *repeated* somewhere between task 5 and 11. Basically, I want the package rebuilds to happen before we start to review software translations, then only there is a point in dividing the translation task into Translation and Review.
I'm still not following.
Forgive me if I tweaked something that threw off the task numbers... task 19 and 20 is: Translate Final Release Banners (POT to PO) and Translation Deadline: Website
The best way for me to update/change the schedule is for you tell me explicitly what the tasks names are and what their dates should be (even if it repeats other parts of the schedule).
Thanks, John
I refer this schedule page: http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.ht... for the changes I am requesting.
Following tasks 19. Software: Start Rebuild all translated packages 20. Software: Rebuild all translated packages
Should be somewhere between tasks 5. Final Software Translation Period (POT to PO) and 11. Review Software Translations as well as on their current place too.
I will stay online late over irc today, to explain the need of the above changes just in case it isn't clear.
Thanks!