Meeting Details

• Meeting time: Monday, December 10 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

• Action items from last meeting

• Webdev contribution badges pilot
  • Introductions from MoFo Badges team
    • Web Literacies -- https://wiki.mozilla.org/Learning/WebLiteracies
  • Data and tools
    • List of webdev repositories on Github to track -- https://etherpad.mozilla.org/webdev-github-repositories
    • Pull Webdev activity information from Github data (Giorgos/Luke)
      • jdm's Swagger prototype that pulls coding data out of Git
    • Security review of https://badgus-dev.allizom.org -- bug 797857 (Les)
    • What are the badges -- https://wiki.mozilla.org/Contribute/Conversion_points#Webdev
  • Etherpad for questions about community badges: https://mozlearning.etherpad.mozilla.org/webmaker-community-badges
  • Other badge efforts in Mozilla
    • Badge concepts from Sean Martell for IT bagdges: http://cl.ly/image/1e3t0h1F093t and http://cl.ly/image/403E170C3t0J

• 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

Placeholder

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

• Luke to send out Carla's list of questions about badges to dev-webdev list and we'll go over responses at next meeting

• Emily and David to make a case study of this pilot to help other teams with badge efforts

• David to help coordinate among other community builders interested in badges