From Fedora Project Wiki
Line 24: | Line 24: | ||
|- | |- | ||
| Work with docs to get notes/handouts prepared, if required for events|| 1 week || Three weeks | | Work with docs to get notes/handouts prepared, if required for events|| 1 week || Three weeks | ||
|- | |||
| Work with translate team to have docs in every language|| 1 week || Three weeks | |||
|- | |- | ||
| Last date of submission of release events requiring funding || - || one week before release | | Last date of submission of release events requiring funding || - || one week before release |
Revision as of 12:51, 25 June 2010
Fedora Ambassadors Schedule
Task Name | Required time | Deadline |
Work with marketing for creating talking points | As per their schedule | |
Send out call for release events and media production | 1 day | One and a half months before the release |
Regional meetings on Swag/media production, choose point of contact | 15 days | one month before release |
Funding request submission for swag production | - | Three weeks before release |
FAmSCo meeting for reviewing and clearing the event/swag requests | 1 | One week before the release |
Work with infrastructure for making the ISO available to Point of Contact immediately after GA staging | - | On GA staging |
Work with design for making the media/sticker artwork available | 2 days | One week |
Work with docs to get notes/handouts prepared, if required for events | 1 week | Three weeks |
Work with translate team to have docs in every language | 1 week | Three weeks |
Last date of submission of release events requiring funding | - | one week before release |
Arrange for a couple of IRC sessions for ambassadors on the new release | two classroom sessions | One week |
Work with marketing on the release events | After release | |
Last date of release event and report | One month after release |