Contribute/Webdev/Group 04 01 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Meeting Details= * Meeting time: Monday, April 1 at 10:30 AM Pacific * Video: David Boswell's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use ...")
 
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[Category:Webdev/Meetings]]
[[Category: Meeting Notes]]
[[Category:Contribute]]
=Meeting Details=
=Meeting Details=


Line 17: Line 20:
** Revisiting the badges.mozilla.org landing page to cover all Mozilla badge activities (David/Emily)
** Revisiting the badges.mozilla.org landing page to cover all Mozilla badge activities (David/Emily)
** Roll out of integrating badges into other webdev teams' processes and creating templates for other teams (Ben/Emily)
** Roll out of integrating badges into other webdev teams' processes and creating templates for other teams (Ben/Emily)
** Future phases
** Any other badges to add -- for example, badges for mentoring bugs?
*** Any other badges to add -- for example, badges for mentoring bugs?
** Measuring effectiveness of badges
*** Measuring effectiveness of badges
** Integration with mozillians.org (see https://bugzilla.mozilla.org/show_bug.cgi?id=680209)
*** Integration with mozillians.org (see https://bugzilla.mozilla.org/show_bug.cgi?id=680209)
** Proposed phases: Algorithmic, peer, then determine popular badges
*** Proposed phases: Algorithmic, peer, then determine popular badges
** Discuss [https://etherpad.mozilla.org/webdev-community-badges questions about webdev community badges]
*** Discuss [https://etherpad.mozilla.org/webdev-community-badges questions about webdev community badges]
** Creating a spreadsheet with relevant metadata for each badge
*** Creating a spreadsheet with relevant metadata for each badge
*** [https://docs.google.com/spreadsheet/ccc?key=0AnUOR-0CBMsTdDhBLUFpTnp2TC1fMW1YWmp2WkNKc1E&usp=sharing#gid=1 Spreadsheet template we can use]
**** [https://docs.google.com/spreadsheet/ccc?key=0AnUOR-0CBMsTdDhBLUFpTnp2TC1fMW1YWmp2WkNKc1E&usp=sharing#gid=1 Spreadsheet template we can use]
** Tying into Web Literacies -- https://wiki.mozilla.org/Learning/WebLiteracies
*** Tying into Web Literacies -- https://wiki.mozilla.org/Learning/WebLiteracies
 
** Logistics: Keep meeting every week or go back to every other week?


'''Placeholder'''
'''Placeholder'''
Line 53: Line 57:
==Action Items==
==Action Items==


* Luke to create badges on badges.mozilla.org using final artwork
* No meeting due to travel and holiday
 
* Ricky to finish updating script to talk to Awards API using a general Webdev team email instead of his own
 
* David to schedule on call on Wednesday to decide if we are ready to launch and will cancel next week's meeting due to conflict with Community Builders meetup

Latest revision as of 09:01, 27 September 2014

Meeting Details

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

Agenda

    • Logistics: Keep meeting every week or go back to every other week?

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

  • No meeting due to travel and holiday