Move away from Zoom (#342)

* Move away from Zoom * Update catchups.md * Update work-process.md * Update hiring.md * Update how-we-work.md * Update 2_Operations/apps.md Co-authored-by: Janez Troha <[email protected]> --------- Co-authored-by: Janez Troha <[email protected]>
teamniteo · Jan 17, 2024 · eb8a21e · eb8a21e
1 parent d04c6bf
commit eb8a21e
Show file tree

Hide file tree

Showing 5 changed files with 13 additions and 11 deletions.
diff --git a/2_Operations/apps.md b/2_Operations/apps.md
@@ -14,7 +14,7 @@ Here is how we set reminders for meetings in Slack:
 Set up reminders on the week they should be posted before reminder post time.
 
 Weekly:
-/remind #operations every Monday at 11:50 UTC “Meeting in 10 minutes! Join the appropriate Zoom room or write an #out-of-office message if not attending”
+/remind #operations every Monday at 11:50 UTC “Meeting in 10 minutes! Join the appropriate Slack's huddle or write an #out-of-office message if not attending”
 /remind #operations every Monday at 11:59 UTC “@here Meeting starting now!”
 ```
 

diff --git a/2_Operations/how-we-work.md b/2_Operations/how-we-work.md
@@ -4,13 +4,15 @@ Niteo is a distributed team spread around the World. Here's a quick overview of
 
 ## Communication
 
-Written communication can sometimes be misinterpreted and could lead to the other person's heartrate going up.
-A bad example of this can be: "Hey, do you have some time to talk?".
-If a senior Nitean sent such a message to a trialist, they might interpret it as "Oh no, I did something wrong" and start stressing out completely unnecessarily, since the senior Nitean just wanted to ask them if they have any dietary or other preferences for the upcoming IRL. Or imagine sending over `Hey, do you have some time to talk on Monday?`. There goes the weekend!
+Written communication can sometimes be misinterpreted and could lead to the other person's heart rate going up for no reason. 
+
+A bad example of this can be: "Hey, do you have some time to talk?". If a senior Nitean sent such a message to a trialist, they might interpret it as "Oh no, I did something wrong" and start stressing out completely unnecessarily since the senior Nitean just wanted to ask them if they have any dietary or other preferences for the upcoming IRL. Or imagine sending over `Hey, do you have some time to talk on Monday?`. There goes the weekend!
+
 To avoid that, we encourage Niteans to state what they want from the other person, what they would like to talk about, and where they would like to talk about it, e.g. chat, voice, or video.
-A good example of this can be: "Hey, I'd like your opinion on which approach is better for the project. Can we meet on Zoom?".
 
-Instant messaging is done through Slack on different channels (operations, support, development etc.). We have standups on Zoom every Monday and Thursday at 12 noon UTC, where everyone has a minute or two to say what they’re working on and if they need any help.
+A good example of this can be: "Hey, I'd like your opinion on which approach is better for the project. Can we meet on huddle?".
+
+Instant messaging is done through Slack on different channels (operations, support, development etc.). We have standups on Slack huddles every Monday and Thursday at 12 noon UTC, where everyone has a minute or two to say what they’re working on and if they need any help.
 
 Twice a month, senior team members have [Catchups](../5_People/catchups.md) with everyone on the team to keep themselves in the loop.
 

diff --git a/2_Operations/work-process.md b/2_Operations/work-process.md
@@ -3,7 +3,7 @@
 ## Schedule
 
 * Every **Monday** we have a [meeting](https://github.com/teamniteo/handbook/blob/master/2_Operations/kanban.md#monday-meetings):
-   * 12:00 UTC for the whole company in the Niteo Zoom room followed immediately by separate meetings for the projects in their own Zoom rooms.
+   * 12:00 UTC for the whole company in the #operations channel huddle followed immediately by separate meetings for the projects in their own channel huddles.
 
 * Every weekday Niteans should check their [GitHub notifications](https://github.com/notifications) so that they don't miss things that involve them.
 
@@ -39,7 +39,7 @@ As an attendee, ask yourself:
 
 As a curator:
 
-- Organize which time to have the session and annoince it in #development when it's time to join and which Zoom room to use.
+- Organize which time to have the session and annoince it in #development when it's time to join and which Slack huddle to use.
 - Prepare a joke or something funny to share.
 - As a curator, meet and greet everyone, especially first-time joiners.
 - Announce who is having the Lightning talk if one was prepared.
@@ -53,7 +53,7 @@ While working on user stories we often need to change code or text that we keep
 
 To ensure that your commits and Pull Requests contain everything necessary for a successful review, read through the [Git](/3_Development/git.md) guide for the best practices.
 
-When a User Story or Pull Request is getting close to being completed but there are still open issues, Niteans should have a discussion on Zoom. We don't want to see long PR discussions on GitHub. The **author** of the issue should ping people on Slack and get them on Zoom to polish things.
+When a User Story or Pull Request is getting close to being completed but there are still open issues, Niteans should have a discussion. We don't want to see long PR discussions on GitHub. The **author** of the issue should ping people on Slack and get them on Slack huddle to polish things.
 
 ## Continual Improvement
 

diff --git a/5_People/catchups.md b/5_People/catchups.md
@@ -9,7 +9,7 @@ Catchups and Career Path notes are stored in your private [Niteo Career](https:/
 
 ## Schedule
 
-Meetings will be scheduled at a suitable time and day every two weeks. They can be on Zoom, by phone or in person. They are usually 30 minutes in length but can take longer if needed.
+Meetings will be scheduled at a suitable time and day every two weeks. They can be on Slack huddle, by phone or in person. They are usually 30 minutes in length but can take longer if needed.
 
 They should not be cancelled unless unavoidable, such as an emergency.
 

diff --git a/5_People/hiring.md b/5_People/hiring.md
@@ -40,7 +40,7 @@ Recruitee guides us through the following stages of hiring a new Nitean. A candi
 
 **4. Phone Screen**
 
-   A chat over Skype, Hangouts or Zoom with @marbeann. Calls can last anywhere between 10 to 30 minutes. The goal is to confirm the candidate is able to communicate via video conferencing. Is their connection OK? Is their English OK? Can they hold a discussion on a subject?
+   A chat over Zoom with @marbeann. Calls can last anywhere between 10 to 30 minutes. The goal is to confirm the candidate is able to communicate via video conferencing. Is their connection OK? Is their English OK? Can they hold a discussion on a subject?
 
    @marbeann also confirms the following:
    * Weekly commitment for the trial period (full- or part-time).