Organisation of Discourse within Mozilla

[leo (Leo McArdle)]

@majken

You can’t say the experiment hasn’t worked without defining the bounds of the experiment.

I said the experiment hadn’t worked for what I’m working on, not generally. For what I’m working on, it gets in the way.

@majken

For keeping people informed who aren’t on the team and doing hands-on work, the pathway is still supposed to be Discourse.

I think Discourse should also be the method of keeping people involved who are on the team. Furthermore, there’s a whole loads of JIRA issues which need discussion before they can be done, discussions which should surely be happening on Discourse.

@majken

We have a plan to make communication better, but we’ve been slow to implement it. Slightly frustrated that the result has been to start a totally new discussion topic without that context, rather than helping to implement the plan we already have.

But I didn’t intend this to be a discussion about communication, I intended this to be a discussion about the organisation of Discourse within Mozilla.

@majken

We need to announce the “Using Discourse” category, which was waiting on organizing the topics.

I think this should be renamed back to Meta, and should be where the Discourse team discussions happen, but I’ll start another topic about that.

@majken

I agree with the 3 categories of contribution. They look good, and the don’t really seem like anything revelatory based on how we’ve already been thinking.

They’re not just categories of contribution, though, they’re separate teams. Different categories of contribution doesn’t stop discussions which have nothing to do with ops happening in the Community Ops IRC channel, in Community Ops meetings and in the Community Ops category here.