Hi Folks,
I’d like to propose transitioning our chat platform from Zulip to Slack. While both platforms have their strengths, I believe Slack offers a more robust and widely adopted solution for our needs. *Why Consider Slack?* 1. *Broader Adoption*: Slack is widely used across organizations, making it easier for new members or collaborators to join and chat seamlessly. 2. *Performance and Stability*: Slack consistently outperforms Zulip in terms of reliability. I’ve experienced occasional crashes with Zulip on my laptop, which can disrupt productivity. 3. *Retention Period*: Slack provides a shorter retention period for chat history. However, this should suffice as chat tools are primarily used for quick responses. For more formal communication, such as proposals, release votes, or other critical discussions, we will continue to prioritize the use of email lists. *Proposed Transition Plan* - *Gradual Rollout*: We can implement Slack alongside Zulip for a transition period of 3 months. This allows team members to adapt and provide feedback before fully committing. - *Historical Access*: We don’t need to shut down the Polaris Zulip instance. Keeping it active ensures historical chat data remains accessible for future reference. I’d love to hear your thoughts on this proposal. If there’s interest, I can take the lead on outlining next steps, including setting up Slack and ensuring a smooth transition for the team. Looking forward to your feedback! Yufei
