Maintenance rethinkdb/rethinkdb-go

[DanyHenriquez]

I would like to take over updating and maintaining the rethinkdb/rethinkdb-go. At this moment there seems to be no reliable update mechanism and it seems abandoned. I want to change that.

First PR is already there so we can make some progress. After that i will check what more i can do there.

[gabor-boros]

@DanyHenriquez I'm a little bit late on this. Are you still interested?

[DanyHenriquez]

@DanyHenriquez I'm a little bit late on this. Are you still interested?

@gabor-boros
Hello. I have not been checking my issues for a while, but I would be interested in maintaining the repo and doing updates.

[gabor-boros]

@DanyHenriquez Then I'd be happy to collaborate with you. I'll go through the open PRs this week and review them. If you need any help/info/resource/etc, just let me know.

At the moment, CMogilko and I are in the GitHub team that can update the repo directly. I did not do any maintenance lately (as visible), however, I'm happy to pick up the track again. Also, if you are interested on the long run, I'm happy to give you access to the repo as a maintainer after some PRs, so you don't have to hassle with forks.

[CMogilko]

I do not work with rethinkdb anymore, so no time to do maintenance, sorry.

[DanyHenriquez]

@gabor-boros @CMogilko

I will work on some PR's and try to resolve some issues next week.

[majst01]

@DanyHenriquez would also help here, already have some fork which updated the whole codebase a bit

https://github.com/majst01/rethinkdb-go/tree/go-1.22

[DanyHenriquez]

@majst01 Its great to have an updated code base, but would it not be better to merge it all back to this repository?

Then we have one source of truth in stead of forks.

I'm willing to help, but I'm not willing to help with maintaining a fork of the original unless the original project maintainer is MIA.

Great work nonetheless!

[majst01]

@majst01 Its great to have an updated code base, but would it not be better to merge it all back to this repository?

Then we have one source of truth in stead of forks.

I'm willing to help, but I'm not willing to help with maintaining a fork of the original unless the original project maintainer is MIA.

Great work nonetheless!

Sure, my goal is of course to get this merged, but i first want to test our sw with this before opening PRs. And it should be split into several PRs for better reviewability.

But it seems to me that right now, no one is reviewing PRs.