Contribute/Webdev/Group 10 29 12: Difference between revisions
< Contribute | Webdev
Jump to navigation
Jump to search
(Created page with "=Meeting Details= * Meeting time: Monday, October 15 at 10:30 AM Pacific * Video: David Boswell's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA u...") |
No edit summary |
||
| Line 39: | Line 39: | ||
*** Is Bugzilla right first step / needed at all with focus on Github? | *** Is Bugzilla right first step / needed at all with focus on Github? | ||
** Tracking effectiveness of reducing barriers to entry | ** Tracking effectiveness of reducing barriers to entry | ||
'''Placeholder''' | |||
* Creating a workflow for how to handle webdev inquiries | * Creating a workflow for how to handle webdev inquiries | ||
Revision as of 18:27, 1 October 2012
Meeting Details
- Meeting time: Monday, October 15 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
- Webdev get involved page
- Review additional edits to add getting started intro section and Webmaker/Firefox OS information
- Updating auto-response to stay in sync: https://etherpad.mozilla.org/contribute-webdev-response
- MozCamp Asia session proposals
- Sancus: evolving the Contributing to Mozilla Websites session from MozCamp Europe
- Ricky: getting web developers involved in Firefox OS
- 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
- 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)
- Rearranging webdev Get Involved page to surface easier opportunities first (Ben)
- Firebug + Firediff for easy CSS hacking without needing to install site (Sancus)
- Installable VM for Bedrock (bug 486363) (Luke)
- 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
- Community metrics
- Finalizing Webdev conversion metrics
- Added forking repo as step
- Is Bugzilla right first step / needed at all with focus on Github?
- Tracking effectiveness of reducing barriers to entry
- Finalizing Webdev conversion metrics
Placeholder
- 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?