Can ActiveLdap organization take over Ruby/LDAP?

[kou]

@bearded It seems that you can't maintain Ruby/LDAP. ActiveLdap organization https://github.com/activeldap depends on Ruby/LDAP. Can ActiveLdap organization take over Ruby/LDAP? (Transfer https://github.com/bearded/ruby-ldap to
https://github.com/activeldap/ruby-ldap )

[ShaneCurcuru]

We also need to use ruby-ldap on ruby 3.2.x+, so I've forked this project to:

https://github.com/Punderthings/ruby-ldap3

And pulled PRs #44, #45, #46 up, changed version number to 0.10.1 and put up on rubygems.

Sadly (and mysteriously) I'm still getting a ton of warnings/errors when trying to bundle install into my actual environment. If anyone's interested in maintaining a ruby 3.x version of this code, let me know; I don't have much dev time, but I will accept PRs to get things to work on new Ruby versions.

[minamino]

@kou @ShaneCurcuru
Few years ago, I posted the PRs #44 and #46 on this repository. Like @ShaneCurcuru, I also need ruby-ldap to work on Ruby 3.x in production.
@ShaneCurcuru's ruby-ldap3 incorporated the existing PRs (#44, #45, #46) and made it available on RubyGems, which is a great step forward. However, as @ShaneCurcuru noted, there are still many warnings and errors remaining. The root cause is the use of the deprecated Data API (Data_Make_Struct, Data_Get_Struct, Data_Wrap_Struct), which Ruby 3.4 warns about and Ruby 4.0 will remove entirely.
I have made a migration to the TypedData API, tested on Ruby 3.4.1 with OpenLDAP (only LDAPS bind/search/unbind verified) on Rocky Linux 8.5. All changes are version-guarded with #if RB_LDAP_RVC >= 30000 to maintain backward compatibility with Ruby 2.x. The patch is available at:
https://github.com/minamino/ruby-ldap
Given that @bearded has not responded for over two years, it would be wonderful if @kou could take over maintenance. I would be happy to contribute this patch to help move things forward.
@bearded If you are reading this issue, we would greatly appreciate your response. Any guidance on the future of this repository would be very helpful to the community.

[bearded]

oh my, sorry guys, somehow I have missed all those messages (did not watch email account properly for a while)

I indeed not able to maintain this repo (I had to, when I was using the lib, but no longer working with LDAP)

I'm happy to move this repo into activeldap org, @kou, I have tried and do not have permissions to do so

You don’t have the permission to create public repositories on activeldap

[kou]

Thanks!
Could you add me to owners of this repository? I'll transfer this repository to https://github.com/activeldap/ .
And could you also add me to owners of https://rubygems.org/gems/ruby-ldap by gem owner -a kou ruby-ldap?

[bearded]

@kou, added you, thanks a lot for taking it under your wings ❤️

[kou]

@bearded Thanks! I accepted the both invitations! But it seems that a repository collaborator can't transfer a repository...

I've invited you to https://github.com/activeldap/ . Could you try transferring again after you accept the invitation?

[bearded]

I have transferred it @kou, thanks

[kou]

Thanks! Confirmed!

@bearded Thanks for maintaining Ruby/LDAP so far!

Let's reboot Ruby/LDAP in https://github.com/activeldap/ruby-ldap/ .

As the first step, let's prepare GitHub Actions: #49

@minamino Are you interested in maintaining Ruby/LDAP?

[minamino]

@minamino Are you interested in maintaining Ruby/LDAP?

Thank you for the offer.
We use my milter and other tools that depend on ruby-ldap internally, so I should be able to contribute as long as I remain employed at my company.

[kou]

Fair enough. I've invited you to the "ruby-ldap-owners" team.