Meeting Details

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

• Sending swag to contributors

• Webdev Badges
  • Revisiting the badges.mozilla.org landing page to cover all Mozilla badge activities (David/Emily)
    • Draft design brief
    • Do we continue discussions here or do we want to include the wider set of community builders through the Recognition Working Group?
  • Integrating badges into Webdev teams' workflow
  • Building out badges to be issued manually by Webdev team members (badges around mentoring, thanking, etc.)
  • Future phases in Q3/Q4
    • Measuring effectiveness of badges and path analysis of Webdev contributors

• Building capacity
  • Ben's notes on efforts to building capacity for working with volunteers in Webprod
  • Using those notes as more effective way to run these regular meetings
  • Planning to do outreach for other groups after we work with Ben

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

• David to follow up with Luke, Ricky and Les about moving discussion about badges.mozilla.org design brief to a place where more Community Builders will be able to take part

• David to contact people interested in a Recognition Working Group about getting together to refine and move forward with design brief

• David to meet with Carla and Sunny to discuss MoCo goals process and how it aligns with MoFo's process to help identify resources for badges.mozilla.org design effort