Thanks for being patient with me as I get up to speed with the different tasks your teams perform and where they intersect. I am continually refining the wording of each task so it is hopefully clearer exactly what is being done. In the process I'm discovering more undocumented tasks that need to be completed to bridge tasks already on the schedule and also finding others that are unclear as to what they are. For example we say "translations due" but we don't say which translations they are... release notes, softare, documentation?
I am also trying to a better job of representing on each team's schedule which tasks THEY perform. For example the Documentation schedule lists only the tasks that docs is responsible for--not translation tasks too. The overall schedule shows combined tasks for all the teams if you're looking for a combined view.
On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby instance to add more details and corrections to the Fedora 10 translation schedule. Feel free to join in. If this turns out to be helpful I would like to do a similar exercise with the docs team if they are so interested.
Translation schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html
Docs schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html
John
John Poelstra wrote:
Thanks for being patient with me as I get up to speed with the different tasks your teams perform and where they intersect. I am continually refining the wording of each task so it is hopefully clearer exactly what is being done. In the process I'm discovering more undocumented tasks that need to be completed to bridge tasks already on the schedule and also finding others that are unclear as to what they are. For example we say "translations due" but we don't say which translations they are... release notes, softare, documentation?
I am also trying to a better job of representing on each team's schedule which tasks THEY perform. For example the Documentation schedule lists only the tasks that docs is responsible for--not translation tasks too. The overall schedule shows combined tasks for all the teams if you're looking for a combined view.
On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby instance to add more details and corrections to the Fedora 10 translation schedule. Feel free to join in. If this turns out to be helpful I would like to do a similar exercise with the docs team if they are so interested.
Translation schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html
Docs schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html
John
Hi John,
Thank you so much for closely working with the FLP & Docs team and sorting out the translation & documentation schedule related issues. These new schedules have made the roadmap pretty clear for FLP team I think.
I might not be able to join you in the meeting, though I wanted to.
So, let me request the last change I would like to see in the Documentation as well as translation schedule.
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
On Mon, Sep 29, 2008 at 02:49:46PM +0530, Ankitkumar Rameshchandra Patel wrote:
John Poelstra wrote:
Thanks for being patient with me as I get up to speed with the different tasks your teams perform and where they intersect. I am continually refining the wording of each task so it is hopefully clearer exactly what is being done. In the process I'm discovering more undocumented tasks that need to be completed to bridge tasks already on the schedule and also finding others that are unclear as to what they are. For example we say "translations due" but we don't say which translations they are... release notes, softare, documentation?
I am also trying to a better job of representing on each team's schedule which tasks THEY perform. For example the Documentation schedule lists only the tasks that docs is responsible for--not translation tasks too. The overall schedule shows combined tasks for all the teams if you're looking for a combined view.
On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby instance to add more details and corrections to the Fedora 10 translation schedule. Feel free to join in. If this turns out to be helpful I would like to do a similar exercise with the docs team if they are so interested.
Translation schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html
Docs schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html
John
Hi John,
Thank you so much for closely working with the FLP & Docs team and sorting out the translation & documentation schedule related issues. These new schedules have made the roadmap pretty clear for FLP team I think.
I might not be able to join you in the meeting, though I wanted to.
So, let me request the last change I would like to see in the Documentation as well as translation schedule.
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
These Docs tasks *should* be in the schedule, Ankit, you're quite correct. That's an oversight that we will get corrected as we work with John to overhaul his rendition of our schedule as well. Note that in the past they've always been on that schedule.
Part of the reason they're not there now is that in the past I had often drafted the next release's schedule on the wiki after some discussion with Docs folks. I wasn't able to do that post-F9 simply for lack of spare cycles. Now that Karsten has Fedora Docs as one of his job responsibilities he's able to carve more time for things like schedule debugging. I notice this is on the Docs Project task list:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings
Thanks for being attentive to this problem; I'm sure it can be resolved to everyone's benefit.
Ankitkumar Rameshchandra Patel said the following on 09/29/2008 02:19 AM Pacific Time:
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Yes, this part of my "revelation" last week :) We need to be very explicit with the task names both in the documentation schedule and the translation schedule.
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
I put it in the maintenance phase because that is when it occurs--after GA, which is when the maintenance of a release begins. Is there an important reason why you would like to have it in the "Launch Phases"?
John
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 09/29/2008 02:19 AM Pacific Time:
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Yes, this part of my "revelation" last week :) We need to be very explicit with the task names both in the documentation schedule and the translation schedule.
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
I put it in the maintenance phase because that is when it occurs--after GA, which is when the maintenance of a release begins. Is there an important reason why you would like to have it in the "Launch Phases"?
John
Let me explain what I understand about "0-day changes". I think "0-day changes to release notes" means, the last minute changes came to release-notes writers. Please correct me, if I am wrong.
So, If my understanding about "0-day changes" is correct, then "0-day changes" should be applicable to "POT generation", which is already taken care, as well as "Po translations" also, which is put in the maintenance phase. After (ideally. could be on the same date, though.) "0-day translation of PO" task "0-day release-notes build updated rpm" task should happen. So, basically end users (local language users) whould get the latest release notes.
I can see, following three entries in the http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html
0-Day rel-notes generate POT Tue 2008-11-25 Tue 2008-11-25 0 0-Day rel-notes update docs.fp.org Tue 2008-11-25 Tue 2008-11-25 0 0-Day rel-notes build updated rpm Tue 2008-11-25 Tue 2008-11-25 0 GA Release Tue 2008-11-25 Tue 2008-11-25 0 Maintenance Phase Wed 2008-11-26 Mon 2010-01-04 404 Add translated zero-day updates to docs.fp.org Mon 2008-12-08 Mon 2008-12-08 0.2
With respect to same "0 day release-notes updates" similar task should be found in http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html Maintenance Phase Wed 2008-11-26 Mon 2010-01-04 404 Translate 0-day release notes for docs.fp.org Wed 2008-11-26 Mon 2008-12-08 11.8
So, the point is, "Translate 0-day release notes for docs.fp.org" should be along with "0-Day rel-notes build updated rpm" as well. That means it should start and end on the same date "Wed 2008-11-26", which is currently starting "Wed 2008-11-26" and ending "Mon 2008-12-08".
On Tue, Sep 30, 2008 at 02:21:24PM +0530, Ankitkumar Rameshchandra Patel wrote:
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 09/29/2008 02:19 AM Pacific Time:
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Yes, this part of my "revelation" last week :) We need to be very explicit with the task names both in the documentation schedule and the translation schedule.
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
I put it in the maintenance phase because that is when it occurs--after GA, which is when the maintenance of a release begins. Is there an important reason why you would like to have it in the "Launch Phases"?
John
Let me explain what I understand about "0-day changes". I think "0-day changes to release notes" means, the last minute changes came to release-notes writers. Please correct me, if I am wrong.
It's really "changes to support 0-day update," which might make it clearer. Docs has to prepare the final Release Notes for the GA several weeks in advance so that composes can be tested, synced, etc. Invariably there will be material that pops up in the meantime which is important enough to have an update available for users to read on release day. So we do another round of content importing (not a lot, usually), issue a new POT, have a few days for translators to incrementally update the content, and publish package updates and Web content.
Paul W. Frields wrote:
On Tue, Sep 30, 2008 at 02:21:24PM +0530, Ankitkumar Rameshchandra Patel wrote:
John Poelstra wrote:
Ankitkumar Rameshchandra Patel said the following on 09/29/2008 02:19 AM Pacific Time:
Fedora Documentation team writes not only Release Notes but also guides like Installation Guide, Desktop User Guide, etc too. I wonder, why these documentation writing tasks are neither mentioned in Documentation schedule nor in translation schedule?
Yes, this part of my "revelation" last week :) We need to be very explicit with the task names both in the documentation schedule and the translation schedule.
Btw, I have got one more doubt. Why can't we put "Translate 0-day release notes for docs.fp.org" in the Launch phase as well, rather than in maintenance phase?
I put it in the maintenance phase because that is when it occurs--after GA, which is when the maintenance of a release begins. Is there an important reason why you would like to have it in the "Launch Phases"?
John
Let me explain what I understand about "0-day changes". I think "0-day changes to release notes" means, the last minute changes came to release-notes writers. Please correct me, if I am wrong.
It's really "changes to support 0-day update," which might make it clearer. Docs has to prepare the final Release Notes for the GA several weeks in advance so that composes can be tested, synced, etc. Invariably there will be material that pops up in the meantime which is important enough to have an update available for users to read on release day. So we do another round of content importing (not a lot, usually), issue a new POT, have a few days for translators to incrementally update the content, and publish package updates and Web content.
Thanks Paul!
It's clear to me now!
On Fri, 2008-09-26 at 17:17 -0700, John Poelstra wrote:
On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby instance to add more details and corrections to the Fedora 10 translation schedule. Feel free to join in. If this turns out to be helpful I would like to do a similar exercise with the docs team if they are so interested.
I should be able to lurk for that, might have some useful input, and then we can schedule one for Docs ASAP.
Muchos, muchos gracias for doing this, John. I'm doing a lot of fast work to step-up the quality of project management for Docs, and tight schedule integration is a key to that.
- Karsten
-
Ankit Patel -
John Poelstra -
Karsten Wade -
Paul W. Frields