Contribute/Webdev/Group 05 20 13

From MozillaWiki
Jump to: navigation, search

Meeting Details

  • Meeting time: Monday, May 20 at 1:30 AM Pacific
  • Video: David Boswell'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: #webdev


  • Webdev Badges
    • Measuring effectiveness of badges and path analysis of Webdev contributors (Carla and Emily)
    • Adding a Mentor badge to current set of Webdev badges (we'll need to design it and get data out of Bugzilla)
      • Future badge topics
        • Integrating badges into Webdev teams' workflow
        • Building out badges to be issued manually by Webdev team members (badges around mentoring, thanking, etc.)
  • Building capacity
    • Question about what Metrics to track
      • Discussion with Annie on Webdev contribution dashboard plans
    • Ben to document capacity building effort to share with other teams
    • Webprod's community building kanban board
  • Summit hacking idea
    • Can we have a hacking session at the Summit to onboard new people onto Webdev projects and create a template for future webdev hack days?
    • Possible hacking project: interactive timeline of Mozilla


  • Reducing barriers for new contributors
    • Top priorities
      • How to contribute to a Mozilla web site screencast (Sancus)
      • Making contact and bug tracking information easier to find on sites (bug 766906) (Rik)
      • Firebug + Firediff for easy CSS hacking without needing to install site (Sancus)
    • Other ideas (need to prioritize)
      • Linking to the Github page template in footer of pages on Bedrock (Rik)
      • Improving documentation and clarifying how different sites have small but significant differences to be aware of
      • Reaching out to Petri team to see if they could help make it easier for front-end webdev contributors to access to a staging site
  • Tulsa Webdev hack day
    • Looking for mentors to prepare contribution opportunities and be available online during event
    • Using this as a template for Reps to run other webdev hack days
  • Creating a workflow for how to handle webdev inquiries
    • Documenting current workflow
    • Enhancing current process (follow back up with promising leads 2 weeks after first contact, recognizing volunteers with a public post or swag after finishing first mentored bug)
  • Piggybacking on other contributor efforts
    • Coding pathway: How to make use of and collaborate with Coding Stewards
    • Design pathway: Are there relevant CSS and web design contribution information to add to Design wiki page for design contributors?

Action Items

  • Annie to look into status of the creation of a simple Webdev contribution dashboard
  • Annie to let us know when there are more licenses available to share SUMO dashboard around to other community builders as a case study