Stewards/Coding/Group 02 27 13: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Meeting Details= * Meeting time: Wednesday, February 27 at 11 AM Pacific * Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
* Community dashboards | * Community dashboards | ||
** Working with [http://blog.bitergia.com/2012/07/19/the-project-metrics-grimoire-started/ Bitergia] on analysis project? | ** Working with [http://blog.bitergia.com/2012/07/19/the-project-metrics-grimoire-started/ Bitergia] on analysis project? | ||
** Next steps with Kyle's review charts -- split out R- and R+ and compare time from R+ to closing bug fixed | ** Next steps with Kyle's review charts -- split out R- and R+ and compare time from R+ to closing bug fixed | ||
**** https://metrics.mozilla.com/bugzilla-analysis/Community_NextReviews.html | **** https://metrics.mozilla.com/bugzilla-analysis/Community_NextReviews.html | ||
| Line 29: | Line 26: | ||
*** New contributor dashboards/metrics for portions of the tree (eg. gfx/, dom/, whatever) | *** 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. | *** 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. | ||
* Clarifying types of starter bugs | |||
** [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.planning/-8NNf269VGw Thread on dev.planning] | |||
* Surveying contributors who stop contributing | * Surveying contributors who stop contributing | ||
| Line 73: | Line 73: | ||
==Action Items== | ==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 | |||
Latest revision as of 19:44, 27 February 2013
Meeting Details
- Meeting time: Wednesday, February 27 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
- Working with Bitergia on analysis project?
- Next steps with Kyle's review charts -- split out R- and R+ and compare time from R+ to closing bug fixed
- https://metrics.mozilla.com/bugzilla-analysis/Community_NextReviews.html
- https://metrics.mozilla.com/bugzilla-analysis/Community_Retention.html
- Measure effectiveness of patch approveded email: https://projects.mozilla.org/browse/BA-90
- Other dashboards items
- Patch size vs. review time -- patch data to be added to Bugzilla Anthropology
- Mentored bugs graphs
- Conversion tracking
- Leverage ratio
- Metrics API (bug 729703)
- Enhancements for patch dashboards in Metrics' goals for Q1
- New ideas to discuss
- 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.
- 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
- Interactive timeline of contributions idea (bug 484416)
- Other ways to recognize (Friend of Tree, blog posts, etc.)
- This may need some updating? 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?
- Infrastructure
- Is it possible to host the tools we're building on Mozilla servers?
- How do we garden all this stuff -- thoughts on a coding community building portal?
- Coordinating with other contribution funnels
- QA, Metrics, Support? Others?
- 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?
- Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects
Place holders
- 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