Communication channels: Difference between revisions
m →Post! |
m →Post! |
||
Line 64: | Line 64: | ||
Some email addresses are automatically cross-posted to Slack channels, for example trustees@nottinghack.org.uk automatically gets delivered to the Trustee slack channel. This allows Slack to be used as a unified inbox, though it is spammed horribly. | Some email addresses are automatically cross-posted to Slack channels, for example trustees@nottinghack.org.uk automatically gets delivered to the Trustee slack channel. This allows Slack to be used as a unified inbox, though it is spammed horribly. | ||
Teams Slack - usefulness diluted by banter and other inappropriate postings eating into clarity of discussion and message longevity. | Teams Slack - usefulness diluted by banter and other inappropriate postings eating into clarity of discussion and message longevity. Also, please do not post the same message to multiple channels, e.g. Laser + Tools when reporting broken or missing tools as this also eats into the message base. |
Revision as of 10:24, 1 December 2016
(Still a Work in progress - being re-created, lost due to timeout!)
Communications methods available to members / users and others to discuss matters related to the Hackspace.
Prioritised by appropriateness for different tasks -
- Longevity
- Security (moderation, etc.)
- Speed of response
- etc...
Wiki
Long term, Hackspace 'documentation'. Seen as not easy to contribute to by some (but an 'expert' can always be found lurking who can assist). Used for monitoring pledge drives (although this function will migrate to HMS in the future).
As well as member-personal emails, there are also a number of addresses set up for formal communication with and by the Hackspace. Ought to be the preferred way of pushing messages (e.g. trustees@...) but like all email, blighted by spam.
Google Group
The public channel. Permanent, searchable, message storage. Moderated.
Anyone joining the google group is initially put under moderation. This is simply to prevent the group from being invaded by 'bots, but moderation has been (and can be) re-instated on occasions when inappropriate postings have become contrary to the best interests of the Hackspace.
Slack
Super-IRC, with the ability to handle media, files and other larger message types. Not permanent, and with a limited mailbox size across all channels, banter and irrelevant comment eats into the lifetime of messages.
No effective moderation (though admins can have messages deleted)
NH-Teams
Originally set up for communication within and between teams. Has been taken over as the go-to communication channel for too many unrelated purposes where the Google Group would be better. May yet be recovered to perform this function.
Trustees
A Slack account is used by the trustees, whose accounts are paid-for, and so a permanent record is kept.
IRC
Long-established geek channel of choice. Transient (unless via a caching proxy)
(Links to message display boards in the 'space)
Telephone
There is no active telephone number for the Hackspace. The line is used only for broadband delivery. Unfortunately Google has found the number and it has become known - don't try and use it!
Post!
Some things just have to be delivered as hard-copy to the Hackspace. Letters are pretty reliable, but packets and parcels should not be expected to be delivered promptly, as it depends on someone regularly checking with the site management to discover if something is awaiting pickup in the management office.
Types of message
- Banter
- Showing Off
- Answers to Questions
- Asking Questions
- Progress reporting
Cross links between channels
Some email addresses are automatically cross-posted to Slack channels, for example trustees@nottinghack.org.uk automatically gets delivered to the Trustee slack channel. This allows Slack to be used as a unified inbox, though it is spammed horribly.
Teams Slack - usefulness diluted by banter and other inappropriate postings eating into clarity of discussion and message longevity. Also, please do not post the same message to multiple channels, e.g. Laser + Tools when reporting broken or missing tools as this also eats into the message base.