Contribute/Graphics: Difference between revisions

Contribute/Graphics (view source)

Revision as of 22:27, 8 November 2011

621 bytes added , 8 November 2011

no edit summary

Bjacob

Confirmed users

753

edits

@@ Line 9: / Line 9: @@
 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.
+Joe Drew, Mozilla employee
+Jeff Gilbert, Mozilla employee
+Benoit Girard, Mozilla employee
+Florian Haenel, non-Mozilla-employee, employed by a german consultancy
+Benoit Jacob, Mozilla employee
+Ali Juma, Mozilla employee
+Chris Lord, Mozilla employee
+Jeff Muizelaar, Mozilla employee
+Oleg Romashin, non-Mozilla-employee, employed by Nokia
+JP Rosevear, Mozilla manager
+Bas Schouten, Mozilla employee
+Doug Sherk, Mozilla intern
+Matt Woodrow, Mozilla employee
+We don't really have any volunteer at the moment, at least until very recently. There are a few new people currently working on mentored bugs, but this is too recent to know if they'll stick around.
+There is a major volunteer contributor, Ms2ger, who works on Canvas stuff, but that's not really Graphics per se.
+We started https://wiki.mozilla.org/Platform/GFX/Meet already; will file bugs to get the Mozillians directory to cover all our needs.
 =Define Contribution Opportunities=
@@ Line 15: / Line 33: @@
 Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
-A:
+A: We started https://wiki.mozilla.org/Platform/GFX/Contribute already, with in particular [http://bit.ly/vpiHea this link] to find Graphics mentored bugs. So we're on track with that.
-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=
@@ Line 23: / Line 39: @@
 Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
-A:
+A: We're trying to document that on https://wiki.mozilla.org/Platform/GFX/Contribute .
-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=
@@ Line 31: / Line 45: @@
 Q: What goals does your team have for bringing in new contributors and how can you measure if you are successful?
-A:
+A: I think the only metric that matters is how many new 'core' contributors we get (and how long they stick around). Quality, not quantity. A contributor who'd contribute 1 or 2 patches and then disappear, would not repay for the investment made to teach him stuff. So 'number of patches' and 'number of contributors' are not the important metrics; 'number of core contributors' is.
-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.