I think these should be default blue components instead of yellow tags.

@Aklapper Yes, thanks for clarifying. I did not mean "Tag" in the WMF sense, but rather "Tag" in the Phabricator sense (I could not find a link, and I'm unsure about uploading screenshots of Phab to Commons, but see "Edit Query" in a Maniphest Search).

:)

I now think we mean the same, though "WMF sense" vs "Phabricator sense" has also become confusing recently due to upstream's latest UI inconsistency (see https://secure.phabricator.com/T10326 ). :D
Anyway: +1! :)

@Aklapper Cool. Any thoughts on the proposed naming convention? Trying to make things easy-to-use for the team (can find projects easily, see them at a glance in board view), and also mitigate the flood of iOS-related projects (and projects in general, such as when searching).

In T129302#2107961, @MBinder_WMF wrote:

@Aklapper Cool. Any thoughts on the proposed naming convention?

Not really. :) Whatever is kind of consistent. I'm more interested in good project descriptions that people outside of the team will also understand, as Wikimedia Phabricator is a public place.

mitigate the flood of iOS-related projects

That's one personal impression I share : File a bug report in Wikimedia Phabricator about a mobile application and try to find/set the correct project/tag. I'd say not easy at all currently (I don't know either when entering either "mobile" or "ios" and looking at Phabricator's project proposals), and might get worse once creating more "iOS-*" projects/tags...

@Aklapper what if we made the tags accessible to only one person, such as the Product Owner on the iOS team? Is that possible? It would allow the PO to tag and track via triage, and hopefully reduce clutter by reducing visibility. However, it would also reduce the possibility of anyone else interacting with the tags, including volunteers, but would not prevent anyone from populating tasks in the backlog or completing work on the workboards.

In T129302#2118313, @MBinder_WMF wrote:

@Aklapper what if we made the tags accessible to only one person, such as the Product Owner on the iOS team? Is that possible?

By default we do not restrict access to projects.
Hiding certain projects (by displaying "Restricted Object" to anybody else) will raise more questions about your team's transparency than help avoiding UI clutter I'd say.

Yes, but it's not just 'by default' - there are no good reasons to have a restricted visibility project in Wikimedia.

Projects were created, but I left this task unresolved so as to not mess with this boards process. :)