Change Details

### Description To promote MW REST API API module creation, we need to have an initial example. Going through the extension module creation process ourselves will also highlight opportunities to make the configuration process easier for API owning teams. NOTE: Which extension module is selected depends on: https://phabricator.wikimedia.org/T414469 ### Conditions of acceptance [] Migrate growthexperiments (proposed, based on {T414469}; pending feedback on additional audience modules) extension to be its own module. [] Module appears in the discovery doc [] Module appears in the the REST Sandbox (within the dropdown, and with docs when selected) [] Lightly document the current set up process. Assume that this artifact is predominately for MediaWiki Interfaces review and utilization (for now). [] Identify pain points in the configuration and deployment process, as it exists today. [] Proposed improvements for pain points. [] Demo current setup process with the MWI team. [] Review identified pain points and potential fixes with the MWI team. [] Create follow up tasks as needed, once we are aligned on the problems and proposed solutions. **//Out of scope//**: * For now, do not worry about making the spec fully linter compliant. We can have a follow up task to raise the bar on the quality of the generated spec, likely in partnership with the owning team.

### Description To promote MW REST API API module creation, we need to have an initial example. Going through the extension module creation process ourselves will also highlight opportunities to make the configuration process easier for API owning teams. NOTE: Which extension module is selected depends on: https://phabricator.wikimedia.org/T414469 ### Conditions of acceptance [] Migrate at least one extension into a dedicated module (proposed, based on {T414469}; pending feedback on additional audience modules) extension to be its own module. [] Module appears in the discovery doc [] Module appears in the the REST Sandbox (within the dropdown, and with docs when selected) [] Lightly document the current set up process. Assume that this artifact is predominately for MediaWiki Interfaces review and utilization (for now). [] Identify pain points in the configuration and deployment process, as it exists today. [] Proposed improvements for pain points. [] Demo current setup process with the MWI team. [] Review identified pain points and potential fixes with the MWI team. [] Create follow up tasks as needed, once we are aligned on the problems and proposed solutions. **//Out of scope//**: * For now, do not worry about making the spec fully linter compliant. We can have a follow up task to raise the bar on the quality of the generated spec, likely in partnership with the owning team.

### Description To promote MW REST API API module creation, we need to have an initial example. Going through the extension module creation process ourselves will also highlight opportunities to make the configuration process easier for API owning teams. NOTE: Which extension module is selected depends on: https://phabricator.wikimedia.org/T414469 ### Conditions of acceptance [] Migrate growthexperimentsat least one extension into a dedicated module (proposed, based on {T414469}; pending feedback on additional audience modules) extension to be its own module. [] Module appears in the discovery doc [] Module appears in the the REST Sandbox (within the dropdown, and with docs when selected) [] Lightly document the current set up process. Assume that this artifact is predominately for MediaWiki Interfaces review and utilization (for now). [] Identify pain points in the configuration and deployment process, as it exists today. [] Proposed improvements for pain points. [] Demo current setup process with the MWI team. [] Review identified pain points and potential fixes with the MWI team. [] Create follow up tasks as needed, once we are aligned on the problems and proposed solutions. **//Out of scope//**: * For now, do not worry about making the spec fully linter compliant. We can have a follow up task to raise the bar on the quality of the generated spec, likely in partnership with the owning team.