Offering to maintain LDAP Integration [#2278091]

I'd like to offer to maintain or co-maintain this module. There hasn't been a release cut for two years, and several items have patches ready for review.

I have already started triaging issues, I have 10 patches currently in the queue, and more on the way as I need this module to support multiple clients.

Comments

Comment #1

johnbarclay CreditAttribution: johnbarclay commented 2 June 2014 at 00:41

Thanks. My primary work is in the Drupal 7 version (https://drupal.org/project/ldap) so appreciate you taking this on. I've added you as a maintainer. If the other maintainers of LDAP Integration could chime in on what their current role is here, I can adjust the permissions accordingly.

Comment #2

cgmonroe CreditAttribution: cgmonroe commented 2 June 2014 at 18:53

greeting from drupalcon austin!

thanks for taking this on. I've been letting this run on autopilot since like most folks I've moved on to D7.

I've done a quick first pass thru your submits and most of them seem straight forward. Just remember that there are a lot of variations in how the 7K sites use this. Please try to evaluate how a change might effect sites using different security and other options than your sites.

Plus I have been trying to avoid making this a swiss army does it all module by not adding in specialty code. Instead, I have tried to expand the api to let these be supported by custom modules.

Just consider this the standard with great power comes great responsibility speach..lol

Comment #3

John Franklin CreditAttribution: John Franklin commented 2 June 2014 at 20:43

My plan is to commit a handful of bug fixes to the 6.x-1.x branch and then put the bulk of the new features on a 6.x-2.x branch. It'll let sites that don't need the 2.x features stay with what they know, but also give features to sites that may need taxonomy syncing or file fields.

I've been using this module since 2009 or so for a few sites, most of which could use the bug fixes, but have no need for the new features. My own decision to migrate to 2.x will based on site needs.