Stewards/Coding/Group 11 28 12: Difference between revisions
Jump to navigation
Jump to search
(→Agenda) |
No edit summary |
||
| Line 24: | Line 24: | ||
* Community dashboards | * Community dashboards | ||
** | ** Patch dashboards now public! | ||
*** | *** Ideas for enhancements: Add patch size to get some information for comparison? Ratios of submitted vs approved vs commited patches? | ||
*** | ** Other dashboards in the works | ||
* | *** Mentored bugs graphs | ||
** | *** [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc&invite=CKfXqpEO Conversion tracking] | ||
** Leverage ratio | *** Leverage ratio | ||
*** | *** Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703]) | ||
* Rewards process for contributors | * Rewards process for contributors | ||
Revision as of 20:59, 27 November 2012
Meeting Details
- Meeting time: Wednesday, November 28 at 11 AM Pacific
- Video: David's vidyo room (use this link for guest access)
- Audio: If video doesn't work, call +1 800 707 2533, pin 369, conf 9634#
- Back channel: #planning
Agenda
- Community building workshops
- Designing your project for participation
- Identifying Contributors
- Measuring and evaluating workshop on November 29 at 10 pacific
- Is there any value in running these workshops at Engineering work weeks? Would be around 3-4 hours for all 3.
- Coding community manager
- Community Manager, Firefox Engineering posted
- Setting community managers up for success
- Identifying coding areas with needs for community management -- Firefox OS, webdev, education liaison, ???
- Community dashboards
- Patch dashboards now public!
- Ideas for enhancements: Add patch size to get some information for comparison? Ratios of submitted vs approved vs commited patches?
- Other dashboards in the works
- Mentored bugs graphs
- Conversion tracking
- Leverage ratio
- Metrics API (bug 729703)
- Patch dashboards now public!
- Rewards process for contributors
- Are we able to pull out information about people who have submitted patches to feed into Gear Store?
- Defining other recognition points on coding path
- Mentored bug for creating gear nominations to use at gear.mozilla.org
- https://wiki.mozilla.org/Stewards/Coding/Rewards
- Coding Community Tools
- What Can I Do For Mozilla?
- Creating a promo and finding places to promote it on Mozilla sites like MDN and other sites like Stackoverflow (bug 775771)
- Bugs Ahoy
- Mach
- Are we able to see how this has helped people in the conversion metrics we have?
- What Can I Do For Mozilla?
Place holders
- Academic institutions
- Move forward with just mailing list: https://lists.mozilla.org/listinfo/education
- Clean up references to Google Groups and newsgroup versions of forum that aren't linked anymore
- Any next steps with student-project keyword?
- Creating a case study that would promote this work and make it easier to duplicate?
- Using community dashboards
- Measure effectiveness of first patch approved email when conversion tracking in place
- Contributor survey once we have information about conversion path