Change Details

As discussed in a recent engineering team meeting, there are several advantages to splitting MediaSearch out of WikibaseMediaInfo into its own extension: - We can set up Jest for front-end testing without having to deal with the existing node-qunit frameowrk in WBMI - We can use the opportunity to create some boilerplate code for future projects (test framework, potentially webpack config or Storybook implementation) - If an opportunity to use MediaSeach on another wiki comes up in the future, the code will already be modular and separate from WBMI - WBMI is becoming quite large and modular code will be easier to maintain going forward Here's a rough outline of what needs to be done; I'll split some of this out into subtasks later: - Request a new Gerrit repo - Build new extension, get CR from team - Determine if we need security readiness review and, if so, get the ball rolling on that - Remove code from WBMI - Coordinate deployment - Documentation: extension page and help page on mediawiki.org, add to https://www.mediawiki.org/wiki/Developers/Maintainers

As discussed in a recent engineering team meeting, there are several advantages to splitting MediaSearch out of WikibaseMediaInfo into its own extension: - We can set up Jest for front-end testing without having to deal with the existing node-qunit frameowrk in WBMI - We can use the opportunity to create some boilerplate code for future projects (test framework, potentially webpack config or Storybook implementation) - If an opportunity to use MediaSeach on another wiki comes up in the future, the code will already be modular and separate from WBMI - WBMI is becoming quite large and modular code will be easier to maintain going forward Here's a rough outline of what needs to be done; I'll split some of this out into subtasks later: - Request a new Gerrit repo - Build new extension, get CR from team - Determine if we need security readiness review and, if so, get the ball rolling on that - Remove code from WBMI - Coordinate deployment (part of which will be T278121) - Documentation: extension page and help page on mediawiki.org, add to https://www.mediawiki.org/wiki/Developers/Maintainers

As discussed in a recent engineering team meeting, there are several advantages to splitting MediaSearch out of WikibaseMediaInfo into its own extension: - We can set up Jest for front-end testing without having to deal with the existing node-qunit frameowrk in WBMI - We can use the opportunity to create some boilerplate code for future projects (test framework, potentially webpack config or Storybook implementation) - If an opportunity to use MediaSeach on another wiki comes up in the future, the code will already be modular and separate from WBMI - WBMI is becoming quite large and modular code will be easier to maintain going forward Here's a rough outline of what needs to be done; I'll split some of this out into subtasks later: - Request a new Gerrit repo - Build new extension, get CR from team - Determine if we need security readiness review and, if so, get the ball rolling on that - Remove code from WBMI - Coordinate deployment (part of which will be T278121) - Documentation: extension page and help page on mediawiki.org, add to https://www.mediawiki.org/wiki/Developers/Maintainers