Judging by T388228#11405523, it seemed like this project may no longer be actively watched/monitored/used:
I asked in the #wikimedia-qte IRC channel (linked from https://www.mediawiki.org/wiki/Wikimedia_Quality_Services), and this was confirmed by @SLong-WMF:
<A_smart_kitten> hello QTE/QS :) just a question out of curiosity -- are you aware if the Phabricator project https://phabricator.wikimedia.org/project/profile/4403/ (#Quality-and-Test-Engineering-Team) is monitored/watched, and/or whether it's (in practice) an active Phabricator project used by the team? <A_smart_kitten> i'm just asking, as the comment at https://phabricator.wikimedia.org/T388228#11405523 suggests (to me) that it may not be (in practice) an active Phabricator project; but e.g. the docs at https://www.mediawiki.org/wiki/Wikimedia_Quality_Services still points to that Phab project. <slong> It's not used. The QTE team hasn't really been a group for a couple of years now - it's "Quality Services" and "Test Platform", managed by different people (myself and Armen). We're further evolving the QS team along the lines of automation support and semi-embedded testing support aligned to yearly objectives that the Foundation is currently standing up. <slong> I removed the reference on that document but #QS-Test-Automation in Phabricator is currently where we're gathering automation-related projects that the automation portion of the team is working on prioritizing.
(as I believe that #wikimedia-qte is an unlogged channel, confirming that permission was given to copy these messages to Phabricator.)
A few things to note:
- The Quality-and-Test-Engineering-Team project currently contains a number of open tasks. Someone might want to go through them & (e.g.) retriage the still-relevant ones into their relevant tags, & close ones that are now e.g. obsolete/no longer relevant.
- Maybe the Quality-and-Test-Engineering-Office-Hours project should also be archived, if Quality-and-Test-Engineering-Team is? (I'm not personally sure how that tag might/might not fit within current practices.)
- One complication might be that Quality-and-Test-Engineering-Team currently has the subproject Catalyst, which - as far as I'm aware - is an active WMF project/team. Given that (as far as I'm aware) subprojects can't currently be separated from their parent project, I guess the options here might be:
- Have Catalyst remain as a subproject of an archived project (which admittedly might be simplest, but might then e.g. lead to a bit of confusion sometimes - e.g. T324929 - and might not be the most semantically correct); or
- Create a new project (probably that isn't a subproject of anything), & silently batch-move all tasks tagged with the current Catalyst project to that new project. (& do something similar for Catalyst's milestone-type projects)
(FWIW, it looks like these Phab projects were referenced from T384348: QTE cleanup (triage & planning) in early 2025, but it's unclear (to me) what the conclusions/outcomes from that task were.)