Hello, valued community!
Throughout the years, the Mozilla QA team(s) have undergone many changes (people, products, focuses, communication mediums, etc.,); as part of those changes, many of our wiki pages, blogs, websites, Twitter accounts and others have gone sadly out of date. Additionally, due to changes in what we work on, and how we work on it, some systems and processes are no longer open, or at the very least, as transparent as they could and should be.
Some specific examples of feedback we’d love to have you provide back to us are:
- Which site(s)/communication method(s), etc., (if any) are easy to use, understandable, and provide you with up-to-date information on how to get and stay involved in Mozilla’s QA/testing community?
- What can (and should) we do better, to make getting started/unstuck easier?
- Are you interested and able to help in fixing broken links, adding new ones, etc.?
- Are there any technological (tools, accounts, access-permissions, etc.) or process/communication barriers which we might be able to help you with, to unblock further contribution?
- What brought you into the Mozilla QA community? And, if you’re still active, what are the things which are keeping you there?
Anything else you can provide feedback/suggestions/direct help fixing (again, as specific as possible, down to the link/pages, etc.) would be fantastic!
The current team I’m on, Firefox Test Engineering (http://firefox-test-engineering.readthedocs.io/en/latest/) would also love it if you could give us specific feedback about the above Read the Docs page, and any links/instructions you find there, as well.
In posing these questions, I purposefully am trying not to lead any of the answers, but do note that I, at least, am particularly aware of, and will be focusing my and the larger team’s attention to bringing up-to-date/re-evaluating, the following (in no specific ranked order):
Thanks so much!