You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kvrocks.apache.org by "jihuayu (via GitHub)" <gi...@apache.org> on 2026/06/11 02:21:36 UTC
[I] Tracking Issue: Developer Tasks Suitable for Contributors [kvrocks]
jihuayu opened a new issue, #3516:
URL: https://github.com/apache/kvrocks/issues/3516
This thread collects open issues that are suitable for contributors who want to work on Apache Kvrocks.
We very much welcome anyone to claim the tasks and start contributing to Kvrocks. If you need any help during the contribution process, you can leave a message under the corresponding issue.
## Good first issues
- [ ] #3128
- [ ] #2302
- [ ] #2628
- [ ] #884
- [ ] #755
## Redis compatibility
- [ ] #3411
- [ ] #3073
- [ ] #2610
- [ ] #2500
- [ ] #2414
- [ ] #2133
- [ ] #3319
- [ ] #3436
## CI and reliability
- [ ] #3515
- [ ] #3157
- [ ] #3153
- [ ] #3100
- [ ] #1759
## Cluster and replication
- [ ] #3498
- [ ] #3496
- [ ] #3495
- [ ] #3147
- [ ] #3113
- [ ] #3095
- [ ] #2473
- [ ] #2177
## Performance and optimization
- [ ] #3314
- [ ] #2144
- [ ] #2398
- [ ] #2305
- [ ] #2297
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Tracking Issue: Developer Tasks Suitable for Contributors [kvrocks]
Posted by "ChaseForward (via GitHub)" <gi...@apache.org>.
ChaseForward commented on issue #3516:
URL: https://github.com/apache/kvrocks/issues/3516#issuecomment-5149368932
Hi @jihuayu, thanks for your work on Kvrocks.
I am a beginner who is interested in contributing to open-source projects. I have some experience with C++ and database-related projects (such as implementing storage engines and database components), but this would be my first contribution to a large open-source project.
I noticed your work on this issue and I am wondering if there are any beginner-friendly tasks or issues that would be suitable for someone who is just starting to contribute.
I would like to learn the contribution workflow, understand the codebase, and try to make my first PR. If there are any recommended issues, documentation improvements, tests, bug fixes, or small features that I can help with, I would really appreciate your guidance.
Thank you for your time!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Tracking Issue: Developer Tasks Suitable for Contributors [kvrocks]
Posted by "kita-renji (via GitHub)" <gi...@apache.org>.
kita-renji commented on issue #3516:
URL: https://github.com/apache/kvrocks/issues/3516#issuecomment-5640373328
Hi @jihuayu,
I'd like to contribute to #3518. I've read the design direction and the linked discussions, and I'd like to start with the foundation and work through the steps in order.
1. ACL user model, `ACL SETUSER` rule-string parser and serializer, in-memory cache, with unit tests
2. Persist ACL users in storage and replicate them to replicas
3. Integrate ACL authentication with `AUTH` and `HELLO ... AUTH`
4. Command and category permission checks
5. Key and channel pattern permission checks
6. Initial ACL command set (`ACL SETUSER / GETUSER / DELUSER / LIST / USERS / WHOAMI / CAT`)
7. Denial logging and `ACL DRYRUN`
8. Integration tests and documentation
To keep PRs reviewable, I'd propose splitting the tracking issue into these sub-issues, each mapping to one PR:
I'm aware #3517 (subcommand abstraction, PR #3558) is listed as the first step. Items 1 to 5 don't depend on it, so I'd start there and adopt the subcommand framework for item 6 once it lands.
Two questions before I open the first PR:
- For persistence, is it acceptable to follow the same storage path used for namespaces, so ACL users replicate through the existing mechanism?
- Should `requirepass` remain the credential for the implicit default admin user, or do you want the default user to become a regular ACL user from the start?
I also noticed #2415 is assigned to you. Happy to coordinate if there's existing work I should build on.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Tracking Issue: Developer Tasks Suitable for Contributors [kvrocks]
Posted by "jihuayu (via GitHub)" <gi...@apache.org>.
jihuayu commented on issue #3516:
URL: https://github.com/apache/kvrocks/issues/3516#issuecomment-5151680989
Hi @ChaseForward, thanks for your interest. Feel free to give it a try: [#3552 — commands CF.INFO or CF.COUNT](https://github.com/apache/kvrocks/issues/3552).
This data structure is currently being tracked by [nagisa-kunhah](https://github.com/nagisa-kunhah). You can leave a comment on the tracking issue to let them know that you’re working on it.
A quick reminder: please read our [contributor guide](https://kvrocks.apache.org/community/contributing).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org