Hi all, GOOD NEWS: After two weeks of negotiation, the Fluss Slack workspace has been successfully restored and will continue operating under the free plan.
Welcome back home: https://apache-fluss.slack.com/ Best, Jark On Mon, 13 Apr 2026 at 15:29, George <[email protected]> wrote: > > Hi there > > ok, thank you... did not realise we still waiting on Slack support, thought > it was communicated last week that a new server will be configured. > > G > > On Mon, Apr 13, 2026 at 9:27 AM Jark Wu <[email protected]> wrote: >> >> Hi George, >> >> The Slack Support team has been responding slowly with a turnaround time of >> approximately three business days per message. Additionally, the frequent >> rotation of supporter has led to context loss, further delaying progress. >> >> In the meantime, we have set up a Discord server as a temporary >> communication workspace: https://discord.gg/HMp5GkwG >> >> Best, >> Jark >> >> On Mon, 13 Apr 2026 at 15:07, George <[email protected]> wrote: >>> >>> Hi guys >>> >>> How are we progressing with spinning up the new Slack server? >>> >>> G >>> >>> On Tue, Apr 7, 2026 at 7:45 AM Giannis Polyzos <[email protected]> >>> wrote: >>>> >>>> This might end up being one-way. >>>> I don't think we have lost much, considering that, for the most part, it >>>> was used for internal communications. On my side, I think it's ok to >>>> proceed with a new workspace creation. >>>> >>>> Best, >>>> Giannis >>>> >>>> On Tue, Apr 7, 2026 at 5:32 AM Jark Wu <[email protected]> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> As we have not yet received a resolution from Slack Support regarding >>>>> the suspended apache-fluss workspace, and I don't when they will reply >>>>> and I'm also not sure whether our worksapce can be restored or not. I >>>>> think we may need to consider creating a new Slack workspace to ensure >>>>> uninterrupted community communication. Note that the new worksapce >>>>> can't preserve the previous historical data from the old workspace. >>>>> >>>>> Please share your thoughts or concerns on this approach. If there is >>>>> general consensus, we will proceed with setting up the new workspace >>>>> promptly. >>>>> >>>>> Best, >>>>> Jark Wu >>>>> >>>>> On Fri, 3 Apr 2026 at 23:08, Jark Wu <[email protected]> wrote: >>>>> > >>>>> > Progress Update: >>>>> > >>>>> > I have contacted Slack Support to request a restoration and received >>>>> > their response. It appears that our workspace was suspended because it >>>>> > is classified under the Hong Kong region, where Slack is discontinuing >>>>> > direct services. >>>>> > >>>>> > The good news: is that our data has not yet been permanently deleted >>>>> > and remains recoverable within the next 90 days. >>>>> > >>>>> > The bad news: Slack initially indicated that restoring access would >>>>> > require purchasing a one-year license. >>>>> > >>>>> > I have replied to clarify our status as an Apache Software Foundation >>>>> > project and am actively negotiating for a free restoration given our >>>>> > non-profit nature. >>>>> > >>>>> > In the interim, please continue using our dev mailing list for >>>>> > community communication. >>>>> > >>>>> > Best, >>>>> > Jark >>>>> > >>>>> > On Thu, 2 Apr 2026 at 15:22, Lorenzo Affetti via dev >>>>> > <[email protected]> wrote: >>>>> > > >>>>> > > crazy stuff, thanks for taking care of this >>>>> > > >>>>> > > On Thu, Apr 2, 2026 at 6:07 AM Jark Wu <[email protected]> wrote: >>>>> > > >>>>> > > > Hi all, >>>>> > > > >>>>> > > > It seems the fluss slack workspace has been deleted. But I don't >>>>> > > > know >>>>> > > > why and who deleted it. >>>>> > > > >>>>> > > > We have already contacted Slack Support to investigate the cause and >>>>> > > > request potential restoration. We are actively following up on this >>>>> > > > matter. >>>>> > > > >>>>> > > > In the meantime, please continue to use the mailing lists for >>>>> > > > project >>>>> > > > communication. We will provide an update as soon as we have more >>>>> > > > information from Slack. >>>>> > > > >>>>> > > > We apologize for any inconvenience this may cause and appreciate >>>>> > > > your >>>>> > > > patience. >>>>> > > > >>>>> > > > Best, >>>>> > > > Jark Wu >>>>> > > > >>>>> > > > On Thu, 2 Apr 2026 at 10:12, Vaibhav Kumar <[email protected]> >>>>> > > > wrote: >>>>> > > > > >>>>> > > > > It shows it has been deleted. >>>>> > > > > >>>>> > > > > On Thu, 2 Apr 2026 at 3:30 AM, Keith Lee <[email protected]> >>>>> > > > > wrote: >>>>> > > > > >>>>> > > > > > Hello all, >>>>> > > > > > >>>>> > > > > > It seems that I am unable to access the slack workspace. >>>>> > > > > > >>>>> > > > > > I have raised a Jira on INFRA and infra team has indicated that >>>>> > > > > > the >>>>> > > > slack >>>>> > > > > > workspace is not maintained by them: >>>>> > > > > > https://issues.apache.org/jira/browse/INFRA-27794 >>>>> > > > > > >>>>> > > > > > Would appreciate if someone can identify the workspace manager >>>>> > > > > > and / >>>>> > > > > > or follow up to reinstate the workspace. >>>>> > > > > > >>>>> > > > > > Thank you >>>>> > > > > > Keith >>>>> > > > > > >>>>> > > > >>>>> > > >>>>> > > >>>>> > > -- >>>>> > > Lorenzo Affetti >>>>> > > Senior Software Engineer @ Flink Team >>>>> > > Ververica <http://www.ververica.com> >>> >>> >>> >>> -- >>> You have the obligation to inform one honestly of the risk, and as a person >>> you are committed to educate yourself to the total risk in any activity! >>> >>> Once informed & totally aware of the risk, >>> every fool has the right to kill or injure themselves as they see fit! > > > > -- > You have the obligation to inform one honestly of the risk, and as a person > you are committed to educate yourself to the total risk in any activity! > > Once informed & totally aware of the risk, > every fool has the right to kill or injure themselves as they see fit!
