Hi all,

I created an "ApacheFluss" workspace in Discord https://discord.gg/HMp5GkwG

Feel free to join the Discord for communication before the Slack workspace
is recovered.

Best,
Jark

On Wed, 8 Apr 2026 at 20:00, Michael Koepf <[email protected]>
wrote:

> I'm fine with creating a new Slack workspace, as the old one has limited
> history anyways due to being on the free plan. In general, I'm also fine
> switching to Discord.
>
> IMO, it's just important to stick to one platform, otherwise messages get
> scattered and it gets difficult to maintain and follow conversations.
>
> --
> Best,
> MKO
>
>
> > On 08.04.2026, at 04:29, tison <[email protected]> wrote:
> >
> > Just for your information,
> >
> > If data privacy and persistence are under consideration, there can be an
> > opportunity for the ASF (INFRA?) to look into Zulip, which is an
> > open-source solution one can host an owned instance.
> >
> >
> > Best,
> > tison.
> >
> >
> > Jark Wu <[email protected]> 于2026年4月8日周三 10:26写道:
> >
> >> Hi all,
> >>
> >> I have some good news to share regarding our Slack workspace. I
> received a
> >> response from the Slack Support team, and they have indicated that they
> can
> >> update our address and restore the workspace once a U.S. billing
> address is
> >> confirmed. I have provided them with the ASF mailing address and am
> >> currently awaiting their reply.
> >>
> >> Additionally, I think Discord is an interesting option to consider.
> >> Providing multiple instant messaging platforms doesn't conflict, and
> >> Discord offers unlimited message history on its free plan.
> >>
> >> Best,
> >> Jark
> >>
> >>
> >>> On Wed, 8 Apr 2026 at 10:22, Nicholas <[email protected]> wrote:
> >>>
> >>> Hi Greg,
> >>>
> >>>
> >>> The ASF project slack workspace needs to invite person to
> >>> join which is not convenient. Meanwhile, the ASFproject workspace has
> >>> Fluss channel that only has two members.
> >>>
> >>>
> >>> Regards,
> >>> Nicholas Jiang
> >>>
> >>>
> >>>
> >>> ----- Original Message -----
> >>> From: "Greg Stein" <[email protected]>
> >>> To: [email protected]
> >>> Sent: Wed, 08 Apr 2026 00:14:49 -0000
> >>> Subject: Re: Slack Workspace Down
> >>>
> >>> Why not just start using the-asf.slack.com like most projects?
> >>>
> >>> Note: it is on a data retention plan. Free plans only hold about 10,000
> >>> messages.
> >>>
> >>> See: https://infra.apache.org/slack.html
> >>>
> >>> Cheers,
> >>> -g
> >>>
> >>> On 2026/04/07 02:31:50 Jark Wu 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>
> >>>>
> >>>
> >>
>

Reply via email to