I unarchived it for now.

I will wait to see if I did something wrongly or was just a mistake.

@Aklapper archived Blocked-on-schema-change, despite being created with his ok, now WMF schema creation workflow is broken

I have no idea what "despite being created with his ok" is supposed to imply.

No heads up was done to the members of the project

See T142734 where this discussion maybe should take place.

@Aklapper you literally told me to create this project:

T119751#1835024

Now this and Blocked-on-Operations are deleted, arguably the only tickets that ops use to check pending work? If schema changes and operation work stop happening you will literally have a riot from all WMF developers and volunteers. :-D

In T145361#2628076, @jcrespo wrote:

@Aklapper you literally told me to create this project:

More recent T142734 stated these "aren't used and aren't looked at". I had no reasons to challenge such info (which in hindsight maybe was not fully agreed on and communicated, seeing confusion and surprise expressed in this very task and in T142734#2575848 by hashar).

Now this and Blocked-on-Operations are deleted

They were archived (not deleted).

For the time being I've reactivated Blocked-on-Operations (no idea if that made sense or not).

Thanks for joining the discussion in T142734 where previous conversations regarding this topic have taken place.

Shall we close this task and continue in T142734?

@Aklapper, now that I know the context (I wasn't aware of that task, and that it's a problem by itself), it was not your decision.

I asked the owner of the task there; and as you may have already seen, merged the threads.

I hope you can see how worried I was, given the importance of those projects. The only context I had was "Aklapper archived X" and I know I had to mention you explicitly to get your attention because you are subscribed to each ticket.

@jcrespo: Makes a lot of sense! No worries; I just was a bit confused by the choice of words (and probably in need of a first coffee). :)