Contribute/Webdev/Group 03 04 13

Meeting Details

• Meeting time: Monday, March 4 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
  • Launching phase 1 on March 8?
    • Schedule: https://openbadges.etherpad.mozilla.org/web-dev-badges
  • Designs done
  • Pulling data from Github done (see https://github.com/mozilla/webdev-contributors)
  • Issuing site done (see http://badges.mozilla.org)
    • Any blocker bugs come up during testing?
  • API to automate adding Github data to badges.mozilla.org?
  • Integration with mozillians.org? (see https://bugzilla.mozilla.org/show_bug.cgi?id=680209)
  • Preparing for creating 2013 plan for badges at Community Building meetup in March
  • Future phases
    • Proposed phases: Algorithmic, peer, then determine popular badges
    • Discuss questions about webdev community badges
    • Creating a spreadsheet with relevant metadata for each badge
      • Spreadsheet template we can use
    • 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 follow up with John about getting final versions of badge designs

• Luke to enter new badges into badges.mozilla.org when designs are done

• Les to put API up this week and Luke to look at updating data script to talk with API

• Ben to test on production version of badges.mozilla.org to verify it's ready to go

• David to bump integration with mozillians.org into phase 2

• Emily to update schedule to go live with badges on March 19

• David to add templates and roll-out to next agenda

• Emily to bring up questions about design of badges site after phase 1