The purpose of the MozillaWiki team is to facilitate maintenance and improvement of MozillaWiki.
The MozillaWiki team (formerly Wiki Working Group) was formed in early 2014 with the goal of kick-starting a revitalization of the wiki and to create a sustainable framework for empowering the entire Mozilla community to participate in and sustain this effort. We have achieved the first part of this goal (revitalization) and are now working towards incremental feature improvements and creating a framework whereby the entire Mozilla Community can participate in maintaining and improving the wiki.
Our main goal is to build tools and establish processes that empower Mozillians across functional, product, and regional areas to contribute to collective stewardship of the wiki.
Our 2015 goals include:
- implement feature improvements according to our roadmap
- document MozillaWiki policies, procedures and processes
- recruit an active group of page patrollers
How to Participate
Bi-weekly MozillaTeam meetings are currently on-hold.
If you want to be involved in the MozillaWiki team, please contact User:CaptainCalliope or join one of our communication channels.
- subscription page (subscribe via email)
- google groups page
We release changes to MozillaWiki weekly on Thursdays. We track release planning on MozillaWiki:Releases subpages. Once the release is complete, post an announcement explaining the changes to MozillaWiki:News.
All feature and change requests are tracked in Bugzilla, under Websites > wiki.mozilla.org.
The process for a feature or change request to be implemented in production is as follows:
- File a bug.
- Members of MozillaTeam will triage the bug accordingly, modifying whiteboard, milestone and other fields accordingly.
- The request will be evaluated for suitability on MozillaWiki during a MozillaWiki community call (held twice monthly). Decisions during community calls are generally made by lazy consensus, with MozillaWiki module owners and/or peers making the final call if necessary.
- If MozillaWiki team determines the change should be implemented, it will be rolled out to our development instance first. While it implemented on dev, it will undergo testing and security review (if required).
- Once the change has been tested and passed security review (if required), it will be pushed out to stage and finally production.
Requesting features and changes
To request a change or feature, please file a bug.