Contribute/Webdev: Difference between revisions
Groovecoder (talk | contribs) (→Tools) |
|||
| Line 15: | Line 15: | ||
===Channels=== | ===Channels=== | ||
* 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=== | ===Tools=== | ||
Revision as of 18:10, 2 March 2012
Steward
Christie Koehler, Andy McKay, Rob Helmer, Tim Watts, Les Orchard, Mike Alexis, Anthony Ricaud and Luke Crouch
Webdev Contribute Group
Meetings every other Monday at 1:30 pm pacific
- Next meeting: Contribute/Webdev/Group_03_12_12
- Notes from previous meetings
Action Plan
Goals
Channels
- 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 http://mzl.la/webdev_mentored_bugs 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
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.
Define Contribution Opportunities
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
A:
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.
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
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:
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.