Fork me on GitHub
#community-development
<
2016-09-09
>
ricardo19:09:14

@seancorfield i agree with the rename of #announce-to-everyone , but I suggest you rename it to something admin-specific. If you name it #lobby, it reads as free-for-all. Maybe #admin-announcement would send a clearer signal.

seancorfield19:09:53

Good input. Naming is hard.

ricardo19:09:07

At least if you do it right once, you don’t have to deal with cache invalidation.

shaun-mahood19:09:51

@seancorfield: For the new announcements channel, is it going to be acceptable to have follow up conversations there as well? It would be really nice to get rid of the need for anyone to police it.

ricardo19:09:26

If it’s admin-only, I expect only admins will have write-rights. Otherwise we’re back to conventions and expecting people to respect them. Might as well keep it as is.

seancorfield19:09:15

@shaun-mahood I suspect we won’t police follow-ups at all since it will be possible to opt out of the channel if you don’t like the noise 🙂 That’s kind of the point of making this switch. I suspect that folks indulging in extended discussion in the #announcements channel will be asked to take it somewhere more appropriate if it annoys people.

seancorfield19:09:33

Admins can’t switch #announce-to-everyone to admin-only, only an Owner can do that and the two Slack Owners are not currently online to do that (we had the discussion, we agreed on the path of action, we announced the intent, we’ll close the loop "soon").

seancorfield19:09:17

As @ricardo suggested we only want to rename it once so we’ll do that when we make it admin-only (and so we’re open to naming suggestions until that point 🙂 )

shaun-mahood19:09:54

I like #admin-announcements to go with my green bikeshed.

ricardo19:09:21

@shaun-mahood I object to your coloring preferences!