Contribute/Webdev/Group 01 14 13
From MozillaWiki
< Contribute | Webdev
Meeting Details
- Meeting time: Monday, January 14 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
- Proposed phases: Algorithmic, peer, then determine popular badges
- Launching phase 1
- Luke and Brian Brennan to connect re: technical integration
- Pulling data out of selected Github repositories
- Open design challenge -- templatized design challenge
- John has committed to have designs ready for March 1 -- needs deliverable information (file type, size, etc.) and can we reuse Github icons?
- Les' badge generator tool could be useful for that -- http://static.lmorchard.com/art-maker/demo.html
- February 7 brown bag at Grow Mozilla discussion
- March 1 launch for phase 1
- Luke and Brian Brennan to connect re: technical integration
- Future phases
- Discuss questions about webdev community badges
- Security review of https://badgus-dev.allizom.org -- bug 797857 (Les)
- Tying into 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
- Top priorities
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
- Emily to follow up with contact at Github about icons
- Emily and David to follow up with John about next steps with design challenge
- Emily to post written roadmap by next Monday