Contribute/Webdev/Group 11 04 13
From MozillaWiki
< Contribute | Webdev
Meeting Details
- Meeting time: Monday, November 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
- Improving visibility of opportunities
- Featuring projects or tasks didn't seem to move the needle
- Testing if featuring mentors would be helpful
- Josh's new Mentor Watch dashboard could help us measure impact
- Metrics
- David reached out to Nigel B about monthly new webdev contributors report
- Could go in new 'Introducing New Volunteers' section of All Hands meetings
- Webdev hackathons
- Luke to draft template
- willkg also looking to do a webdev hack session at Summit that could serve as a template
- Next step will be to try it out and document how it went
Placeholder
- 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.)
- New badge ideas:
- 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
- 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
- Ben to host a featured webdev mentor office hours before our next call
- Mike to put together some information on being a good mentor
- David to follow up with Nigel B about a new webdev contributors report