MozillaWiki:About

This wiki (wiki.mozilla.org, AKA MozillaWiki or WikiMO) is the official public wiki of the Mozilla Project. It serves as the public memory for the Mozilla community, documenting its projects, planning, processes and teams. Additionally, the wiki seeks to facilitate lively community interaction that empowers contributors to coordinate activities, find support, and make their projects accessible to other contributors across Mozilla.

This wiki is a publicly available resource for those wanting to learn more about the Mozilla Project. It is not designed nor intended for end-users. If you're looking for user support for any of Mozilla's products, visit support.mozilla.org.

What content is appropriate for MozillaWiki?

Content that is related to the ongoing planning, coordination, or other contribution activities of current or past Mozilla projects.

Content pertaining to Mozilla's mission, strategy, or history.

Content that supports Mozilla's mission or community.

Content which appears to be unrelated to Mozilla and not falling into any of the above categories may be deleted as spam without notice.

Namespace-specific guidelines

Some content is reserved for specific areas (namespaces) of MozillaWiki:

Discussion about the content of a page on MozillaWiki belongs on its corresponding discussion page (in a Talk namespace).

Content that is related to helping people use the Wiki belongs in the Help namespace.

Content that is about a particular individual or their work (including personal task tracking) belongs in the User namespace. Unlike on Wikipedia, biographies are not appropriate content for the Main namespace on MozillaWiki.

Pages may be moved out of the Main namespace without notice in accordance with these guidelines.

Is product documentation appropriate for the Mozilla Wiki?

In general, no, product documentation is not appropriate for the Mozilla Wiki except when it is about the Mozilla Wiki itself.

There are two types of product documentation: end-user documentation and developer-focused documentation.

End-user documentation is written for users of Mozilla's products and explains how our products work and how to use them. In general, this type of content belongs on SUMO.

Developer-focused documentation is written for programmers and includes content such as technical reference information and building and debugging instructions. In general, this type of content belongs on MDN.

To summarize: MDN documents how to interact with code. The Mozilla wiki documents how to interact with teams. SUMO documents how to interact with Mozilla products (as an end-user).

Technical Support is provided jointly by the community and MoCo staff.

Content is managed by the community. Information here is public and can be modified by anyone in the Mozilla community with sufficient interest and knowledge to improve it (and an account).

Where can I report issues with wiki.mozilla.org?

Technical issues should be reported via bugzilla. These include server or client-side errors, styling issues, problems with accounts or logging in, and feature requests.

Content issues should be addressed on the wiki itself using Talk/Discussion pages whenever possible.

General questions can be addressed to tools-wiki or #wiki on irc.mozilla.org.

How is the Wiki a critical resource to the Mozilla Project?

The Wiki provides the most comprehensive, overall picture of Mozilla's mission, strategy, and history. Information on the wiki tells the story of Mozilla and makes the organization navigable in a way that no other single resource does. The wiki, along with Bugzilla and our forums, form the core of Mozilla's long-term institutional record.

The Wiki is a significant entry point for contributors into the Mozilla project. It serves as a primary and massively scalable on-boarding tool because it provides the opportunity for self-serve contribution pathways across all areas of the project. The wiki enables self-motivated individuals to take advantage of contribution opportunities immediately. The better organized the wiki, the more people are able to take advantage of these opportunities.

Publicly available wikis, code repositories, and bug trackers are essential to our collaborative environment and connect our project to the greater open source eco-system. These tools are part of the established canon of open source organizational tools because they make the knowledge and tools required to participate immediately available to those who are interested. Experienced open source participants benefit from Mozilla providing these tools because it is what they are accustomed to, and those new to open source benefit because it prepares them for working with other projects in the open source ecosystem.