Stewards/Coding/AgendaDump
From MozillaWiki
Huge list of previous agenda items
- Community dashboards
- Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs:
- Data about number of mentored bugs resolved fixed sorted by mentor (as proxy to learn who outstanding mentors are to then capture learnings to share with other mentors)
- Coding activity dashboards based on query to search for work done by non MoCo email addresses in certain time period
- Mentored bugs to return to pool of available contributors based on query for mentored bugs with an assignee who has not touched it in >2 weeks
- 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
- Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs:
- Recognition plans for contributors
- Webdev badges live on badges.mozilla.org
- Report back on usefulness of Award API for badge automation and Gear store form
- Mapping recognition items to conversion points
- This may need some updating? https://wiki.mozilla.org/Stewards/Coding/Rewards
- Coding Community Tools
- Training missions
- What Can I Do For Mozilla?
- Bugs Ahoy
- Mach
- Academic institutions
- Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program
- 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?
Place holders
- Coordinating with other contribution funnels
- QA, Metrics, Support? Others?
- 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?
- 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/)
