Discussion: zulip stream naming convention causing 'understanding friction' about rust-forge HOT 7 CLOSED

t- is a weird spelling of T- IMO, which is the label prefix we use in rust-lang/rust.

But also, it's an unnecessary prefix, compiler and compiler/... look fine to me.
For comparison, one Discord there's #compiler, which also works fine.

from rust-forge.

I don't think we should be removing the prefixes because for certain teams it makes the room's topic ambiguous and more prone to spam or offtopic discussion. E.g. #community is not obvious that it's for the community team and not the community. We've been adding -team to a few of the channels on the discord to address this exact issue.

from rust-forge.

I would like to add: I really like there being a 2-char team-name prefix. Makes things MUCH clearer when you realize what it is. I would see 'tm-' as a more temporary thing during the community uptake period, where the broader community is still becoming familiar with it.

from rust-forge.

Thank you for your issue! I think whether it should t- or tm- would be better discussed on Zulip in the #zulip channel. Since it's more likely that the right people will see it.

Personally I lean to keeping t- if only for historical reasons. Regardless I think we can try to address some of what you mentioned by having a section that explains the naming scheme.

Generally I think we'd be well served with a "jargon" page, filled with terms and shorthands like this.

from rust-forge.

I was originally going to post in zulip, but started feeling like a formal submission of an issue. I'll Copy-paste with a link to this issue shortly, and comment there.

from rust-forge.

link to Zulip discussion

from rust-forge.

I'm going to close as it's offtopic for the forge.

from rust-forge.