-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project status #244
Comments
Sounds good to me @dhoepelman, thanks for taking care of this! |
Unfortunately I don't have admin access either. |
Ok next try: @benjchristensen could you please grant write access for the RxScala repo to @dhoepelman? |
Hey I'm an admin on ReactiveX, I'm going to give @akarnokd admin here, and I'll add @dhoepelman as having write permissions. Have a great day and thanks for taking care of this! |
Okay, all is done! @dhoepelman, you should have an invite in your email. |
Thanks @benlesh and @samuelgruetter! |
Hello,
Interest in RxScala seems to have waned over time, in favor of other streaming frameworks in the Scala ecosystem. This is visible in multiple ways
While this is sad for people who like using the Rx model in scala, there are lot of good Scala alternatives in akka streams, monix, cats-effect, fs2 and ZIO (apologies in advance if I missed one). Scala community interest has drifted to those over time. RxJava 3 or Reactor are also alternaties for developers who are willing to use RxScala-like libraries that are less Scala idiomatic
This leaves RxScala 1. My proposal is to put the project in an official End-of-life (EOL) or maintenance only state. This creates clarity about the state of the project and makes sure effort of both potential users and the community is not wasted. It says nothing about a potential RxScala 3 if someone is interested in starting that.
I am willing to perform some work here, which would entail:
I cannot do the second because I have no release rights, so either I would need get those or releases would need to be done when needed by someone else
@zsxwing @samuelgruetter @xuwei-k what do you think?
The text was updated successfully, but these errors were encountered: