-
Notifications
You must be signed in to change notification settings - Fork 197
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
license specifics #402
Comments
So licence is BSD 3-Clause — so you're free copy the code, as long as you maintain the original copyright notice and attribution.
OK, cool, yes... something to think about. Can I ask, what's the difference? Is it essentially just a Maybe there's a neutral rename to be had to save have two packages doing the same thing 🤔 |
hi for this project it was mostly just except for lua scripts that need to be changed to use and i changed the packaging to use also from time to time my tests timeout, i have not discovered the reason yet. I'm not sure what the last sentence means |
I think Carlton's point is that it might make sense to have a single package that is able to handle the functionality of both "redis" and "valkey" |
hm i think i can do that, if you want i need to think on how to implement it cleanly, tho i'm not sure if |
There's also redict. Considering the "redis fork wars" that are going on right now maybe the best move is to stay out of this and wait for the dust to settle and then make this package work for all well-used forks of redis. I'm not sure such a merge needs to happen now, in other words. |
hi |
hi
sorry to bother, I'm rather unaware of how licenses work
I've forked this package and made
channels_valkey
.is it ok if i keep watch of this repo and mirror the changes to that package?
also for the future, if valkey becomes the defacto, I'm more than happy to move channels_valkey repo to django
The text was updated successfully, but these errors were encountered: