Confirmed users
4,378
edits
| Line 23: | Line 23: | ||
* (juanb) Today I cannot point them to a well defined list of contribution opportunities. It is one of our quarterly goals to produce a list of, say, 3 well defined tasks people can try, per functional QA team. | * (juanb) Today I cannot point them to a well defined list of contribution opportunities. It is one of our quarterly goals to produce a list of, say, 3 well defined tasks people can try, per functional QA team. | ||
* (nhirata) https://wiki.mozilla.org/Mobile/Get_Involved; https://wiki.mozilla.org/Mobile (get involved section); in terms of testing mobile, mobile newsletter : https://mail.mozilla.org/listinfo/android-mobile-nightly-testers, https://wiki.mozilla.org/Mobile/Testdrivers_Program | * (nhirata) https://wiki.mozilla.org/Mobile/Get_Involved; https://wiki.mozilla.org/Mobile (get involved section); in terms of testing mobile, mobile newsletter : https://mail.mozilla.org/listinfo/android-mobile-nightly-testers, https://wiki.mozilla.org/Mobile/Testdrivers_Program | ||
** to note : the mobile newsletter is syndicated in my blog, my twitter account, my people account, my facebook account, Planet, QMO, Browser Tech and Mobile blogs. | |||
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. | ||