@Aklapper Discussing here is fine or doing so on-wiki and linking it here would be most appropriate? I think that we can do it on-wiki at mediawiki.org so we can have input of all the stewards and watchers of the bug and avoid mailspam, but will do as you think it's better. Best regards.
tl;dr it allows a project management approach
A project creates a (parent) board to which multiple components can be added, and enables easier addition.
and it doesn't have to relate solely to an editing change. It can have a forward looking approach to what may need change, when, ...
Alternative names, noting that swmt is jargon, and it is bigger then bugs
- "Steward, global sysop and small wiki monitoring"
- "Stewards and global tools"
The UI in phabricator is terrible for tracking bugs, you can only add blockers from the tracking task itself, not from the task that is blocking, which is pretty inconvenient IMO.
SWMT should be a hashtag for the project. I like the suggestion of "Stewards-and-Global-tools" for now, we can refine the name later on if people are unhappy with it.
If we could call it rue, I would say it, we could call it steward, swmt and gs "stuff". Mayve We could take the name form MF-Warburg, and replace Bugs with tools. So this could be:
Steward, global sysop and SWMT tools
Maybe this is a bit long, but I think it would be better to create this project, and rename it later, than discussiong a long time.
Stewards and functionaries tools? I'm fine with stewards and global tools if the scope of the tracking bug is reduced, see below.
I think T43492 has become a potpourri of tasks related to stewards, tools and rights. Maybe we need more than one project, or reduce the scope of the task.
That would be great Legoktm. Thanks for the creation. It was one of our
decisions late last week, so good to see it happen already.
Do people have a recommended board structure for a project suchas this?