ADD "NO LONGER MAINTAINED" NOTICE

[chase2981]

Checklist

• [x] I have included information about relevant versions
• [x] I have verified that the issue persists when using the master branch of Faust.

Steps to reproduce

Tell us what you did to cause something to happen.

Expected behavior

Tell us what you expected to happen.

I expected to not have to dig into all the different issues nor look into all the last published dates, etc, in order to be able to tell that this project is actually no longer maintained.

Actual behavior

Tell us what happened instead.

I had to dig into all the different issues and look into all the last published dates, etc, in order to be able to tell that this project is actually no longer maintained.

See https://github.com/robinhood/faust/issues/468#issuecomment-810739444 for more details.

Full traceback

Paste the full traceback (if there is any)

Versions

• Python version - 3.6+
• Faust version - all
• Operating system - Mac
• Kafka version - all
• RocksDB version (if applicable)

[vcabral19]

That's a shame if it's true, this project had a lot of potential

[ryou90]

Please take a look at the faust-streaming fork ;)

[chase2981]

My question to @ask is—did Robinhood move away from Faust itself internally at some point or something I’m assuming? If so when? And why? Lastly, what alternative python Kafka package did it move to?

I noticed you guys forked Kafka-python in or around November of 2018, which is around the same time Faust was last published. I’m therefore assuming that’s what Robinhood ultimately moved to?

Thank you for any additional insight. 🙏

Hopefully you’ll actually see this and respond one of these days... ☹️

[chase2981]

Please take a look at the faust-streaming fork ;)

I appreciate you trying to make this project live on as a community-driven project. Robinhood should honestly have the dignity to at very least hand this project over to people like you.

It’s really just sad in my view. My org had tons of faith in this package originally given the fact that Robinhood was behind it and given how “Robinhood uses Faust to push billions of events daily” but since discovering Robinhood has all but neglected Faust without even saying anything to the community about it—it’s completely changed my whole perspective of Robinhood as a company for the worse.

Like who does that? It sounds like something some solo programmer might do on a lib he or she set up previously that they have since forgotten about—not what a multi billion dollar company would do. If google or any other major player did this with any of their open source projects there would be complete outrage. I will never trust any software from Robinhood again after this tbh, and luckily my org even caught this in time before getting in too deep with Faust, we had only started implementing it in our own projects.. We just came from another kinesis streaming lib that stopped being maintained out of nowhere around 2018 too.. At least Leo had the dignity to say so however. Even still, it’s been a complete nightmare to have to deal with since across our entire organization—hence why we were looking to Kafka and Faust in the first place.

Going forward we are only working with projects that are highly supported across multiple programming languages to minimize the chances of this ever happening again. (And for consistency reasons, we have .net core micro services that need to speak to Kafka too)

[zerafachris]

Hi @chase2981 What did you end up pursuing at the end?

[m4nuC]

For reference here is the link to the community fork mentioned above: https://github.com/faust-streaming/faust. Hopefully, Robinhood will pass the wheel to the community

[austinnichols101]

@chase2981 - would be glad to discuss in further detail on slack (see link below).

I'm not with Robinhood, but have been active in the community along with a number of others before and after the original project went "dormant". We did try for a while to get Robinhood to add outside maintainers, but were unsuccessful.

As others have said, the project is alive and well - just not here. Please join us in the fork location:

https://github.com/faust-streaming

Many of the major issues have been resolved since the fork was created and there are also some very nice improvements. There are also forked versions of the mode library which faust depends on and python-rocksdb which was unmaintained elsewhere and out-of-date.

There was a new release 0.6.6 3 days ago (note that the version numbers for faust-streaming are different than for faust).

Also there is an active community at:

Slack

For discussions about the usage, development, and future of Faust, please join the fauststream Slack.

https://fauststream.slack.com
Sign-up: https://join.slack.com/t/fauststream/shared_invite/enQtNDEzMTIyMTUyNzU2LTIyMjNjY2M2YzA2OWFhMDlmMzVkODk3YTBlYThlYmZiNTUwZDJlYWZiZTdkN2Q4ZGU4NWM4YWMyNTM5MGQ5OTg

Why the fork

We have decided to fork the original Faust project because there is a critical process of releasing new versions which 
causes uncertainty in the community. Everybody is welcome to contribute to this fork, and you can be added as a maintainer.

We want to:

- Ensure continuous releases
- Code quality
- Use of latest versions of kafka drivers (for now only aiokafka)
- Support kafka transactions
- Update the documentation