Ubuntu Forums Lucid Roadmap

Roadmap

• OBJECTIVE: Upgrade forums software to vBB 4.0

• SUCCESS CRITERIA: Successful upgrade of software with little disruption for users

• ACTIONS:

  • Notify users of upgrade (Forums Council)
  • Upgrade of software (Ryan Troy)
  • Convert custom templates to vBB 4.0

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Ryan Troy

• OBJECTIVE: Monthly Reports

• SUCCESS CRITERIA: Insightful and on-time report produced monthly by Forums Council

• ACTIONS:

  • Make easy to edit template for reports
  • Find someone to fill FC secretary to assist in reports

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Mike Basinger (Forums Council on item 2)

• OBJECTIVE: Include freenode webchat links to Forums Council meetings

• SUCCESS CRITERIA: Promote use of freenode webchat to increase participation from Fourm member who are unfamiliar with IRC

• ACTIONS:

  • Publishize webchat links before Forums Council meetings

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Mike Basinger

• OBJECTIVE: Better communications between Forums and Canonical IS

• SUCCESS CRITERIA: Quick and responsive communications between Forums and Canonical IS

• ACTIONS:

  • Find good communication channel
  • Address and security concerns

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Forums Council and Canonical IS

• OBJECTIVE: Better transparency between FC and community

• SUCCESS CRITERIA: Provide transparent as possible forums governance

• ACTIONS:

  • Monthly Reports
  • Communicate to other council lists of bans and why.
  • Item.

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Forums Council

• OBJECTIVE: Lucid Lynx Forum Support

• SUCCESS CRITERIA: Provide any extra support needed for the Lucid Lynx forum.

• ACTIONS:

  • Provide proper moderation support for this forum
  • Make proper channels get testing requests from developers to user
  • Get any requested feedback from forums to developers

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Mike Basinger

• OBJECTIVE: Forum-Launchpad Link Part II

• SUCCESS CRITERIA: Make LP-Forums link two way

• ACTIONS:

  • Make the forum<->LP link two way

• BLUEPRINT: https://blueprints.edge.launchpad.net/ubuntu/+spec/forum-council-lucid-plans

• DRIVER: Forums Council and LP Team

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 LoCo 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 LoCo 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.

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.