> 1) Events
Consider spreading the date range in which QA runs (maybe with someone
at the first day present). Having it always on the same day causes some
people always being unable to attend.
> * Bucket large tasks into smaller chunks so it's easier for the community to choose roles
This can maybe not over-emphasized so people who just want to contribute
few time or try contributing have a good chance to do so.
> * Clearer steps to get involved on Nightly first run page, link
> to QMO
Please get rid of the video. The tab is pretty resource hungry
> 4) Mozillians.org
> * Use as an entry point for new QA contributors
Don't have to high expectations on existing community members coming to
QA, I don't know of any members being idle and not knowing what to do to
help Mozilla. As far as I know, Mozillians has showing contributions on
its roadmap which QA could have an advantage from its implementation.
> * create a program to reward contributors based on earning points and/or badges
Just my experiences with this:
From testdays years ago (with one person rewarded, eligible once per
year if I remember correct): The people who participated did much work,
but the work of some was void or had to be checked by someone else (they
skipped working steps to get more points). The people who participated
in those days and are still active now were already involved somewhere
else in Mozilla.
I don't know about what kind of rewards you are talking, on
we ran last year a review competition for add-on
reviews to decrease the review backlog and the review count was the only
metric. This year, it stretches again over two months, and along to the
review count, security and adherence to review policies have an impact.
These contests shift behaviour of the editors who review the add-ons: A
trend is towards easy to review add-ons which don't need much time,
locking add-ons pending review by having multiple review tabs open etc.
Also keep in mind different motivations dependent on the conditions of
the member (like pay/hour in his home country) or motivations by lack of
resources like time compared to other team members or being active in an
area lacking appropriate metrics.
For myself, after addons.mozilla.org
getting paid editors, I think I
shifted priorities away from it because I know someone will care about
the work there.