Category name to Local communities?

Meta
#1

Hello,

Everything at mozilla is a community then if you have a category with the name community alone is not clear, if this is the place for communities by country or region I think Local communities as name is better.

#2

I think the “Community” category is for general topics and then there are local community subcategories.

#3

My point of is different:

Community (http://mozilla-community.org/) is for general (developers, translators, marketing, QA, documentation … communities) and then there are “local communities” category and each local community have his own subcategory.

Because if you follow the semantic sense of “community” word, then we can ad a developers community inside it but as I can see is not the expected organization because I see developers community at the same level that local communities category and for example webapps developers can be inside of developers communities like UK community inside local communities.

#4

@yousef @tanner Maybe we should move this to Meta, since it’s about this Discourse and its organization (categories names).

#5

True, I agree it’s more clear.

If the QA community/team wants a place in this discourse the best place would be a top level category and not under “Communities”.

#6

Ping @yousef

#7

I agree with this change but is there something shorter than ‘Local Communities’ we can come up with? It would make email subjects smaller (eg [Local Communities/UK]). If not, I’m happy to change it.

#8

Also I think it would be good to clearly define the scope of the parent Local communities category.

Is it just a holder for the subcategories? Is it OK to use it as a regular category, for what kind of topics?

I see a lot of overlap between some topics already in there and mozillians category.

#9

It’s just an idea.
Could enter the word league (or another word) into the lexicon used by Mozilla.
But this required organize hierarchy to make sense.

right now i understand we have something like this:

  • communities (developers, translators, marketing, QA, documentation)
    • webapps developers
  • local communities (COL, UK, JAP, HIS)
    • communities (developers, translators, marketing, QA, documentation)

It could be like this:

  • communities (developers, translators, marketing, QA, documentation)
    • league ( webapps developers )
  • local communities (COL, UK, JAP, HIS)
    • league (developers, translators, marketing, QA, documentation)

Leagues always been inside a community

League:

  1. a covenant or compact made between persons, parties, states, etc., for
    the promotion or maintenance of common interests or for mutual
    assistance or service.
  2. an association of individuals having a common goal.

and for subjects smaller could be like [L/C/…] (eg[L/C/COLOMBIA)]

#10

Discourse doesn’t allow sub-subcategories.

So the only solution would be to create languages as top level categories

  • Language 1
  • Functional area 1
  • Functional area 2
  • Language 2
  • Functional area 1
  • Functional area 2

I also assume some communities already have their own forums to organize all areas and don’t need this.

As an example Mozilla Hispano is going to migrate their discussion forums to its own Discourse instance to organize all areas this way.

#11

I think community is implicit (mozilla-community.org) Then to short every category name you can remove the community word, then [Local/UK] maybe using Moz as prefix or suffix can made better (to know that is Mozilla) the subject [Moz. Local/UK].

#12

@nukeador

I think that language as a main category is not a clean solution, In lang communities as Mozilla Hispano and MozillaFR his own discourse is a very good idea.