@Salt: I’ve converted each of the subcategories in #shoveling and #support to tags, which are required for each post and restricted to their respective categories. I moved posts in the legal and infrastructure categories to #shoveling:semi-private, although I think most of them can be fully public. I also moved #unsure above #restricted in the category list, to preserve the order for folks who can see #restricted (personally I always forget that #unsure exists; this helps).
I have a couple new observations and outstanding niggles:
The tagging restrictions are not enforced for forum admins (the same as posting restrictions, where we weren’t able to prevent mods/admins from posting in top-level categories). So folks who have those permissions will just need to remember to tag their posts.
I’m not sold on getting rid of the Announcements subcategories. They have very clear boundaries so I don’t feel any tension about where they go, and I think it’s useful to have them displayed in the main categories list, whereas tags aren’t shown so prominently.
I’m still skeptical that this will resolve my Tension about forum categories (f&s vs ctp). I don’t see any way to draw a discrete line between support, feedback, suggestions, and concrete work.
- Support vs feedback: “How do I do X?” also means “It’s hard to figure out how to do X.”
- Feedback vs suggestion: “I wanted to do Y but the site doesn’t let me.” is also “Would you consider adding Y?”
- Suggestion vs concrete work: Mechanism re-proposal: Preshold and similar posts could easily be both.
To clarify: some posts fit squarely in one category or another. My tension is that enough are that I don’t want to spend time figuring out where they belong, or moving them retroactively. Take a look in #support or #general: many of those posts, by current standards, really ought to be in #shoveling. I’m not going to move them, since they’re old enough that it doesn’t really matter, but that situation is just not one that I want to be in… and it’s caused by category boundaries that are vague enough to be fluid over time.
One sufficiently hard distinction I could see drawing is whether the core team is working on it. That is, #shoveling topics should be tracked (linked to a GitLab issue). In that case, we’d probably restrict #shoveling so only team members can create new topics there (although anyone would be able to reply). However, we don’t need to do that (or something like it) yet; for now, I’m okay with waiting to see if these changes will help.