We need a name for this project, which should replace this tracking bug T43492: [DO NOT USE] Steward, global sysop and SWMT tasks bugs (tracking) [superseded by #Stewards-and-global-tools]
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
NOTE: When created this project, please ping to me, I will add the new project to all blocking tasks of T43492
Comment Actions
Please provide the project name and a description. See https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects
Comment Actions
@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.
Comment Actions
I have no idea what a project is and why it is preferable to a perfectly working tracking bug, but why dont we call it "Steward, global sysop and SWMT bugs"?!
Comment Actions
tl;dr it allows a project management approach
OR ...
A project creates a (parent) board to which multiple components can be added, and enables easier addition.
https://www.mediawiki.org/wiki/Phabricator/Project_management
https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects
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"
Comment Actions
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.
Comment Actions
I'd suggest another name other than Stewards-and-global-tools. In T43492 we kept track of bugs on tools not necesarily "global".
Comment Actions
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.
Comment Actions
@MarcoAurelio it has an "and" there for both stewards' tools and global tools. If you can identify which tools are not covered by the name so we can get a name, and stop a naming being a blocker that would be helpful.
Comment Actions
I wonder about the scope of that task. Is it useful as is, or would it be better to be broken into smaller more easily identifiable parts?
Comment Actions
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.
Comment Actions
@MarcoAurelio it may be the case, and if we get it into a project we can better sort items into their own boards/sub-projects and reassess. Can we please call this ready for a project creation? Our fluffing around over a perfection of a name is <ugh>.
Comment Actions
Can we get this done please? Updating the huge blocked by list in the parent task is a PITA.
Comment Actions
I'll be bold and go with "Stewards-and-Global-tools" for now and we can refine later.
Comment Actions
Stewards-and-global-tools created, and all open tasks migrated. I can do the closed tasks too if someone wants.
Comment Actions
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?