Stewards/Coding/Group 12 05 12: Difference between revisions
Jump to navigation
Jump to search
(→Agenda) |
(→Agenda) |
||
| Line 11: | Line 11: | ||
* Community building workshops | * Community building workshops | ||
** | ** [[Contribute/Workshops/Designing_for_participation|Designing your project for participation]] | ||
** [[Contribute/Workshops/Identifying_contributors|Identifying contributors]] | |||
** [[Contribute/Workshops/Metrics_for_growth|Metrics for growth]] | |||
** Is there any value in running these workshops at Engineering work weeks? Would be around 3-4 hours for all 3. | ** Is there any value in running these workshops at Engineering work weeks? Would be around 3-4 hours for all 3. | ||
* Community dashboards | * Community dashboards | ||
*** Enhancements for patch dashboards | *** Enhancements for patch dashboards | ||
** Other dashboards in the works | ** Other dashboards in the works | ||
*** http://www.joshmatthews.net/swagger/health.html | |||
*** http://www.joshmatthews.net/swagger/index.cgi | |||
*** Patch size vs. review time -- [https://projects.mozilla.org/browse/METRICS-1290 patch data to be added to Bugzilla Anthropology] | *** Patch size vs. review time -- [https://projects.mozilla.org/browse/METRICS-1290 patch data to be added to Bugzilla Anthropology] | ||
*** Mentored bugs graphs | *** Mentored bugs graphs | ||
Revision as of 20:12, 4 December 2012
Meeting Details
- Meeting time: Wednesday, December 6 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
- Metrics for growth
- Is there any value in running these workshops at Engineering work weeks? Would be around 3-4 hours for all 3.
- Community dashboards
- Enhancements for patch dashboards
- Other dashboards in the works
- http://www.joshmatthews.net/swagger/health.html
- http://www.joshmatthews.net/swagger/index.cgi
- Patch size vs. review time -- patch data to be added to Bugzilla Anthropology
- Mentored bugs graphs
- Conversion tracking
- Leverage ratio
- Metrics API (bug 729703)
- 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, ???
- Rewards process for contributors
- jdm's prototype for contributor first patch notifier to feed into Gear Store for sending shirts
- graememcc's prototype for tool to issue badges to people contributing to a specific Firefox release
- Could also use for adding info about new contributors for that release to release notes, automating credits additions, content for Spotlights, Friend of Tree?
- Defining other recognition points on coding path
- 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