BOF_fridge-and-news-team
4792
Comment: trivial formatting
|
2626
fixed another formatting item and removed help instructions which improves readability
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
== RoadMap == | |
Line 6: | Line 7: |
== Building Your Roadmap == Each goal in the roadmap has a set structure which you should stick to. This is how it works: * '''Objective''' - An Objective is a goal that you want to achieve. Summarize your objective here in one sentence (e.g. 'Exhibit Ubuntu at OSCON' and 'Create Lucid Marketing Materials'). * '''Success Criteria''' - This is a statement that can be clearly read to determine success on the above 'Objective'. This needs to be as clear as possible and not vague: it will indicate if you achieved the 'Objective' (e.g. 'A successful exhibition at OSCON' and 'Lucid website buttons, banner ads and wallpaper provided for Lo``Co Teams'). * '''Actions''' - This is a set of steps that need to be executed to achieve the 'Objective'. It is recommended that if someone volunteers to commit to delivering on an action, you put it in brackets (e.g. 'Print out Lo``Co logo on a banner (Jono Bacon)'). There can be multiple actions for each Objective. * '''Blueprint (optional)''' - It is recommended to use a launchpad blueprint for your objective. Launchpad isn't just for developers, but is also great for community tasks. * '''Driver (optional)''' - If someone is coordinating this objective and helping those involved to deliver on their actions, list that person here. If you're using a blueprint it's especially convenient to mark the driver as the Drafter and Assignee of the launchpad blueprint. ## * '''Objective'''' ## * '''Success Criteria''' ## * '''Actions''' ## * Actions ## * Actions ## * Actions ## * Actions ## * '''Blueprint (optional)''' ## * '''Driver (optional)''' === Tracking Progress === Here are some tips on tracking progress on your roadmap: * Review it at meetings - your roadmap should be an agenda item at every meeting your team has. Review progress, identify problems, ensure everyone is clear on what they are doing and unblock blockers. * Review mid-cycle - it could be useful to review progress on the roadmap halfway through the cycle in detail. * Evaluate at the end of a cycle - when the cycle is complete, review the roadmap and see how much the team achieved. === RoadMap === * '''Objective'''' - Migrate Fridge to Word``Press |
* '''Objective''' - Migrate Fridge to Word``Press |
Ubuntu News Team - Discussion and Planning of NEW WordPress Fridge
RoadMap
Objective - Migrate Fridge to WordPress
Success Criteria - Fridge will utilize WordPress rather than Drupal
Actions - Canonical (Joey)
to migrate earlier Fridge content to new WordPress Fridge
- New Fridge Theme Based on New Ubuntu "light" Theme
Current Fridge Editors trained on Imput procedures for new WordPress Fridge
- Fridge Content to be adjusted based on "Information Radiator" model
Blueprint (optional) - https://blueprints.launchpad.net/fridge/+spec/community-m-fridge-and-news-team
Driver (optional) - Joey Stanford
Objective - Re-Design of Content on Fridge
Success Criteria - Implementation accepted ideas
Actions - Review Ideas for Content Restructure and implement accepted ideas
- Ubuntu Community at a Glance - community form...what the dev teams are doing, loco teams...etc....toward the release - semi-graphic showing a title, a status indicator, and holding a link for more information
- to be able to embed images and video
- link to the forum is a pita - better/faster way to get information to the Forums
- a way for non-team members to post to the Fridge for approval Fridge Team - suggestion to have x number of news team members review and ack or nack it for a successful peer review model so community material written specifically for the Fridge.
- Separate Links to Various Calendars
Calendar for Meetings held in -Meetings (If LoCa, Classroom, and FOSSEvents Calenders/Links are added the we will need to leave wording for what the Fridge Calendar is for or change wording based on implementation or non-implementation of suggested Calendars/Links added to Fridge)
Calendar for LoCo Team IRC meetings and events Calendar
LoCo Calendar would need to be created (short term)
If possible this Calendar could be linked or Pull information from/to LoCo Directory (Long Term Goal)
LoCo Team leaders/contacts as well as Newsletter and Fridge Editors
- Calendar for Sessions held in -classroom
- Link to FOSSEvents.com Calendar
Blueprint (optional) - https://blueprints.launchpad.net/fridge/+spec/community-m-fridge-and-news-team
Driver (optional) - TBD
UbuntuWeeklyNewsletter/RoadMap/BOF_fridge-and-news-team (last edited 2010-05-11 11:31:58 by 217)