I am currently using Stateful Functions in my application. I use Apache Flink for stream processing, and StateFun as a hand-off point for the rest of the application. It serves well as a bridge between a Flink Streaming job and micro-services.
I would be disappointed if StateFun was sunsetted. Its a good idea. If there is anything I can do to help, as a contributor perhaps, please let me know. > On Apr 3, 2023, at 2:02 AM, Martijn Visser <martijnvis...@apache.org> wrote: > > Hi everyone, > > I want to open a discussion on the status of the Statefun Project [1] in > Apache Flink. As you might have noticed, there hasn't been much development > over the past months in the Statefun repository [2]. There is currently a > lack of active contributors and committers who are able to help with the > maintenance of the project. > > In order to improve the situation, we need to solve the lack of committers > and the lack of contributors. > > On the lack of committers: > > 1. Ideally, there are some of the current Flink committers who have the > bandwidth and can help with reviewing PRs and merging them. > 2. If that's not an option, it could be a consideration that current > committers only approve and review PRs, that are approved by those who are > willing to contribute to Statefun and if the CI passes > > On the lack of contributors: > > 3. Next to having this discussion on the Dev and User mailing list, we can > also create a blog with a call for new contributors on the Flink project > website, send out some tweets on the Flink / Statefun twitter accounts, post > messages on Slack etc. In that message, we would inform how those that are > interested in contributing can start and where they could reach out for more > information. > > There's also option 4. where a group of interested people would split > Statefun from the Flink project and make it a separate top level project > under the Apache Flink umbrella (similar as recently has happened with Flink > Table Store, which has become Apache Paimon). > > If we see no improvements in the coming period, we should consider sunsetting > Statefun and communicate that clearly to the users. > > I'm looking forward to your thoughts. > > Best regards, > > Martijn > > [1] https://nightlies.apache.org/flink/flink-statefun-docs-master/ > <https://nightlies.apache.org/flink/flink-statefun-docs-master/> > [2] https://github.com/apache/flink-statefun > <https://github.com/apache/flink-statefun>
