Hi all, Thanks for your great ideas and input. I would like to do a quick summary here. If there are no strong objections, we can move forward with this approach.
This Slack policy change has impacted multiple ASF communities, which reinforces the importance of relying on the mailing list as our primary and official communication channel. I believe we will continue to treat the mailing list as the primary and official communication channel for the community. All important discussions and decisions should take place there. Real-time platforms are intended for informal discussions only, and key outcomes should always be summarized back to the mailing list. For real-time communication, we can introduce complementary platforms to improve day-to-day collaboration and accessibility: * Slack: widely adopted in professional and enterprise environments * Discord: more accessible globally and active among developer communities Both platforms have their own strengths, and using them in parallel can help us reach a broader audience while avoiding reliance on any single service. If Greg is available, it would be great if you could help set up a new Slack workspace (e.g., asf-cloudberry.slack.com). I can also create a Discord server and invite interested members to join. As a side note, we are still in contact with Slack support regarding the recovery of the original workspace, but there has been no update so far. Best, Dianjin Wang On Fri, Apr 3, 2026 at 2:42 AM Kirill Reshke <[email protected]> wrote: > > There is both official discord server & slack workspace on PostgreSQL > kernel hacking. huh > > On Thu, 2 Apr 2026 at 14:05, Greg Spiegelberg <[email protected]> wrote: > > > > Nothing wrong with discord or others however more professionals have and > > use slack. We want it to be easily found and available to them. > > > > If it is simply a question of "who creates a new slack from where", I can > > do it. > > > > On Thu, Apr 2, 2026 at 3:00 AM Leonid Borchuk <[email protected]> wrote: > > > > > Hi! > > > > > > + 1 for Discord > > > > > > We could also use Telegram, SimpleX, WeChat, but they are not so familiar > > > for the other countries. > > > > > > WBW, Leonid > > > > > > On Thu, Apr 2, 2026 at 7:02 AM Dianjin Wang <[email protected]> wrote: > > > > > > > Cool! Discord is also a great choice. > > > > > > > > > > > > Best, > > > > Dianjin Wang > > > > > > > > On Thu, Apr 2, 2026 at 11:54 AM Jianghua Yang <[email protected]> > > > wrote: > > > > > > > > > > Discord +1 > > > > > > > > > > On Wed, Apr 1, 2026 at 20:45 Kirill Reshke <[email protected]> > > > > wrote: > > > > > > > > > > > On Thu, 2 Apr 2026 at 08:37, Dianjin Wang <[email protected]> > > > > wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > Hope this is not an April Fool's joke, but just received an > > > official > > > > > > > response from Slack regarding this matter. > > > > > > > > > > > > > > Slack has confirmed that our workspace was impacted by a > > > > > > > previously > > > > > > > communicated policy change affecting Slack services originating > > > from > > > > > > > mainland China, Hong Kong, and Macau. Workspaces created from > > > > > > > these > > > > > > > regions were scheduled for suspension, and as of April 1, 2026, > > > > > > > our > > > > > > > workspace is no longer accessible. Sincerely apologize for any > > > > > > > disruption this has caused. Now, trying to discuss the possibility > > > of > > > > > > > exporting our historical data from the suspended workspace. > > > > > > > > > > > > > > Moving forward, I think we need to establish a new, reliable > > > platform > > > > > > > for our community's real-time communication besides the mailing > > > list. > > > > > > > I think we have two primary options: > > > > > > > > > > > > > > 1. New Slack Workspace (free plan): We could create a new Slack > > > > > > > workspace. This would require a community member from the Slack > > > > > > > service region to assist with its setup and administration, > > > utilizing > > > > > > > a free plan. > > > > > > > > > > > > > > 2. Migrate to Zulip: Alternatively, we could migrate our community > > > > > > > communication to Zulip. Zulip is an open-source, powerful group > > > chat > > > > > > > platform that is already being used by several other Apache > > > projects > > > > > > > (you can see more at: https://zulip.com/communities/#opensource). > > > > They > > > > > > > offer dedicated plans for open-source communities. > > > > > > > > > > > > > > Personally, I prefer the second option—migrating to Zulip. This > > > > choice > > > > > > > would provide a more globally friendly and resilient communication > > > > > > > platform, free from region-specific service restrictions, ensuring > > > > > > > better accessibility and inclusivity for all our community members > > > > > > > worldwide. > > > > > > > > > > > > > > Please share your thoughts. Sure, the mailing list is always our > > > > > > > first main channel. > > > > > > > > > > > > > > Best, > > > > > > > Dianjin Wang > > > > > > > > > > > > > > On Thu, Apr 2, 2026 at 10:37 AM Dianjin Wang < > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > I'm writing to inform you that our apache-cloudberry.slack.com > > > > Slack > > > > > > > > workspace has been unexpectedly deleted. This situation is > > > > > > > > highly > > > > > > > > unusual, and we are trying to contact the official Slack support > > > > team > > > > > > > > to understand the cause and facilitate its restoration. > > > > > > > > > > > > > > > > We will provide updates as soon as we have more information. > > > > > > > > > > > > > > > > Best, > > > > > > > > Dianjin Wang > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > Discord maybe?) > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > Kirill Reshke > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > -- > Best regards, > Kirill Reshke > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
