Contribute/Webdev/Group 07 01 13

From MozillaWiki
Jump to: navigation, search

Meeting Details

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


  • Can we move this earlier to a more European friendly time?
  • Summit hacking idea
    • Proposal: Have a hacking session before the Summit to build new interactive History and/or Manifesto pages for use at Summit and create a hack in the box template for future webdev hack days
    • Lots of interest in our history and our identity at Summit Assembly
    • Next steps?
  • Webdev Badges
    • New badge ideas:
      • Mentor badge
      • Partner badges (ie, someone who has contributing pull requests to both Mozilla and other open source projects, like Code for America, Wikipedia, etc)
    • Other badge topics
        • Integrating badges into Webdev teams' workflow
        • Building out badges to be issued manually by Webdev team members (badges around mentoring, thanking, etc.)


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

  • Ben will check with Giorgos to see if he would attend these meetings if we moved the time to earlier in the day
  • Ricky to set up etherpad to brainstorm ideas about why/how to do webdev hackathons
  • Alex to send link to ReMo's AppDaysInABox guide as possible template for us to edit for webdev hackathons
  • Ben to send information about draft webprod stats he gathered to Annie on Metrics team who is looking into making a webdev contribution dashboard
  • David to remove reference to swag from webdev contribution points to avoid any confusion with contributors thinking we're sending out things we were just thinking about adding into the recognition process