Stewards/Coding/Group 03 06 13: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Meeting Details= * Meeting time: Wednesday, March 6 at 11 AM Pacific * Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this lin...") |
No edit summary |
||
Line 50: | Line 50: | ||
* Academic institutions | * Academic institutions | ||
** Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program | ** Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program | ||
Place holders | |||
* Coordinating with other contribution funnels | * Coordinating with other contribution funnels | ||
Line 55: | Line 57: | ||
* Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects | * Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects | ||
* Videos | * Videos |
Revision as of 19:54, 27 February 2013
Meeting Details
- Meeting time: Wednesday, March 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 dashboards
- Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs
- Potential data analysis contribution opportunities
- Splitting out R- and R+ from review and retention dashboards and comparing time from R+ to closing bug fixed
- Measure effectiveness of patch approved email and other changes like releasing Mach
- Patch size vs. review time -- patch data to be added to Bugzilla Anthropology
- Mentored bugs graphs
- Conversion tracking
- Leverage ratio of coding employees and volunteers
- Investigating the use of the Metrics API (bug 729703)
- New contributor dashboards/metrics for portions of the tree (eg. gfx/, dom/, whatever)
- Get engineers to tag nontrivial bugs with common annotation (eg. [complex]). Write a tool that watches for successful resolution of these bugs and adds assignee to list of promising contributors.
- Other topics
- Working with Bitergia on analysis project?
- Enhancements for patch dashboards in Metrics' goals for Q1
- Clarifying types of starter bugs
- Surveying contributors who stop contributing
- Can we segment who we reach out to? People who made one patch vs. more than one patch?
- What information do we want to find out? Can we work with User Research to craft the right questions?
- Recognition plans for contributors
- Mapping recognition items to conversion points
- Making use of Gear store and badges
- This may need some updating? https://wiki.mozilla.org/Stewards/Coding/Rewards
- Coding Community Tools
- Infrastructure
- Is it possible to host the tools we're building on Mozilla servers?
- Is mozillalabs.com still an option?
- How do we garden all this stuff -- thoughts on a coding community building portal?
- Is it possible to host the tools we're building on Mozilla servers?
- Academic institutions
- Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program
Place holders
- Coordinating with other contribution funnels
- QA, Metrics, Support? Others?
- Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects
- Videos
- Reprise of Josh's FOSDEM presentation
- https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu
- Experiments
- The mobile team is experimenting with posting a "featured bug" (http://lucasr.org/2012/12/07/featured-bug-1-in-firefox-for-android/)
Action Items
- Mike to get public data ready for posting and we can look at then creating a data analysis contribution landing page
- Mike to post thoughts on improving experience with different types of starter bugs
- Mike to look into ability to host sites on mozillalabs.com domain
- David to connect Mike with Katherine about the Student Reps' Classroom Toolkit idea