I don’t think anyone is advocating for using Slack for documenting things.
In my view of the world:
Slack = Hive13 Banter
Google Groups = Hive13 Communication
Wiki = Hive13 Documentation
I understand that some people can’t or don’t wish to adapt and/or keep up with Slack and they are missing out on much of the fun banter. I doubt if that banter can be coaxed back to Google Groups given the degree of ubiquity it has achieve for this purpose. I agree that communication to the entire membership needs be done through Google Groups (which also funnels into a channel in Slack for those of us too lazy to check two paces). I understand that we have not been consistent with using Google Groups for communication - we’ve done a pretty good job but based on feedback we need to do better.
I think the mailing list should be used LESS, not more. This current conversation shouldn’t be here. Regular members shouldn’t be able to post to the group. If it must stay around, and I think there’s a good argument that it shouldn’t, then it should be for the leadership to post things out, like the #announcements channel.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
I fail to see why the google group / mailing list shouldn’t exist.
-D
Get off my lawn!
I totally understand that we could move to Slack & Wiki.
We would just need to actually learn how to use it correctly.
Distinct Slack channels for announcements and thoroughly moderated.
Wiki used for documenting and basic info/projects.
Right now Slack is a barfing of general discussions with some important stuff tossed in.
Is there a way to just get notified of postings in just a channel?
Can we have some training on how to use it properly?
Can we realize that different people think about things differently?
I’m happy to get less email. It does provide a more measured conversation compared to the Twitterverse speed of Slack.
I believe we can merger the different worlds into one beautiful crapfest.
Good times.
Some of us don’t know what the #anmouncements channel even means!
Bill