Confirmed users
1,340
edits
Contribute/Webdev: Difference between revisions
no edit summary
No edit summary |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Webdev]] | |||
[[Category:Contribute]] | |||
=Steward= | =Steward= | ||
Mike Alexis, Ricky Rosario, Andrei Hajdukewycz (Sancus), Benjamin Sternthal, Anthony Ricaud and Luke Crouch | |||
=Webdev Contribute Group= | =Webdev Contribute Group= | ||
Meetings every other Monday at | Meetings every other Monday at 10:30 am pacific | ||
* | * [[Contribute/Webdev/Group_Meeting_Notes|Agenda and dial-in for next meeting and notes from previous meetings]] | ||
=Action Plan= | =Action Plan= | ||
| Line 32: | Line 33: | ||
Next register an account on bugzilla. Bugzilla can be daunting, so check out http://mzl.la/bugzilla_for_humans (15m video HIGHLY recommended). | 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 | 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! | Finally, with your mentor, fork the github repository for the bug's website and you're ready to start coding! | ||
| Line 54: | Line 55: | ||
A: | A: | ||
Suggestion: Use the [http://www.mozillians.org 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 [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf 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. | Suggestion: Use the [http://www.mozillians.org 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 [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf 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== | ==Define Contribution Opportunities== | ||
| Line 65: | Line 72: | ||
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. | 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== | ==Map Contribution Paths== | ||
| Line 80: | Line 91: | ||
3. Visit us on [http://irc.mozilla.org IRC] #sumodev and ask away<br> | 3. Visit us on [http://irc.mozilla.org IRC] #sumodev and ask away<br> | ||
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. | 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. | ||
| Line 96: | Line 110: | ||
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. | 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== | ==Relevant Bugs== | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=688911 Make it easier for contributors to get involved with web development at Mozilla] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=688911 Make it easier for contributors to get involved with web development at Mozilla] | ||
{{:Contribute/Webdev/Conversion_points}} | |||