Future Crate Maintenance and Redis Inc. Relationship
Hello users. I haven't actively maintained this library in a very long time as you probably noticed. I am still controlling the entry on crates.io for it alongside the redis release team and @badboy individually additionally. As far as I'm concerned that project can do just fine without me, and you should consider that project to not be related to me. However as it stands I got an email from the company currently controlling redis (Redis Inc.) which basically informs me that the present state of this library is not acceptable to them. I also had a 45 minute call with someone from there to walk me through their thinking. They offered some options but it basically comes down to these it seems: * Commercial buy-out and transfer to Redis Inc. * Renaming the package on crates.io where the name of the library constitutes a trademark violation in their mind * Continued continue maintenance under the governance of the Redis project. As someone who is not very active with this crate any more, and historically has built it largely for my own uses I do not feel qualified in making a call here. However it's very clear to me from that call, that Redis has some increasing interest in client libraries. They have some customers now that want Rust support and they need to figure this out somehow. They also transferred the Python and Go client libraries to redis, not sure under which terms and they are trying to do this with the remaining ones of interest. When I created this projec
Posted by mitsuhiko on Nov 25, 2024, 1:57 PM
Tags
Related issues
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
- in the middel of a coding session with 5.6 sol.
- [Hero Run] 535B-A23B on 18T tokens
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (Other)
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I hate that this is how AI is being used..
inexperienced protobuf user here -- why do non-googlers generally use protobuf?
Future Crate Maintenance and Redis Inc. Relationship
Hello users. I haven't actively maintained this library in a very long time as you probably noticed. I am still controlling the entry on crates.io for it alongside the redis release team and @badboy individually additionally. As far as I'm concerned that project can do just fine without me, and you should consider that project to not be related to me. However as it stands I got an email from the company currently controlling redis (Redis Inc.) which basically informs me that the present state of this library is not acceptable to them. I also had a 45 minute call with someone from there to walk me through their thinking. They offered some options but it basically comes down to these it seems: * Commercial buy-out and transfer to Redis Inc. * Renaming the package on crates.io where the name of the library constitutes a trademark violation in their mind * Continued continue maintenance under the governance of the Redis project. As someone who is not very active with this crate any more, and historically has built it largely for my own uses I do not feel qualified in making a call here. However it's very clear to me from that call, that Redis has some increasing interest in client libraries. They have some customers now that want Rust support and they need to figure this out somehow. They also transferred the Python and Go client libraries to redis, not sure under which terms and they are trying to do this with the remaining ones of interest. When I created this projec
Comments (0)
No comments yet. Start the discussion.