Replies: 1 comment
-
I have been thinking about moderator role that could edit and delete questions/answers that are not their own. Managing tags could also be part of that role. And it should use the Backstage permission framework to distinguish the moderators from normal users. This requires some changes to the current permission checks that are done all the way in the database level + UI changes for moderating the tags etc. If there is someone interested to contribute to this, it would be much appreciated. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We were trying to think about how to scale Tag governance a bit better. It's either a bit of anarchy or we use the app-config which works for a handful, but may get a bit crazy if you have a reasonable about of Tags. Not to mention restarting the instance to get a new Tag is not ideal.
Figured a middle path is to have trusted moderators able to create Tags. This creates some friction in the system, but a loose taxonomy can fall apart quickly. Need to figure out the feedback loop for the moderators though. Could be a UI component with RBAC to do some of these basics.
Also had thought about an external git process that would directly insert into the database as well, but trying not to go too out of band.
Does anyone else have creative approaches to Tag governance to avoid all the permutations and regular cleanup/consolidation needed to keep things discoverable?
Beta Was this translation helpful? Give feedback.
All reactions