Hm, I wonder if "Blocked-on-schema-change" should be clearer, to make it obvious that it applies to WMF infrastructure only?

I agree with all the suggestions, except with #wikimedia-DBA. That sounds
and writes unnaturally.

Either it reflects a team, DBA, DBAs,Database-administrators, or a task; in that last case I would prefer Wikimedia-databases or WMF-databases. I would prefer it
without a reference to the foundation, after all, I am part of operations,
not Wikimedia operations, not wikimedia-netops, etc.

I know a better name doesn't fix worflows on its own, but it has to be easy
to find.

Makes sense. Thanks for explaining, please feel free to go ahead, either with DBA or Wikimedia-databases.

I've edited the description shown here:
https://phabricator.wikimedia.org/project/profile/1060/

I've specifically avoided adding the alias #Database and #Databases, as those are ambiguous- (is it about database code or problems with actual databases?).

I want to clarify the differences between DBA and MediaWiki-libs-Rdbms, but I have problems doing it without sounding "that is not my job"- what I want to clarify is that if you create an extension X, it is the responsibility of the creator of X to create good and fast persistence code, even if I can be helpful in some cases, will verify it and apply personally the schema change.

I've documented the changes on my workflow on https://wikitech.wikimedia.org/wiki/Schema_changes