Specific: What do we want to achieve?
The mobile site, when AMC is disabled, replaces the Special:Contributions special page with its own implementation. Code-wise this page shares very little with the core page. It is not maintained, has numerous bugs, and when modifications need to be made to the mobile experience it grows in complexity.
In a future project it is planned to add tabs to the mobile experience of the contributions page. To prepare for this, we'd like to build from better foundations, and have one special page in core which contains the code for this experience.
We want to do this in such a way that users notice no difference. We will need to make changes to core, potentially adding hooks and style the non-AMC page to look identical to how it is now.
Measurable: How will we know when we've reached our goal?
- The special page code no longer exists in MobileFrontend https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/master/includes/specials/SpecialMobileContributions.php
- The page looks exactly the same
Achievable: What support will we need to achieve our goal?
No support outside the team should be needed. Special pages do not have maintainers.
- Relevant: Is this goal worthwhile? **
Will reduce the code the team maintains.
Time-bound: What is the time frame? Can we achieve this goal in the timeframe I've set?
One month. Change is limited to core changes, Minerva styling and MobileFrontend code removal.
Developer notes
this is what we'll trying to do get to: https://gerrit.wikimedia.org/r/c/mediawiki/skins/MinervaNeue/+/733027