Building off of the previous milestone, the tasks performed by contributors should result in the construction of their Mozilla ‘resume’. In that scenario, to provide better understanding of their accom- plishments, the aim is to build a badges and titles system that corresponds with a rewards hierarchy that offers community members properly deﬁned rewards based on their efforts.
Build up tools to increase retention and lower attrition in Contributor Involvement
|P1||Integrate a Achievements/Badging service into the phonebook|
|P1||Build up a leveling system for contributors per sub-community|
|P2||...any P3 priorities not achieved|
|P1||Integrate with Badge/Achievements/Leveling|
P2: Events Manager
|P1||Users can see events from other sub-communities (i.e. aggregated from QMO, AMO, SUMO, etc.)|
|P1||Filter by Levels|
Community Data and Visualization
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.
|Determine the growth our community||
|Determine new contributor characteristics per community||
|Increase current contributor involvement||
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community to greater numbers and activity. Phase 4 will be heavily promoted to Students and Industry workers using paraphernalia with our recruiting team and continuing promotions to our existing user and contributor engagement channels.
|Web Services w/ user accounts||
|User/product services and pages||
|Events (fliers, emails, signup stations..)||
|Job Fairs/ Recruiting/ college fairs||
To support this learning and development plan, we'll need to build out programs to mature and guide new, casual and active contributors to become core contributors and leaders. To do that, Mozilla will need to either build out internally or partner with external educational institutions, trade groups and skill building organizations and programs.