The admin tool and Striker serve very similar purposes, yet are separate things with separate codebases. It would help create a more unified, cohesive experience for Toolforge users if these were just the same website. Since Striker is a production-grade service (as it is required to be), my thinking is that we should just merge admin tool functionality into Striker and then make the admin tool just a pointer to that content (since WMCS can depend on production but not vice versa).
Description
Description
Related Objects
Related Objects
- Mentioned In
- R1922:f3d1fd8e7eb6: Redirect tool pages to Striker
- Mentioned Here
- T179222: Investigate reconciling two tools interfaces
- Duplicates Merged Here
- T179222: Investigate reconciling two tools interfaces
Event Timeline
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 30 2018, 8:17 PM2018-04-30 20:17:20 (UTC+0)
• Vvjjkkii renamed this task from Merge admin tool and Striker; serve admin tool content from Striker to 2xdaaaaaaa.Jul 1 2018, 1:12 AM2018-07-01 01:12:51 (UTC+0)
CommunityTechBot renamed this task from 2xdaaaaaaa to Merge admin tool and Striker; serve admin tool content from Striker.Jul 2 2018, 7:25 AM2018-07-02 07:25:47 (UTC+0)
• bd808 moved this task from Backlog to Needs Discussion on the Striker board.Dec 30 2018, 4:05 AM2018-12-30 04:05:30 (UTC+0)
• bd808 removed a project: cloud-services-team (Kanban).Jul 9 2019, 9:33 PM2019-07-09 21:33:41 (UTC+0)