The QA team says there are no current plans to resurrect support for -- at least not via QMO -- its "Media" (/media) / ("QMO Videos") section.

So, we can:

1. remove that page and its top-nav entry
2. disable or better-yet outright remove the powering Vimeo plugin

On https://quality.mozilla.org/community/, there are currently plugin-based filter buttons to toggle "All," "Blogs," and "Tweets." Per discussion and decision in a couple of meetings, we should remove these buttons, since our Tweets are outdated, and for now we really only care about the blog posts.

We @mozilla/firefox-test-engineering (and perhaps other individuals?) should figure out a plan to update this blog to reality.

A good start would be to look through the team-specific additions from the QMO6 landing, and figure out what to do with them (likely remove them):

956db2f

It's been decided that we should remove the username and password login fields on https://quality.mozilla.org/ , since they are confusing to new and returning, non-Admin users (since the former no longer has a place to sign up, nor, really a reason to).

Admins and other user-levels with permissions can and should (post-this-change) still log in via https://quality.mozilla.org/wp-login. We should also take care to reflect and expose the logged-in state/username/log out ability for those users.

added a readme file on my locale github file of qmo https://github.com/satdav/quality.mozilla.org/blob/master/README.md

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• the wiki has been disabled, as it was not used

These were made as the result of a recent automated defacement of publically writeable wikis.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)