4
edits
Stewards/Coding/Group 11 28 12: Difference between revisions
Stewards/Coding/Group 11 28 12 (view source)
Revision as of 21:37, 28 November 2012
, 28 November 2012no edit summary
(→Agenda) |
No edit summary |
||
| (7 intermediate revisions by one other user not shown) | |||
| Line 9: | Line 9: | ||
* [[Stewards/Coding/Group_11_21_12#Action_Items|Action items from last meeting]] | * [[Stewards/Coding/Group_11_21_12#Action_Items|Action items from last meeting]] | ||
* Community building workshops | |||
** Measuring and evaluating workshop on November 29 at 10 pacific ([https://blog.mozilla.org/community/2012/11/28/workshop-about-measuring-and-evaluating-contributions/ meeting details]) | |||
** Past workshops: [[Contribute/Workshops/Designing_for_participation|Designing your project for participation]] and [[Contribute/Workshops/Identifying_contributors|Identifying Contributors]] | |||
** 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 | ||
| Line 23: | Line 28: | ||
*** Leverage ratio | *** Leverage ratio | ||
*** Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703]) | *** Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703]) | ||
* Coding community manager | * Coding community manager | ||
| Line 63: | Line 62: | ||
==Action Items== | ==Action Items== | ||
* David to talk to Metrics team about improving organization of components and changing default filter in patch dashboards | |||
* David to talk to Kyle to see if patch size data is included in Bugzilla Anthropology data | |||
* Josh to show prototype of script to get data for use in nominating people to receive shirts | |||
* Graeme to work on prototype for creating badges for people contributing to specific releases | |||
==Notes== | |||
* David: last community building workshop tomorrow; we can evaluate next week whether the workshops could be repeated for other audiences (eg. work week) | |||
* David: patch dashboards are now public: https://blog.mozilla.org/community/2012/11/26/coding-contribution-dashboards-now-available/ | |||
* David: collecting feedback; what should we prioritize when talking to Metrics? | |||
* Josh & Benjamin: prioritize getting better module categorization (possibly bugzilla components instead) and better default filter | |||
* Benjamin: community manager hiring process - phone screening in process, interesting conversations happening (contributing as gamification, for example) | |||
* Josh: prototyping new contributor first patch notifier; read in data from git on a regular schedule, keep database of commits, find new contributors that appear - should have demo in one week | |||
* Benjamin: prototyping holding entire bugzilla database (without actual patches) in memory, allowing near-instant queries; should be able to be pretty open about it eventually. Will allow for must easier exploration of bugzilla data than current Elastic Search-based Bugzilla Anthropology project | |||
* Graeme: thinking about automated badges for "contributed to FF release N"; prototype at http://www.graememcc.co.uk/badger/ ([http://www.graememcc.co.uk/2012/11/28/open-badges-for-contributions-to-specific-firefox-releases/ Blog post]) | |||
* David: could we use this for automatic about:credits additions? | |||
* Benjamin: from phone conversations with candidates: interest in tying contributions to rapid release; show that this person's first patch was in release X | |||
* David: we could publicize this better (community blog, release notes, ...?) and celebrate it | |||