Meeting Details

• Meeting time: Monday, October 1 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

• Webdev get involved page
  • Review Ben's edits
  • Discuss linking to Webmaker and web development related Firefox OS tasks on wiki page and webdev auto-response
  • https://etherpad.mozilla.org/contribute-webdev-response

• MozCamp Asia
  • Submit proposal for updated version of Contributing to Mozilla Websites session from MozCamp Europe?

• Tulsa Webdev hack day
  • Preparing contribution opportunities (Bedrock tasks?)
  • 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

• Community metrics
  • Tracking effectiveness of reducing barriers to entry
  • Next steps with Webdev conversion metrics
  • Is there a need for a more in depth Webdev dashboard beyond the conversion points?

• 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?

• Anything else?

Action Items

• Sancus to post bug for Inspector patch feature and we'll discuss resourcing options if it's not priority for Dev Tools team

• Ben to add getting started info and David to add Webmaker/Firefox OS info to Webdev Get Involved page

• Sancus and Ricky to submit MozCamp proposals for webdev sessions

• David to reach out to mrz and Corey and copy Luke about finding IT volunteers to help maintain install READMEs for websites

• Luke to pull mzl.la link stats from current auto-response

• David to add forking Github repo to webdev path