Create basic guidelines for Slack / Restructure existing information about Slack
I am missing basic guidelines. And some basic information, how to use Slack. Now you can find that on general information about Slack, but some is TYPO3 specific, esp. how we use the Slack workspace and how it is organized.
Not sure where these should go. typo3.org / docs.typo3.org?
- guidelines for creating new channels, e.g. add a description (I find this pretty annoying: many channels have no description. What are they about? Some are named similar. I found 3 channels for new people. Several channels with no users. etc. etc.) Example: #edu-general, typo3-education
- naming conventions for channels? (see [draft](TYPO3 Wiki Slack: https://wiki.typo3.org/Slack))
- use threads or not? (this is actually becoming quite an annoyance because some people use threads, others do not. There are some problems with both. With thread: only people in thread get notification. Person who posts original message also gets a notification. some don't want this. Some even state in their profile, they do not use threads. If you don't use threads, everything gets mixed up. You can't reply to things from previous day without creating chaos. This practically forces you to read everything right away if some topics are important to you and others not. This is not an option for me
- Is it ok to create a thread from someone's message. replying in Thread is basically the same as @mention person from which thread is created. (some people explicitly state in their profile, they don't use threads)
- is it ok to direct message people? When yes, when not?
- is it ok to @mention someone (they get a notification)
- how do we get channels closed? Do we just notify an admin? Which one? Do we have a procedure, e.g. no activity for n weeks, close right away, else: notify @channel, then wait m weeks, then close?
- when should you use Slack and when create an issue (depends on team)
my main motivation: have one page about Slack to link to and not worry about the rest.
I think some of the above problems with threads should be less once talk.typo3.org or some alternative is used more.
Ideal result
- I would like to link to a start page about Slack from sections that mention Slack, e.g. https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/HowToGetHelp.html
- the Slack landing page should contain:
- information about registration and link to register (for typo3.org and Slack)
- above mentioned guidelines
- have a shortcut (quick link for this), e.g. typo3.org/slack
Open question
- document this on typo3.org or on docs.typo3.org?
Additional information
Some of the above mentioned information already exists. But I think it should be in one place and get cleaned up.
- my.typo3.org : Slack for TYPO3: https://my.typo3.org/index.php?id=35
- help page: https://typo3.org/help/
- news article How to use Slack in the TYPO3 community
- Contribution Guide: How to register for Slack: https://docs.typo3.org/m/typo3/guide-contributionworkflow/master/en-us/Account/Slack.html#register-for-slack-account
- TYPO3 Wiki Botty: https://wiki.typo3.org/T3Bot
- TYPO3 Wiki Slack: https://wiki.typo3.org/Slack