Threads for @roles

Discussion
1

This is mostly aimed at @tomnewsom but not to the exclusion of anybody else.

@SarahJ and @timahrensbach had the first marketing meeting, with me chipping in my tuppence. To do the role, we thought we should make two discourse threads. First a thread for us discussing the business of doing it, and second a log of marketing actions done. The business-of-doing-it thread has no need to be public, but it shouldn’t be distracting to others: just like the meeting we just had at the space. The log is meant to be public, so people see what is happening and who was making it.

What’s the discourse structure we should have to do this? Related - in what part of discourse do the blog entries ‘repost’ themselves?

I imagine we’d want something similar for the other roles.

2

If the business-of-doing-it thread was only visible to at-marketing, we could wikify the first post and record social media logins there.

perhaps i’m overthinking this, and it obvs should just be private and that’s that.

3

…aaand i just routed around the settings i have access to, and i don’t think i have the permissions to mess with groups or categories. (and this is not me asking, just saying i looked to see if i could do it myself).

4

The easiest thing to do for the-business-of-doing-it is make a @role-only category, then you can do with it as you wish. Although - not a good idea to keep social media username/passwords online in one place, maybe?

A public record of marketing actions - maybe we could have a @roles category, in which only people with @roles can post, but everyone else can read. That way, @roles can make announcements which don’t get drowned out by feedback/questions.

Blog posts go to #blog, which is currently hidden from the Categories page.

5

Yes, that sounds spot on. A shared @roles log-thread particularly so.

6

Well, I should probably edit it out of this thread if we do. I really don’t know, but suspect six of one and half a dozen of the other: having things spread into individuals’ emails is also letting go of security.

7

The broad question is 'how lucky do you feel about discourse security, punk? ’

Edit: I’ve decided that all my contributions to discourse will be pop culture references from here on in ¥

¥ probably a lie.

8

#roles and #marketing are now open for business.

A thought: #roles has the potential to become an “insider’s forum”

We don’t want that. In fact, the more I think about it, the more it feels like a bad idea.

Small silos for administrating each @role, yes.
Large category that only @roles can post in? no.

9

Um, now I’m not sure I understand. Certainly neither of us wants to create an insiders forum.

Some kind of public log so makerspace org activity is visible but not overwhelming strikes me as worth working out how to make happen. Aiming for something like “marketing met and talked about newsletters”, “toby posted this twitter”, “tool got fixed”.

Are we worried about / do we have options around discourse-implementation, moderation or both?

10

I think a thread in #discussion will be enough - just bump it when something interesting happpens