Engagement/Creative/Community: Difference between revisions
< Engagement | Creative
Jump to navigation
Jump to search
(Created page with "No Pixels Left Behind Goal: Set up a sustainable community of contributors around creative. General approach: 1. Open our processes and make ourselves more available for consul...") |
No edit summary |
||
| Line 1: | Line 1: | ||
No Pixels Left Behind | ==No Pixels Left Behind== | ||
Goal: Set up a sustainable community of contributors around creative. | Goal: Set up a sustainable community of contributors around creative. | ||
General approach: | =General approach:= | ||
1. Open our processes and make ourselves more available for consultation to support and encourage current Mozillians. | 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. | 2. Improve efforts to broaden the scale and reach of our design community. | ||
Immediate Action: | =Immediate Action:= | ||
* Communicate our activity through existing channels (such as commmunity marketing call, email list, etc) | * 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 | * Introduce the team, let people know where to find us and how to get in touch | ||
* Be better bloggers | * Be better bloggers | ||
By August 15: | =By August 15:= | ||
* Introduce toolkit - find out what people think about the draft and what else people would need to make it useful | * 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) | * Better Mozilla Creative Collective cultivation (weeding out spam) | ||
| Line 19: | Line 19: | ||
* Work with ReMo team to set up design special interest group | * Work with ReMo team to set up design special interest group | ||
By September 30: | =By September 30:= | ||
* Unveil and publicize brand toolkit as a live website | * Unveil and publicize brand toolkit as a live website | ||
* Launch the first of a regular series of quarterly MCC design challenges | * Launch the first of a regular series of quarterly MCC design challenges | ||
| Line 25: | Line 25: | ||
* Solidify copywriting/l10n process | * Solidify copywriting/l10n process | ||
By December 31: | =By December 31:= | ||
* Update MCC to make it more of a team HQ/community hub: | * Update MCC to make it more of a team HQ/community hub: | ||
** integrate more info about the team (profiles, projects, office hours, etc) | ** integrate more info about the team (profiles, projects, office hours, etc) | ||
Revision as of 17:59, 18 July 2011
No Pixels Left Behind
Goal: Set up a sustainable community of contributors around creative.
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.
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