Prior to initial deployment, the Code Stewardship for a new extension or service needs to be determined and reviewed. Not doing so will result in a ever growing amount of code in production that is unmaintained/supported. Although the community at large may be providing maintenance support (bug fixes, minor enhancements, etc...), broader code health concerns generally remain under/un supported without explicit Code Stewardship plans.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T203703 Create production code deployment management process | |||
| Open | None | T195244 Investigate and make improvements to the extension review process | |||
| Open | None | T203698 Add Code Stewardship review to Review Queue process |
Event Timeline
Comment Actions
Is this supposed to be mandatory? If yes, would this be an item under "Preparing for deployment" under #3 on https://www.mediawiki.org/wiki/Review_queue ?
* {{anchor|stewardship}} '''Stewardship:''' Request a [[Code stewardship review]] to verify that the code base is actively maintained and that issues or broader [[code health]] concerns get addressed.Comment Actions
I've made some edits over the last days to https://www.mediawiki.org/wiki/Review_queue as I had to realize in https://phabricator.wikimedia.org/T61245 that the page is/was rather incomprehensible to non-technical community members. Coming from that, I propose that this should be the very first item on that page, and be combined with telling the reader (may that be a community member or a developer) that this is the first thing to check and resolve.