To clarify: anybody should be able to set priorities. Team should have nothing exclusive or different, other than the fact that they work full time and get to do more things than an individual volunteer.

I don't see how to programmatically say that it's related. But it is:

• https://phabricator.wikimedia.org/T78482 XXXX-Radar projects for Wikimedia family projects and languages + MediaWiki Stakeholders

This task can't be done by a volunteer. It's a configuration change that only an admin can do. If anything, it may be "declined".

Please don't do it. Fix https://phabricator.wikimedia.org/T268 instead. There is no valid need for this task; whether a task is filed by an "organized community" or a "random stranger" doesn't really matter — what matters is its contents, i.e. what needs fixing.

That's peculiar. 3 things may happen, —

Ok, I understand, you want to set it to Lowest because you aren't taking it. I am now ok with setting a lowest-ever priority if a Team doesn't want to work on it now. It's relatively painless compared to manually maintaining tags.

It's ok. Our two messages give an idea. I don't care where to start. (The timestamp editing is needed for refactoring things, a point you missed, but I have the impression that the Flow folks understand what I mean.)

( Spage: I disagree with the process documented on the wiki page you linked. Please discuss here: https://phabricator.wikimedia.org/T76682 ) Discussed on IRC. Looks like we agree there (and this current task is needed just not to lose the data — for some wikis which feel ready to start Flowing without converting old discussions.)

Can I ask how specifically are we converting it to a Flow board? Where does the original content go? Thanks.

No, no yet another checkbox. Just remove it if all notifications are off.

In that list, we missed some features. For instance, these ones:

WARNING: You may have received a lot of email, as I am learning to edit comments. And editing them doesn't have a preview button. I apologize. Please read this comment before replying.

Let's say that a Team acknowledged that it would do tasks A, B, and C, but it doesn't want to do D or E. Yet D is higher priority than E. How would we convey that to the volunteers? We could either not convey it and set "needs volunteer" priority for them both (which sounds silly to me), or actually use the priority field for its original purpose...

Imagine that you create the tasks (if such feature requests haven't been created already, didn't check), and imagine that you set them to High priority. So what?

I can put a specific example. These two tasks have been ignored by the Flow team:

I disagree. If I disabled the notifications, the icon should disappear — it is useless in that case.

Why does the wiki page linked, https://www.mediawiki.org/wiki/Flow/Converting_talk_pages, completely ignore the discussion at https://www.mediawiki.org/wiki/Topic:S12prb6trf24nhkz ?

There are three states a task may take.

I disagree.