Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.

Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.

Comments on Make proposed community tags mandatory

Post

Make proposed community tags mandatory

+2
−0

Every question in the Incubator Q&A category should have 1 or more tags for a proposed community, so that it is clear which community or communities the question is intended for.

Currently it is possible to add a question without adding a proposed community tag. Could the presence of such a tag be made mandatory, in the same way as the mandatory tags on Codidact's Meta categories must have at least 1 applied?

The Codidact Proposals Meta category also does not have any mandatory tags, unlike other Codidact communities' Meta catagories. Should this also be changed?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Not saying this is a bad idea, but it will put a load on the admin team because adding a tag to the r... (7 comments)
Not saying this is a bad idea, but it will put a load on the admin team because adding a tag to the r...
Moshi‭ wrote about 1 year ago

Not saying this is a bad idea, but it will put a load on the admin team because adding a tag to the required tag set requires admin permissions.

Secondly, it poses a UI problem (image). The list of required tags will likely only grow.

trichoplax‭ wrote about 1 year ago

I wonder if there's a way to reduce the admin burden without introducing too much chaos.

What if anyone could add a proposed community tag, but only admins could delete/downgrade them?

trichoplax‭ wrote about 1 year ago

For the UI problem, dealing with that might also help if there are other instances in future that have other reasons for larger numbers of mandatory tags.

trichoplax‭ wrote about 1 year ago

Even so, we would probably need to make sure mandatory tags are deleted as their proposed communities migrate, so the list doesn't get too long.

Moshi‭ wrote about 1 year ago

Data integrity may be an issue if a required tag is deleted, since posts that use that tag won't have it anymore, causing them to have zero required tags.

IIRC, this has been tested before and found to not visibly break things since I believe the requirement is only checked at submission, but it's still worth thinking about since it is not a state that the system currently expects.

trichoplax‭ wrote about 1 year ago

Yes it's probably worth implementing a check at migration stage. Ideally the migration of all of the questions for a given community tag should leave none remaining with only that community's tag.

A question with more than one community tag would presumably be copied to the new site rather than migrated, so that the original remains for the other communities. In this case the migrating community's tag can safely be removed due to the presence of other community tags.

There are probably other edge cases we won't think of so having extra checks in place seems sensible.

Monica Cellio‭ wrote about 1 year ago

It wouldn't be more of an admin burden than adding it to the "topic tags" list, which is what we do now.

For proposals that are no longer active, we don't have to delete the tag, just remove it from the list of required tags. If a question has more than one community tag and we're going to launch one of them, we'll ask the people involved to decide what to do with that question first.