Meeting Details

• Meeting time: Monday, March 11 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 Badges
  • Getting final designs (Emily)
  • Adding designs for each badge to badges.mozilla.org and creating criteria URL (Luke)
  • Testing Award API and updating script to automate adding Github data to badges.mozilla.org (Les/Luke)
  • Launching phase 1 on March 19 -- still on track?
    • Schedule: https://openbadges.etherpad.mozilla.org/web-dev-badges
  • Roll out of badges to other webdev teams and creating templates for other teams (Ben/Emily)
  • Future phases
    • Proposed phases: Algorithmic, peer, then determine popular badges
    • Integration with mozillians.org (see https://bugzilla.mozilla.org/show_bug.cgi?id=680209)
    • Discuss questions about webdev community badges
    • Creating a spreadsheet with relevant metadata for each badge
      • Spreadsheet template we can use
    • Design discussion for badges.mozilla.org
    • Tying into Web Literacies -- https://wiki.mozilla.org/Learning/WebLiteracies

Placeholder

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

• Emily to contact David Smiley for final artwork

• Luke to add final artwork to create badges on badges.mozilla.org

• Luke and Les to wrap up work with API and data script

• David and Ryan to talk about avoiding confusion with Open Badges launch