Meeting Details

• Meeting time: Monday, October 29 at 10: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

Agenda

• Review action items for last meeting
  • metrics for Webdev canned response email links
  • Jay Clark now helping with Webdev vagrant stuff! (PR 652 and 656)
    • Sent him some MDN stickers for doing MDN. Now he's moving on to Socorro.

• Community metrics
  • Click throughs on auto-response: 82 clicks on 341 auto-responses last month -- more activity than replies was suggesting (note that the bit.ly links only track 2 of the 3 links in the message)
  • Finalizing Webdev conversion metrics and adding related recognition points

• Updating auto-response and Webdev Get Involved page with Webmaker/Firefox OS information

• MozCamp Asia session proposals
  • Sancus: evolving the Contributing to Mozilla Websites session from MozCamp Europe
  • Ricky: getting web developers involved in Firefox OS

• 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

• 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)
    • Rearranging webdev Get Involved page to surface easier opportunities first (Ben)
    • Firebug + Firediff for easy CSS hacking without needing to install site (Sancus)
    • Installable VM for Bedrock (bug 486363) (Luke)
  • 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

Placeholder

• 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 http://whatcanidoformozilla.org/ 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

• Giorgos to look into getting some rough conversion numbers from Github about contributor activity

• David to get Webdev auto-response updated on mozilla.org