--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Hello Josiah,It's great that you are still working at improving Redis. You know that I don't think certain features like rollbacks are a good fit, but I want to merge the SSL patch that AWS contributed a few days ago, and I may also merge the changes you did to soeedup loading if they look in line with the project other concerns.I've nothing against people forking but another possibility could be for you to leverage modules to implement the rollback that you are interested in, and for SSL as I said there is going to be an official implementation. The speedups so far are a bit vague since there is any information but we can work on that.CheersSalvatore
Il gio 26 apr 2018, 07:58 Josiah Carlson <josiah....@gmail.com> ha scritto:
Hey folks,Probably the only/last time I'll post this here, but I'm forking Redis for a collection of reasons. You can see the announcement, read the features, and see the benchmarks:Regards,Dr. Josiah CarlsonAuthor of Redis in Action, open source, and more
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.
Ok Josiah, I understand your POV, and open source allows forking as a
right, so have fun coding.
I've just two requests to avoid confusion within the community:
1. Please pick a name for your fork instead of using Redis. I really
want the Redis name to be associated with exactly the source code that
I control directly, and that people are used to find stable and
functional. In theory you can do even a much better work than I did,
but I've no control on your work, so please just fork with a different
name. So far all the forks changed name fortunately.
2. Please make sure that the name is also replaced in the user-facing
stuff, like in INFO, output "foobar_server" instead of "redis_server",
so that it's clear is not Redis, especially in crash reports,
otherwise it is very likely that we'll get confusion about what such
an object is, and get the bug reports that inevitably will arise.
As a third point, and this is not a request but a kind hope to have a
community of good citizens: try to release the changes under the BSD
license.
Because otherwise we create a monoculture where people get from Redis
and return nothing back.
This is happening already enough with the
cloud. For instance while I was *not* doing all the things you wanted,
I did modules and streams and PSYNC2 and so forth, that you probably
as one of the best person to assemble data structures to solve
problems in our community, will find useful. However if your fork will
be able to incorporate the official change, but not the contrary, it
is unfortunate: legal, but unfortunate. For instance another fork
introduced the concept of GEO indexing in Redis, and thanks to this we
now have GEORADIUS and so forth (plus a lot of work did after, but
still this is how it started). Then the original fork probably was not
used much, but still it hybridated with Redis.
>>> email to redis-db+unsubscribe@googlegroups.com.
>>> To post to this group, send email to redi...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/redis-db.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Redis DB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to redis-db+unsubscribe@googlegroups.com.
>> To post to this group, send email to redi...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/redis-db.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to redis-db+unsubscribe@googlegroups.com.
> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.
--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com
"If a system is to have conceptual integrity, someone must control the
concepts."
— Fred Brooks, "The Mythical Man-Month", 1975.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.
Replies inline.
>>> email to redis-db+u...@googlegroups.com.
>>> To post to this group, send email to redi...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/redis-db.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Redis DB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to redis-db+u...@googlegroups.com.
>> To post to this group, send email to redi...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/redis-db.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to redis-db+u...@googlegroups.com.
> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at https://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.
--
Salvatore 'antirez' Sanfilippo
open source developer - Redis Labs https://redislabs.com
"If a system is to have conceptual integrity, someone must control the
concepts."
— Fred Brooks, "The Mythical Man-Month", 1975.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
As a third point, and this is not a request but a kind hope to have a
community of good citizens: try to release the changes under the BSD
license.For code that gets released and is derived from BSD source code, of course. But not everything that I'm working on or with is BSD licensed, and I'm not going to limit my choice of solutions to only BSD-licensed solutions.