Implement a Public Slack Space For the Wider GitLab Community
Purpose
This issue is to discuss how to move forward with the implementation of a public slack instance for the wider GitLab Community.
Migration
For getting things up and running, do it in the minimal way as possible.
- Instance and admin accounts
- A selected number of channels
- Bots for automation: Create a list and test-drive them
- User migration: Evaluate scripts/ways
- Evaluate which capabilities can be re-used from GitLab company Slack
What does a migration from Gitter to Slack mean? (I don't know if this is possible):
- Pinned message about the migration for one month. Team members still expected to respond to users in Gitter until deprecation deadline. During this time we also need to find all mentions of Gitter on our website and other material and reference Slack instead
- After one month, a bot sends a message to users when they use Gitter asking them to request an invite to Slack and continue there.
- Gitter channels permanently close with a message after 3 months?
WIP: Timeline
A sample / example timeline: (from @nuritzi)
- Set up Slack: 2 weeks
- Promote internally: 2 weeks. Ensure a critical mass of at least 40 (?) people.
- Promote externally + transition Gitter: 1 month
- Permanent shut-down of Gitter channels in 3 months
WIP: Setup
- introductions - Introduce yourself and meet others!
- meta - Help us make this GitLab slack useful and awesome. Let us know what we can improve.
- announcements - join for announcements about what's happening at GitLab.
- heroes - A space for GitLab Heroes or questions about the program
- general - public discussions about GitLab
- random - (just for fun?)
cc. @gitlab-com/marketing/community-relations @gitlab-com/marketing/community-relations/community-operations
Iterations welcome in the comments!