Adding `-team` to (almost) all of the tags in Project Discussion

[jflory7 (Justin W. Flory)]

@mattdm

But… unless I’m missing something, I think a prefix has several disadvantages:

1. More typing. You actually can start in the middle, so if the tag were #badges-team, typing b a d still makes it show up, but it’s more natural to start at the beginning, which means a lot of t e a m - to find the right tag.
2. Kind of confusing because we don’t usually[1] invert like that… “Fedora Design Team”, not “Fedora Team Design”.
3. Puts Team vs. SIG. vs WG in a primary, emphasized position — when we generally want to de-emphasize that.
4. And if you are starting at the beginning, you need to remember whether it is #sig-cloud or #team-cloud or #wg-cloud.
5. And (a new one I just made up): phrasing it as “Team Cloud” seems more like “I’m a fan of cloud computing paradigms!” than “discussion for the team working on Cloud stuff”.

1. Granted, it is a few more characters. However, many times I approach a new topic as my intention to find the right audience for my topic. My desire for a prefix is because this is the typing I am already doing when I come to post something. For example, a Mindshare topic might be relevant to mind-co but I might also want to flag it to a specific team or sub-group too. If I can use a prefix as a filter to find other teams that I might not know about yet, that helps me get my content in front of the right group of people.
2. A prefix is not the same as the team title. Think of it like hostnames, a “pretty” hostname and a “static” hostname. The pretty hostname (or team name) is how it would be written in a document or spoken aloud. The static hostname is easier for sorting, organizing, and finding similar content. My pitch for a prefix is only about the “static” name, not changing how we refer or write a team name across the project.
3. Could we only use team- as a prefix then, and not adopt sig- or wg-? I think this is simpler. Maybe this is also in line with what you originally pitched.
4. So, let’s just have team- as a prefix then. Problem solved?
5. Then best to leave it to the tag homepage and Discourse magic-config post describe what the tag is all about?

@mattdm

But there is a catch. The reason for this change is because tags on Ask overlap with the tags here — for example, both currently have #server. If we do the above, someone filtering on #server for this site who does not adjust would suddenly[2] get the Ask category posts in the folder they were expecting to be for the team posts, and the #server-wg team posts unfiltered. I’m thinking it would make more sense to let people adjust this first. Does that make sense?

This is useful context that I didn’t have. But if I am a newcomer to the community posting about something Fedora Server-related, and I am only typing in the tag field without digging in too much, I would be confused by what -wg or -sig means. (I often find myself having to explain SIG vs WG already to Fedora newcomers.) The difference between server and server-wg is not intuitive as a newcomer.

Additionally, I like the team- prefix better because as an author of a new topic, if I am trying to reach a team/SIG/WG, I must be intentional about it by starting the tag with team-. I think it is more intuitive and it would also avoid people posting general knowledge questions and topics in the wrong place. I feel that if a tag is prefixed by team-, it is more intuitive that this is a group of people doing work.

@mattdm

Let me throw another wrinkle in here: Discourse just merged a feature request of mine, FIX: Improve tags in email subjects and add filter headers (#19760) · discourse/discourse@c4ea158 · GitHub — which means that there will now be X-Discourse-Tags: to filter on, and people using procmail or mail clients with sensible filtering options should change to use that whenever it becomes available — probably at the next site update. So we definitely should wait for that at least.

Sure, I think it is fine to wait for this to work its way into a mainline Discourse release. But as you noted, for Gmail users (as well as other email web clients, even some desktop client filters like Thunderbird), this won’t have an impact.