Engagement/Creative/Community: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 4: Line 4:
=== General approach:  ===
=== General approach:  ===


1. Open our processes and make ourselves more available for consultation to support and encourage current Mozillians. 2. Improve efforts to broaden the scale and reach of our design community.  
* Open our processes and make ourselves more available for consultation to support and encourage current Mozillians.  
* Improve efforts to broaden the scale and reach of our design community.  


=== Immediate Action:  ===
=== Immediate Action:  ===

Latest revision as of 18:07, 18 July 2011

No Pixels Left Behind

Goal: Set up a sustainable community of contributors around creative.

General approach:

  • Open our processes and make ourselves more available for consultation to support and encourage current Mozillians.
  • Improve efforts to broaden the scale and reach of our design community.

Immediate Action:

  • Communicate our activity through existing channels (such as commmunity marketing call, email list, etc)
  • Introduce the team, let people know where to find us and how to get in touch
  • Be better bloggers

By August 15:

  • Introduce toolkit - find out what people think about the draft and what else people would need to make it useful
  • Better Mozilla Creative Collective cultivation (weeding out spam)
  • Set up regular "office hours" in IRC
  • Host one live design project with Sean Martell
  • Work with ReMo team to set up design special interest group

By September 30:

  • Unveil and publicize brand toolkit as a live website
  • Launch the first of a regular series of quarterly MCC design challenges
  • Blog at least three creative projects (per quarter) to encourage awareness and participation
  • Solidify copywriting/l10n process

By December 31:

  • Update MCC to make it more of a team HQ/community hub:
    • integrate more info about the team (profiles, projects, office hours, etc)
    • set up MCC job board
    • add public bug list of projects that could use help
    • link to toolkit
  • Integrate MCC into other relevant Mozilla properties (ex. phone book, personas)
  • MCC designer meet-up
  • Facilitate design events such as creative mornings at various MozSpaces, or other appropriate sponsorships