And some times not…
If I’m not wrong, it was discussed when Ask and Discussion were merged.
If I’m not totally wrong, people explicitly asked to use “*-team” only for project discussions and not for support requests in order to avoid confusion and mixes between team workflows and user requests.
Documentation is good, just putting everything under Moderator Coordination is not optimal.
The draft we do have now, covers admin and user tasks too. Best would be like the discourse manual does, to separate in user, admin & moderation-tasks.
This way wen we make a poll where users are involved, we can link the draft for them in a public space. That they can see for what this tags are and what the intention is, alias how they should be used.
I do remember when we merged ask to discussion, we combined that the -team, -wg, and -sig? tags have been created to filter information.
If we make this tags just available for the discussion section, we will cut the communication between ask and discussion. The idea is, tat at least one member of each team also looks the ask.fp.o to support if we do need their attention.
More useful would be, when just TL3 and above, could set this kind of tags.
I had them set to only be allowed there, as that’s the entire intent of having separate tags. I’m not sure how it got changed to allow them. Maybe accidental. I’m inclined to just go ahead and put them back to restricted. Any objections?
Moderators can break the tagging rules. (A “feature” I am not fond of!) I’m not sure if that’s true of TL3/TL4.