Attention visual designers! Are you interested in contributing to Mozilla QA, being part of an awesome worldwide community and having your work seen by a lot of people? If so, read on because we’re looking for help with a very cool new project.
Mozilla’s Quality Assurance (QA) team relies on community volunteers for help with a variety of things and would like to create a badge to recognize these contributors for their work. The following actions represent a small sample of the many different ways a community contributor could earn a General QA Participation Badge:
- Participating in a Test Day
- Translating documentation
- Filing or updating bugs in Bugzilla
- Participating in product stability testing and crash investigation
- Running tools (like link checkers against Mozilla websites, etc.)
- Submitting a pull request on Github for test automation
- Assuming responsibility for one round of manual testing in a project
- Completing a round of exploratory testing
This General QA Participation Badge will serve as a guideline for other, more specific QA badges that will follow. The badge will also be part of the Open Badges Project (http://www.openbadges.org/) – a wider network of badges that are interoperable, shareable and contain metadata so people can easily learn more about how they’re earned. The badge will go into a digital badge repository, and could be added to blogs using a WordPress plugin.
Mozilla QA needs a visual designer to create this badge. Interested? You need not be a professional designer – we’d love to have anyone try their hand at creativity and submit their design.
* To submit designs, please upload your images to Flickr and tag them with mozqabadges. (This part is very important – we won’t see your submission if it’s not tagged properly.)
* Designs are due on Friday, August 16 2013 8:00 PM PST.
* Deliverables include 90×90 PNGs for each badge, with a maximum size of 256kb.
Christopher Appleton of the Mozilla Foundation has already developed a visual system for other Mozilla-related badges, so we would need you to both follow his general style and put your own creative twist on this particular project.
• Avoid using existing branding http://www.mozilla.org/en-US/styleguide/identity/mozilla/branding/
• Badge design should be predominantly illustrative (photography should be used sparingly or not at all)
• Text should be avoided on the badge itself
• Graphics should be legible at small sizes
If you have questions, please send an email to email@example.com and we’ll respond as quickly as possible.