i just removed them from my proposal for now. I’m a little worried about moderation being too thin for those
I would rather prefer Language groups to be a separate category. We could use extra levels for communities that might create multiple topics and define their own structure.
E.g.
- Language Groups
- Spanish
- Spain
- Mexico
- Argentina
- French
- Jenkins users
- Jenkins development
- Russian
- St. Petersburg Meetup
- Belarus Meetup
- …
- Spanish
Sub categories are not super clear in the UI, I’ve only tested second level, I cant imagine what 3 would look like. Its probably worth testing at least once.
It might be better to tag posts with languages instead of duplicate categories. It’ll be confusing for users to have to select between two “Jenkins Users”
My vote is just language groups, but not the sub categories until we get enough content that categories make sense.
Agreed. Would you grant me permissions so that I can prototype it?
I’m not sure what you agreed with, but I’m not comfortable messing with permissions. I’m happy to make the categories, or you can wait for one of the others that is more comfortable giving out access.
For what it’s worth it @halkeye, you can totally create a private category with the nested level tests and allow only a few users to access it, without requiring right delegation.
We can also use this opportunity to “try” moderation delegation: creating a parent category, delegate the rights to @oleg-nenashev and see if he can create sub category.
Honestly, there are no risks: worth case is having a category indexed in Google until it’s deleted. Not really an issue: WDYT?
Considering that we are still in experimenting mode, @oleg-nenashev I can grant you access which you will loose in the future as I prefer to as few admin as possible 
Ooooh, GitHub - discourse/discourse-solved: Allow accepted answers on topics is pre-installed. I think it’ll be awesome for support and site feedback categories. Any objections to me enabling it?
Sure, I was also interested by it
I am wondering where the “governance” topic should be?
Under community or contributing? Imho it should be below community but I am curious about other’s people thought
- Community
- Contributing
- Other
0 voters
I turned your post into a poll!
1 Like
Created Language groups - Jenkins
Should we also create categories for SIGs, sub-projects and other topic groups? E.g. “Jenkins on Kubernetes” or “Hardware CI” could be good categories. I would be also interested in a “Jenkinsfile Runner” or “Jenkins Operator” or “Jenkins Helm” category. Maybe tags are enough for some cases.
I don’t have strong feelings about it, but I feel like having too much stuff pre-created, especialy empty, is going to cause confusion. If we have a category called “Helm chart” it’ll almost definatly get support questions, like the configuration as code gitter channel. My vote is to hold off creating categories until the need arises. But i’m not against it if others want to do it.
Thanks for working on this, it looks great.
I just want to share something I stumbled upon while trying to figure out what a category vs tag was in Discourse:
Thought it might be relevant to the discussion at hand:
Over specialising categories is a common problem that manifests itself differently in communities old and new. […] In new communities, this stems from a desire from the founder to make sure that any topic the community could want to talk about is covered. While this is understandable, it will lead to users simply being intimidated by the enormous number of categories at their disposal. In most communities with vast numbers of categories, the majority of them will lie fallow. If a new user posts in one and doesn’t get a response, they’re unlikely to persist much further.
Hope this helps
2 Likes
I’m going to close this so its less intimidating for new users (Since I’m announcing it any time now). I think we had some really great discussions, but I think any new categories or changes should be new topics.
1 Like