Maintainers wanted!

[gvolpe]

Hi all,

If you or your company uses Redis4cats in production, it would benefit from maintainers helping cut releases, reviewing PRs, etc.

As a one-man project, I don't have the time it needs, and I'm sincerely overwhelmed. Happy to provide some guidance for those who volunteer.

There are also a lot of known (hard) issues to solve that are barely documented, or not at all, so if you're up to the challenge, this is also a good way to learn the internals as well as working with effects.

Cheers,
Gabriel.

[gvolpe]

To all of you asking for a new release

Cutting a new release is very easy, I only need to trim the automatically generated release notes and create a tag. The rest is all automated.

The problem is that before doing so, we need to groom all the existing opened issues and PRs, and make sure everything is good. Also, lately I've only focused on the CE3 version (series/1.x) while the CE2 version (master) was left behind.

All of this requires a lot of time and energy I don't have, thus the call for maintainers.

[ayushworks]

hi @gvolpe : i am more than happy to help in maintaining. My lack of experience in OSS could hurt but otherwise i am in.

[kyri-petrou]

Hi @gvolpe 👋 . Happy to help with maintaining as well in any way that I can. I've only ever used CE3 though, so not too sure how well I can contribute to the CE2 version.

[danielnaumau]

Hi @gvolpe . I'll be glad to help you

[gvolpe]

Thank you, folks! I sent out an invite to all of you.

The priority is now to groom all the open PRs (mainly by scala-steward) and see why they don't pass the CI build, and try to fix it, so I can finally cut a release for the CE3 version at least. Most of them might not compile because of some imports that have changed or so, others might be a little bit tricky.

Once you pick up one, make sure you assign yourself to the issue / PR so that other maintainers know it's taken.

Feel free to join the Gitter channel to discuss (I use it from Matrix), or if you don't like to use that, we can discuss on GH discussions.

[hajlaoui-nader]

hello @gvolpe ! I will be happy to help maintaining this lib

[gvolpe]

Cheers @hajlaoui-nader , you should have received an invitation.

[MamdouhAhmed]

Hey @gvolpe, I'd be happy to volunteer as a maintainer for this project.

[gvolpe]

@MamdouhAhmed great, check your inbox for the invite :)

[andriibutko]

Hey @gvolpe, I want to volunteer as a maintainer for this project.

[gvolpe]

@yourzbuddha you should receive an invite shortly, thanks :)

[yisraelU]

Hi @gvolpe If this is still relevant, I am happy to volunteer some time. I use redis4cats at work currently, however by no means am I a power user

[gvolpe]

@yisraelU sure, the more the merrier! You should have an invite now, thanks :)

[yisraelU]

@gvolpe thank you.
Is there a write-up somewhere on priorities and procedures for managing PR's. I'd probably start with reviewing open PR's and merge, but want to make sure thats what I should be doing

[gvolpe]

@yisraelU unfortunately not. I think a good think would be to add MiMa support if that's something you'd be interested in contributing, as today we don't make any guarantees regarding binary compatibility between versions, as stated in the README.

The Stream API is also quite experimental, but I don't think we emphasize that enough (only here I think). So documentation work is always welcome, also reviewing and merging PRs. You can have a look at previous PRs to understand more or less how we go about it, but it's up to you really.

I've been using AWS for the last 2 years, so don't get to use Redis at all, so better to have maintainers that actually use Redis.