I've sorted, linked, tagged, organized, and
gardened our collection of QA
pages on mw.o to be more useful. Of course there is always more to do, so
comments, criticism, edits are welcome.
In the past days I went a mile (or two) further. I think we have a good
structure of pages under QA now. What is missing are more specific calls
to action for contributors and polishing some pages. Even inside the WMF
teams we are having difficulties to nail down tasks for contributors and
testing sprints. Coincidence? Surely not. We _just_ need better
coordination beyond our own little projects and teams, and better
collaboration with e.g. extensions developers craving for testing and
Currently we have guidelines to be a good contributor in Features
testing and Browser testing. What we miss are specific projects that
need help right now. Otherwise potential contributors hesitate choosing
a project or fear the risk of working in something already done
somewhere. In order to fix this we need the involvement from the
projects (WMF or not).
Probably related to this there is the fact that different teams have
different pages for testing & QA e.g.
pages in Wikipedia or Meta. You can help at least making sure that those
pages are connected to the QA umbrella.
fyi this is how QA is structured now:
Feedback and help is welcome.
Technical Contributor Coordinator @ Wikimedia Foundation