Contribute/Webdev/Group 09 23 13: Difference between revisions
< Contribute | Webdev
Jump to navigation
Jump to search
(Created page with "=Meeting Details= * Meeting time: Monday, September 23 at 10:30 AM Pacific * Video: David Boswell's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPn...") |
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 12: | Line 15: | ||
* Improving visibility of opportunities | * Improving visibility of opportunities | ||
** Creating a Featured Project section on the [[Webdev/GetInvolved|Webdev Get Involved page]] | ** Creating a Featured Project section on the [[Webdev/GetInvolved|Webdev Get Involved page]] | ||
** | ** How will we measure success? Number of mentored bugs fixed? Time for someone to take a mentored bug? Something else? | ||
* Webdev hackathons | * Webdev hackathons | ||
| Line 60: | Line 63: | ||
==Action Items== | ==Action Items== | ||
Latest revision as of 09:24, 27 September 2014
Meeting Details
- Meeting time: Monday, September 23 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
- Creating a Featured Project section on the Webdev Get Involved page
- How will we measure success? Number of mentored bugs fixed? Time for someone to take a mentored bug? Something else?
- 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
- Community building systems
- How to build a community around the community building systems we need?
- Metrics
- Webdev contribute dashboard is on Metric team's Q3 list
- Blackhole may also be something we could use to get data
- Additional automated badges will need to wait until we have better Metrics
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?