Steward

Mike Alexis, Ricky Rosario, Andrei Hajdukewycz (Sancus), Benjamin Sternthal, Anthony Ricaud and Luke Crouch

Webdev Contribute Group

Meetings every other Monday at 10:30 am pacific

• Agenda and dial-in for next meeting and notes from previous meetings

Action Plan

Goals

Channels

• Get Involved page on Webdev blog:
  • http://blog.mozilla.com/webdev/get-involved/

• One Mozilla footer will have a 'Would you like to edit this page?' link that will point to a page about how to get involved with webdev at Mozilla.
  • Background: http://davidwboswell.wordpress.com/2012/02/03/would-you-like-to-edit-this-page/
  • Current link like this on www.mozilla.org has generated substantial traffic (185,316 page views as of March 2, 2012)

Tools

Canned Response

Thanks for offering to help us build Mozilla's websites!

Start by joining us in #webdev on IRC. http://mzl.la/irc_getting_started will help you get connected, and http://mzl.la/webdev_irc lists some WebDev channels.

Next register an account on bugzilla. Bugzilla can be daunting, so check out http://mzl.la/bugzilla_for_humans (15m video HIGHLY recommended).

Now look for a WebDev mentored bug in https://wiki.mozilla.org/Webdev/GetInvolved and contact the mentor - over IRC, email, or comment on the bug.

Finally, with your mentor, fork the github repository for the bug's website and you're ready to start coding!

bit.ly bundle for links in Canned Response

https://bitly.com/bundles/mozillafoundation/9

Potential Contributors

Active Contributors

Core Contributors

• nigelb

Background Information

Identify Community

Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?

A:

Suggestion: Use the mozillians.org contributor directory to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the Mozillians dashboard will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.

A (SUMO):

SUMO - Staff: Ricky Rosario, Will Kahn-Greene, Tim Watts (part of his time), Tanay Gavankar (contractor/intern). Volunteer: Berker Peksag (irregular). We've had a couple other one- or two-commit contributors. Those are just code, are you also interested in QA? MDN - Staff: Luke Crouch, James Bennett, Les Orchard, Paul MacLanahan (part time), Craig Cook (part time). Volunteer: Buddy Lindsey, Manuel Strehl, Tanner Filip, Connor Montgomery. Community Tools - Staff: Dave Dash, Tim Watts (the rest of his time), a number of people from Flux, but I assume Fred will cover them. Volunteer: Nigel Babu.

Define Contribution Opportunities

Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?

A:

• Mentored bug list - http://mzl.la/webdev_mentored_bugs
• MDN - front-end coding with HTML & CSS!

Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.

A (SUMO):

We have lists of bugs, some marked Good First Bug. We're starting to use mentored bugs more.

Map Contribution Paths

Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?

A:

Kitsune

1. Fork it

2. We've put the documentation on ReadTheDocs

3. Visit us on IRC  #sumodev and ask away

A (SUMO):

We have done a lot of work to document installation and in some cases (MDN) to automate it via tools like Vagrant. There isn't much documentation on how to contribute code in a broader sense.

Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.

Establish Goals and Metrics

Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?

A:

• bit.ly bundle clicks (https://bitly.com/bundles/mozillafoundation/9)
• Read the Docs Webdev Bootcamp traffic (http://mozweb.readthedocs.org/en/latest/)
• GitHub forks (e.g., https://github.com/api/v2/json/repos/show/mozilla/kuma)
• GitHub Contributors (e.g., https://github.com/mozilla/kuma/contributors)
• Closed Mentored Bugs (e.g., http://mzl.la/mdn_mentored_closed)
• humans.txt (e.g., https://developer.mozilla.org/humans.txt)

Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.

A (SUMO): No, we don't have established goals right now, and I don't think we could realistically at the moment. Beyond "number of commits by non-paid authors" I don't think we have a metric in place.

Relevant Bugs

• Make it easier for contributors to get involved with web development at Mozilla

Conversion Points

• http://jsfiddle.net/groovecoder/p6HJN/