as its subproject already

There is no way to "move" projects but we can create a new tech subproject under the new umbrella, and then move tasks from the old tech project and then archive the old tech project.

there are also two archived projects

There are numerous: https://phabricator.wikimedia.org/project/query/MQZmkwGXSjrR/#R

For the records, see also T286866: Unarchive WMUA-tech project and create a custom security policy for its members which is more complicated :-(

thank you, then let's have this new umbrella, with a tech subproject there to move the tasks from the old one, and then archive it. thank you! anything else you need from us to be able to do it?

Nothing else needed, I just need to find time in the next ~24h to create the projects and silently mass-re-tag existing tasks not to spam you all with notifications

Could someone please either re-tag or close the ARCHIVED---WMUA-Tech task https://phabricator.wikimedia.org/T302220 which I do not have permissions to access (as open tasks shouldn't have archived-only project tags)? Thanks.

@Aklapper , added the new project to the task.

I am utterly confused by this whole change though. So it seems that the old tasks are in the old project. The open ones are in the new one. This is already confusing.

Both links on WMUA Technical committee page are leading to the old project. For the public tasks that is an easy matter to change the link (I have put the original link there to begin with). But what about the private ones? I see that the custom form 107 still uses the old project. I guess you are saying that instead of that custom security policy it should now use the spaces? I see that acl*WMUA_policy_admins is listed back from 2016, if it is usable I guess it can be employed for that, but in this case is there a way to tweak the private task form so that it adds all the necessary things automatically?

So it seems that the old tasks are in the old project. The open ones are in the new one.

Hmm, where to see old tasks in the old project (URI)?

I admit I forgot about form 107. Was it ever used? In my understanding it never did what it says as it's simple not "private" and has never been as anyone could join the project defined as the form's view policy.
I fixed the project tag in form 107 but I still believe that form is totally useless. In general, I'm not aware of an "allow anyone to file a task but only allow a bunch of folks to access that task afterwards" setup apart from our custom workflow for Security issues which I don't want to replicate.
If you wanted "only a well-defined static group of people can both file and view a bunch of tasks" then this would be a Space.