View source for Contribute/Webdev/Group 09 09 13

[[Category:Webdev/Meetings]]
[[Category: Meeting Notes]]
[[Category:Contribute]]
=Meeting Details=

* Meeting time: Monday, September 9 at 10:30 AM Pacific
* Video: David Boswell's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA 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=

* [[Contribute/Webdev/Group_08_12_13#Action_Items|Action items from last meeting]]

* Coordinating with new [[ReMo/SIGs/Webdev|Mozilla Reps Web Development Special Interest Group]]

* Swag
** How to roll out swag best practices to webdev teams?  Ie, have standing agenda item in team calls

* Manifesto reboot
** Looking to code this with volunteers -- is this a chance for us to identify and recruit new webdev contributors?
** https://wiki.mozilla.org/Manifesto/Potential_Changes
** [https://app.smartsheet.com/b/publish?EQBCT=b6c3e90ef93841a0a34c9cb681adebf1 Draft schedule]

* Guide for volunteer resourced projects
** Do we want to create a document to use when talking to people about what it means to have a project delivered by volunteers instead of staff?  For example, flexibility on deadlines?

* Webdev hackathons
** Luke to draft template
** Next step will be to try it out and document how it went
** Not something we should try to tie into Summit

* Contribution opportunities
** Ben to report back about experience using community Kanban instead of wiki

* 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.)

* 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 ([https://bugzilla.mozilla.org/show_bug.cgi?id=766906 bug 766906]) (Rik)
*** Firebug + [https://addons.mozilla.org/en-US/firefox/addon/firediff/ 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==

* Ricky and Ben to add standing agenda item about recognizing contributors to their team's regular meetings

* Ben to experiment with creating a Featured Project section on the Webdev Get Involved page to increase visibility of contribution opportunities

* willkg is proposing a Hackathon for the Summit that we could use as a template