https://phabricator.wikimedia.org/project/query/YFNTY6ViYquD/#R
These should all be the same project, no?
https://phabricator.wikimedia.org/project/query/YFNTY6ViYquD/#R
These should all be the same project, no?
Please discuss with the team what is wanted. I cannot answer the "no?" part myself. :)
Related: https://www.mediawiki.org/wiki/Phabricator/Project_management
on irc, subbu says,
11:18:25 AM - subbu: ok. yes, it makes sense for them all to be the same project .. not sure if there is a field for that component business from bugzilla.
11:18:39 AM - subbu: i haven't used that field much when in bugzilla .. not sure if others have found it usefull.
It is possible to have a single project and multiple additional tags. Since every issue can have many projects / tags assigned to it, it's possible to start with just the project by default, but also add finer-grained tags so that people can follow them / filter on them.
For services we just asked for few project / tags in T75769. We added some -rfc tags so that people can subscribe to those if they are interested in higher-level design discussions.
You can assign this task to a member of the Parsoid team. Basically you need to either rename projects (including changing the label icon/color) or move tasks to the project(s) you want to consolidate, archiving the rest.
To do this properly, please check https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects
You can also request to be added to acl*Batch-Editors and/or Project-Admins
I agree with having them all under one single project, maybe leaving the components as additional tags. But for SoS we still need a tag to represent the Parsoid team, which is the one "People" project named Parsoid. So my proposal would be:
Does this make sense?