Meeting Details

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

• • Proposed Next Steps: Algorithmic, peer, then determine popular badges
    • Luke and Brian Brennan to connect re: technical integration
    • Open design challenge--templatized design challenge
    • February brown bag

• • Identifying Badges
    • Proposed badges
    • Badge design bug
    • Questions about webdev community badges
  • 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)
  • Other badge efforts in Mozilla
    • SUMO badges - driver, Roland Tanglao with Madalina Ana and Rosana Ardila
    • Badge concepts from Sean Martell for IT bagdges: http://cl.ly/image/1e3t0h1F093t and http://cl.ly/image/403E170C3t0J
    • Web Literacies -- https://wiki.mozilla.org/Learning/WebLiteracies

• 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

• David/Emily to follow up with John about next steps with badge design challenge
• Emily to connect Luke with Brian from MoFo badge team
• Luke, Ricky, Ben to go through open questions from badge questionaire
• Luke to look into pulling data out of github for badges
• Emily to put roadmap together for phase 1
• David to change webdev contribute invite to every week through March 1