I’m very happy about the idea to use this category and to simplify
communication channels. I have some questions about directly merging this
category and renaming it though.
The idea behind this category is to give people a place to come to get or
give webdev help, similar to Community Ops, with an intended focus on
helping out with community sites. Those sites don’t necessarily live under
Participation Infrastructure. Also, I think Participation Infrastructure is
more complex than just webdev, right? What I’m wondering is if the intended
audience/purpose would be the same or if it would change?
Also would you see any problems arise from having the Ops side of things in
its own category? I can imagine that if there is a Participation
Infrastructure category then the ops tasks for those projects would just be
discussed in that category meaning that ops volunteers would need to watch
both categories. Of course this is one of the advantages of Discourse, it’s
easy to watch multiple categories so they can be more fine-grained.
This isn’t the first time I’ve had an issue with figuring out the best way
to nest categories. In several cases the parent category and the
sub-category could be flipped depending on how you want to look at it.
Discourse currently gives us 3 levels to organize categories - category,
sub-category, and you could use the same colour scheme across categories to
denote a relationship. What I’m thinking is, if Participation
Infrastructure is the parent category, then it would make sense for
Community Ops to be a sub-cateogry, just like webdev, but we definitely
need our sub-categories as it is.
I think this thread would interest you -
https://discourse.mozilla-community.org/t/discourse-multi-site/1424/2 - as
it discusses some issues like this and we need to decide which path to take
to try to address them.
What do you think of leaving Community WebDev so named, and having
sub-categories for the different projects? This could include a
Participation Infrastructure sub-category, though I agree with you it makes
sense for you to use the main category for general discussion and
sub-categories for specific discussion. Or having a Participation
Infrastructure category separate from Community Ops/Community WebDev, but
with the assumption that they would share audiences and sometimes cross
The nice thing about Discourse is that this is all flexible, we can always
rename/name-back or merge/split categories if we change our minds later.