Search results
MediaWiki code review currently mostly takes place on Gerrit . Some Wikimedia software projects experiment with code review in GitLab.
- Process
- Rubric
- Special Roles
- FAQ
*** The Code Stewardship Review process is on pause until further notice. Upon the successful hiring and onboarding of our new CTO and/or CPO, we will reassess this process. In the meantime, please...
tl;dr: Components are proposed and a rubric is filled out, based on that rubric the Technical Debt Program Manageradds it to a prioritized list, that list is submitted to the CTO/CPO on a once per quarter basis, as needed. 1. Propose a component, extension, or service to be reviewed. 1.1. How: Check that there is no task yet in the #code-stewardship-reviews Phabricator project. If there is no task, then create a task and include, at minimum, the name of the software, links to repository/docum...
All entries in the rubric could be augmented with commentary that clarifies/explains, especially for the pure numbers focused entries. Note: A purely numerical decision will not be made on the below items. It is a part of a holistic decision making process. 1. A succinct problem statement to give context for why the review was initiated. 2. Entry i...
Technical Debt Program Manager
1. Is the owner of the process, the prioritized list, and submission to the CTO and CPO.
Senior Leadership of Product and Technology
1. Reviews the prioritized list in time for Annual Plan draft programs submission deadline 2. Reviews exceptional cases as needed
Is undeploying the primary/expected outcome of this process?Is this process the only way that things should be undeployed at the Foundation?Should there be an "owner by default" (eg: all "user facing" things are to be decided by Product)?What about components owned by the community (both funded and non-funded teams/individuals)?MediaWiki code review was itself historically facilitated through a MediaWiki extension. As of March 2012, it has been done through Gerrit . Since version 1.16, MediaWiki uses the jQuery library.
People also ask
Where is MediaWiki code review done?
How does MediaWiki work?
What is wikipedia's code review process?
Is MediaWiki a suitable replacement for a dedicated online forum or blogging software?
Jan 14, 2024 · If you list a patch, then you are taking responsibility for addressing any code review. Any -1s from humans or Jenkins should already have been addressed. Patches should have already been tested and (in theory) ready for an immediate +2. Work in progress patches should not be included. It should apply cleanly to master or have recently been ...
Wikipedia's code review process is a way to receive feedback from other editors about new or proposed changes to a user script or Gadget. Such changes would usually be proposed by the script's maintainer, unless they are inactive.
Dec 30, 2023 · MediaWiki is a free and open source software, so the source code is available for use, inspection and modification. The following pages describe the various ways to interact with it: Download lists methods to getting the source code into one's computer.
