Support/Goals/UpcomingReleasesEngagement

From MozillaWiki
Jump to: navigation, search

Motivation:

Frequent FF releases lead to a higher number of questions on the support forum and need for updates in the KB articles. The purpose of this goal is to create a buzz around product releases to get more contributors engaged in helping out.

Plan:

This needs to be done in several stages:

1. Create a schedule of all actions that need to be taken before and after a product release

  • 1nd week (after release)
    • wrap-up and conclusions on previous release
    • present updates on SUMO meeting
    • start working on the documentation for next release
  • 2nd week
    • work on documentation
  • 3rd week
    • work on documentation
  • 4th week
    • first blog post
    • initiate contributor topic on the forum announcing the release
    • present updates on SUMO meeting
  • 5th week (just before release)
    • initiate contributor topic on forum with top issues and call for feedback
    • initiate discussion on IRC channel
  • 6st week(release week)
    • reminder and call-to-action on SUMO meeting on Monday
    • post announcement for forum helpers with link to top issues as posted by Cheng
    • organize a SUMO day on Thursday with focus on release issues
    • blog post and call to action


2. Create communication templates for blog posts, tweets etc

3. Have back-up plan ready in case of delayed releases

4. Extra actions for big releases

    • create FB event
    • create a cheatsheet and send it to contributors
    • reach out to contributors personally
    • initiate discussion on IRC channel on release day
    • announce "release champions" and get them a merit badge/card
    • create video for call-to-action