|
| 1 | +--- |
| 2 | +slug: moving-forward-new-slack-workspace-and-discord-server |
| 3 | +title: "Moving Forward: New Slack Workspace and Discord Server" |
| 4 | +description: "Update on our community communication channels: new Slack workspace and Discord server established, with mailing lists remaining our primary channel." |
| 5 | +authors: [asfcloudberry] |
| 6 | +tags: [Announcement] |
| 7 | +image: /img/blog/new-slack-workspace-and-discord-server.png |
| 8 | +--- |
| 9 | + |
| 10 | +On April 1, 2025, our `apache-cloudberry.slack.com` workspace became inaccessible due to Slack's policy changes affecting services originating from certain regions. While the timing coincided with April Fools' Day, this was unfortunately not a joke—it was a real incident that impacted our community's real-time communication channel. |
| 11 | + |
| 12 | +<!-- truncate --> |
| 13 | + |
| 14 | +## What Happened |
| 15 | + |
| 16 | +On April 1, 2025, we were surprised to find our workspace suddenly inaccessible. After contacting Slack support, we received confirmation that our workspace was affected by a policy change regarding workspaces created from certain regions. While Slack had sent a notification email to the workspace's primary owner role about this policy change, it was unfortunately overlooked. We immediately reached out to explore options for data recovery and export, but have not received any updates on this matter. |
| 17 | + |
| 18 | +## Our Response |
| 19 | + |
| 20 | +In response to this situation, we have established new communication channels to ensure our community remains connected: |
| 21 | + |
| 22 | +- **New Slack Workspace**: We have created a new Slack workspace at `asf-cloudberry.slack.com`. You can join using the following invitation link: [https://join.slack.com/t/asf-cloudberry/shared_invite/zt-3um34r7hf-Sh~6jG6hVxlQJo1tbhK2sw](https://join.slack.com/t/asf-cloudberry/shared_invite/zt-3um34r7hf-Sh~6jG6hVxlQJo1tbhK2sw). |
| 23 | + |
| 24 | +- **Discord Server**: We have also set up a Discord server to provide an additional platform for real-time communication. Discord is widely accessible globally and popular among developer communities. You can join our Discord server here: [https://discord.gg/GJrz3Fxf6y](https://discord.gg/GJrz3Fxf6y). |
| 25 | + |
| 26 | +### Historical Channel Archives |
| 27 | + |
| 28 | +For those who wish to access historical conversations from the previous workspace, we have made archives available through Linen: |
| 29 | + |
| 30 | +- Previous workspace (`apache-cloudberry.slack.com`): [https://www.linen.dev/s/cloudberrydb/](https://www.linen.dev/s/cloudberrydb/) |
| 31 | +- Current workspace (`asf-cloudberry.slack.com`): [https://www.linen.dev/s/apache-cloudberry](https://www.linen.dev/s/apache-cloudberry) |
| 32 | + |
| 33 | +## Important Reminder: Mailing Lists Remain Our Primary Channel |
| 34 | + |
| 35 | +This incident reinforces the importance of relying on mailing lists as our primary and official communication channel. As an Apache project, we follow the Apache Way, which emphasizes: |
| 36 | + |
| 37 | +- Mailing lists are the official record: All important discussions and decisions must take place on our mailing lists |
| 38 | +- Transparency and inclusivity: Mailing lists ensure that all community members can participate, regardless of their access to third-party services |
| 39 | +- Permanence: Mailing list archives are maintained by the Apache Software Foundation and will remain accessible |
| 40 | + |
| 41 | +Real-time platforms like Slack and Discord serve as supplementary channels for informal discussions and day-to-day collaboration. However, any significant outcomes or decisions from these platforms should always be summarized and documented on the mailing lists. |
| 42 | + |
| 43 | +### Our Mailing Lists |
| 44 | + |
| 45 | +- Dev mailing list: For development discussions, proposals, and technical decisions |
| 46 | + - Subscribe: [dev-subscribe@cloudberry.apache.org](mailto:dev-subscribe@cloudberry.apache.org) |
| 47 | + - Archives: [https://lists.apache.org/list.html?dev@cloudberry.apache.org](https://lists.apache.org/list.html?dev@cloudberry.apache.org) |
| 48 | + |
| 49 | +- Commits mailing list: For tracking code commits and pull requests |
| 50 | + - Subscribe: [commits-subscribe@cloudberry.apache.org](mailto:commits-subscribe@cloudberry.apache.org) |
| 51 | + - Archives: [https://lists.apache.org/list.html?commits@cloudberry.apache.org](https://lists.apache.org/list.html?commits@cloudberry.apache.org) |
| 52 | + |
| 53 | +For complete information about our mailing lists, please visit our [Mailing Lists page](/community/mailing-lists). |
| 54 | + |
| 55 | +## Looking Forward |
| 56 | + |
| 57 | +While we have established new real-time communication channels, we acknowledge that as third-party services, they may face similar challenges in the future. This is why we remain committed to the Apache Way and continue to prioritize mailing lists as our primary communication channel. |
| 58 | + |
| 59 | +We appreciate your understanding and continued participation in our community. If you have any questions or concerns, please feel free to reach out through any of our communication channels or contact us at [dev@cloudberry.apache.org](mailto:dev@cloudberry.apache.org). |
| 60 | + |
| 61 | +Thank you for being part of the Apache Cloudberry community. |
| 62 | + |
| 63 | +--- |
| 64 | + |
| 65 | +For the discussion thread on this topic, please see the dev mailing list: [https://lists.apache.org/thread/fzdo4y45tv1ro4mlwf0w26ozwbnyj2bf](https://lists.apache.org/thread/fzdo4y45tv1ro4mlwf0w26ozwbnyj2bf) |
0 commit comments