Rubygems version about ruby-net-ldap HOT 21 CLOSED

+1

from ruby-net-ldap.

+1 Yes, please! Since the encoding bug is fixed in 0.5.0 but not in the rubygems version (0.3.1).

from ruby-net-ldap.

+1

from ruby-net-ldap.

+1 Please. This is creating unnecessary problems for folks.

from ruby-net-ldap.

+1

from ruby-net-ldap.

+1 how hard is it to push up a new version of the gem?

from ruby-net-ldap.

+1

from ruby-net-ldap.

@yairgo I've held off comment for a while, but in a gem like ruby-net-ldap, it's fairly hard. Most of the people who have developed against the library in the past either have limited need for LDAP at this point, or no longer have need for LDAP at all (or, in my case, have never needed LDAP, but started the gem to fill a need that was apparent at the time).

Unit tests are of limited value for ruby-net-ldap because we don't (currently) have a good mock LDAP server to be able to impersonate ActiveDirectory, OpenLDAP, etc., nor do any of the developers who have been involved in this so far necessarily have a wide enough test environment to make sure that what isn't released is safe and stable.

I certainly can't do it, because I don't use LDAP at all.

from ruby-net-ldap.

What makes you assume folks who've used this gem had either limited needs or no longer need LDAP?

LDAP is critical in the enterprise and my team uses a lot of Ruby in that environment. This gem does a pretty good job, even against Active Directory, and we'd like to keep using it.

I sympathize with the difficulty in testing the gem but that isn't a new problem. How was it tested before?

from ruby-net-ldap.

Additionally, we can mock LDAP in Ruby for testing: https://github.com/NUBIC/ladle

from ruby-net-ldap.

I misstated because I was trying to write this while packing up from work—the people who have developed the library, not the people who have developed against the library. I won't do it on my own since this isn't something I use, actively develop, or have a comfort level in the tests, I'm also not going to be fixing any bugs that may have snuck in since the last release, and barely have enough time to work on the gems that I do have active responsibility for given my full-time job. I have also waited a long time to participate in this because I passed on management of ruby-ldap to @RoryO some time ago, and do not wish to second guess the current maintainer of ruby-ldap.

I'm not active in managing ruby-ldap anymore, and as I have no need for LDAP I would not feel comfortable releasing the library with the tests as they exist and without any mocking tests. If someone wants to join the ruby-ldap team and take on feature and release management, I will be happy to review test results with them and look at making it possible for them to do so. I will not do it on my own, though, as I don't use ruby-ldap and have no need to do so, so I can't even say that the tests that exist are good.

My preference is for someone to reach out directly to the current ruby-ldap team, either here or on the mailing list (and I see that some discussion happened in the summer) so that the question of maintenance can be handled without me being involved, despite my administrative privileges as the person who originated the project (but have developed maybe ~20 lines of code in the software).

from ruby-net-ldap.

@halostatue @RoryO how do we get another person added to the organization? or how do we decide who that will be?

from ruby-net-ldap.

+1

I've offered to help maintain the project in a PM to @RoryO a couple of months ago but did not get any response 'til today.

from ruby-net-ldap.

@schaary, @yairgo, @cthielen: Were any of you interested in maintaining ruby-net-ldap moving forward? I'm looking for a longer-term commitment.

from ruby-net-ldap.

me, me, me!

from ruby-net-ldap.

@schaary and anyone else who is interested, please send a note to the RubyLDAP group on Google Groups and we'll have a governance discussion there. I'm at work right now, so probably can't discuss until tonight, but let's move this forward. Any ideas you have on how you want to see RubyLDAP run moving forward, please share.

from ruby-net-ldap.

I'm interested in helping maintain but I don't want to be the main person
who maintains it. I'll post a note to the group as well.

On Tue, Feb 25, 2014 at 11:44 AM, Austin Ziegler
[email protected]:

@schaary https://github.com/schaary and anyone else who is interested,
please send a note to the RubyLDAP grouphttps://groups.google.com/forum/?fromgroups#!forum/ruby-ldapon Google Groups and we'll have a governance discussion there. I'm at work
right now, so probably can't discuss until tonight, but let's move this
forward. Any ideas you have on how you want to see RubyLDAP run moving
forward, please share.

Reply to this email directly or view it on GitHubhttps://github.com//issues/70#issuecomment-36036033
.

from ruby-net-ldap.

released V0.5.1 today

from ruby-net-ldap.

❤️

from ruby-net-ldap.

Thank you!

from ruby-net-ldap.

Thank you for your work!

from ruby-net-ldap.