lettuce
lettuce copied to clipboard
redis
Lettuce user support model
Dear community,
Lettuce started as a non-blocking driver supporting some basic Redis operations. Over time, it grew to a driver that is able to operate in a majority of operation modes. With its growth, the userbase and amount of support requests ("I have a timeout", "Can't connect", "How do I …?") increased.
Lettuce is maintained by a single person - me. Adding features, fixing bugs works well in this mode of operation. Answering support requests does not. Now it's time to reconsider the user support model as it doesn't scale with a single person maintaining the project in their free time.
I'm happy to discuss suggestions.
Collaborators are always welcome and at times, there are some folks who contribute multiple times. Finding folks who want to contribute regularly is the hard bit. Giving push permissions is a matter of trust and requires that all contributors share a similar vision/code style to keep a consistent code and feature style.
Great to hear. A good starting point is having a look into the open issues, mostly bug reports, reviewing pull requests to get an idea of the Lettuce anatomy.
It is a lot of pain to support such a huge open-source project. BTW recently I've read the great article of redis creator Salvatore Sanfilippo (aka antirez) about such troubles http://antirez.com/news/134 But let me ask maybe a stupid question Since lettuce is a crucial part of spring ecosystem de facto (e.g. used by spring-data under the hood), why shouldn't spring team and community support it as one of the projects?
While Salvatore's motivation is a bit more on a personal expression note, my motivation is contributing back to the community. Spring usage forms only a small fraction of the user-base. The Spring team typically builds integrations on top of drivers, they aren't building drivers themselves. You could argue the same way that Spring/Micronaut/Helidon build heavily on top of JPA and JDBC, so why don't they maintain those projects.
@sokomishalov @dengliming you folks contributed already a lot to Lettuce. Would you like to become a core contributor at some point in time? Such a step clearly requires a bit more communication on particular issues, but that would be a logical step to me.
@mp911de I would say yes. and happy to see that. Personally, I am a fan of Redis and I have recently been active in contributing to the client for Redis modules . Such as redisearch. It would be a great pleasure for me If I can work with you to make the Lettuce community better. Thanks : )
@mp911de well, I would say yes too. I would glad to spend some free time by helping you and community to make the driver be even better. Thanks!
@mp911de Hello, I want to be a contributor to your project and work hard to commit. Do you have any requirements that you can become a commit after meeting the requirements?
Thanks for your interest. The only requirement is to follow our contribution guidelines. Other than that, looking forward to reviewing your first pull request.