I've already posted a working Drupal 6 version of this module at #250260: Port to D6? - at least it works for me and the port only took a couple of hours. I've also contacted the module's owner about two months ago and asked to become a co-maintainer. Since I've received no reply and the last life sign of ssnider is almost two years old, I'd like to take over maintainership.

Comments

EastWan’s picture

Project: Google Apps Authentication » Drupal.org site moderators
Version: 5.x-1.0 »
Component: Code » Project ownership

http://drupal.org/project/googleauth - No reply from module owner.

I would like to take over ownership. Working Drupal 6 port here: http://drupal.org/node/250260#comment-2368024

avpaderno’s picture

Title: Offer to maintain Google Apps Authentication » Offering to take over Google Apps Authentication

I sent an email to the current maintainer.

Hello ssnider. I am writing you because EastWan (http://drupal.org/user/455318) is offering to take over Google Apps Authentication.
Please reply to http://drupal.org/node/690224. If you don't reply before two weeks, the ownership of the project will be passed to EastWan.

Best regards.
— kiamlaluno
Drupal.org site maintainer
Drupal.org contributions CVS maintainer

Aren't there any other projects that have the same purpose, or implement the same functionality?

avpaderno’s picture

Searching for Google Apps Authentication, I found the following projects:

cyberswat is looking for co-maintainers for the first project; I wonder if there is really the need to pass the ownership of Google Apps Authentication in this case.

cyberswat’s picture

The seemingly abandoned googleauth modules scope is targeted specifically at key based SSO for an enterprise level organization that uses Google Apps. The google_auth module implements something Google calls AuthStub to allow a web based application to have it's users authenticate against Google so that the web application can gain CRUD access to the Google services that user is using. The phrase Google Auth is used by Google in both instances so the name is confusing.

I created my module per http://drupal.org/node/364047 and think that it would make a lot of sense to consolidate Google authentication (in all it's forms) into a single module. I'd be more than happy to work with anyone that would like to help that effort.

jacobson’s picture

I would like to endorse assigning a new maintainer. Integration with the Google authentication service would be a valuable capability for Drupal.

Thanks.

EastWan’s picture

Exactly, there are two Google Auth modules and it was confusing to me, too, at first. With this module users authenticate against the Drupal user database to get access to Google and with cyberswat's they authenticate against Google to get access to your Drupal site. Correct?

The module I offer to maintain would be replaced with the module I created for the 6.x branch and is basically just an adaption of the SSO code Google provides. It took me one afternoon to create it which is why this seems to be a manageable task for me.

As for creating a merged module, I would be willing to fit in the SSO part but could probably not help with the rest so that it would not really take any load off cyberswat's shoulders. Also, since people probably just use one of these techniques, a merged module would provide them with lots of code they don't need.

cyberswat, you seem to know more about Google Authentication than I do. Would you like me to merge the SSO part into your module, keeping in mind that I currently don't have time to maintain more than the SSO part? You can take a look at the module here: http://drupal.org/node/250260#comment-2368024

cyberswat’s picture

@EastWan: Let's take a look at integrating this effort so that others aren't confused about which module they should be using. I'm comfortable with you focusing on the functionality you are interested in. Please open a new issue in in the google_auth modules queue by re-rolling a patch of the gzipped module you attached to the comment you reference. http://drupal.org/node/396082/cvs-instructions/HEAD will help you create the patch and http://drupal.org/coding-standards will help make sure we can get the patch included.

Assuming all goes well with my requests above we can work on getting you a cvs account and cleaning up the abandoned module. If you have any questions you can contact me in the Drupal irc channels and I'll help.

@kiamlaluno not sure what status you want this ticket set to so leaving it to your discretion.

cyberswat’s picture

@EastWan The code you submitted contains Google licensed code covered under the Apache License v2.0 which is not compatible with the GPL v2 license Drupal is covered under (it is compatible with gpl v3). So, if you do re-roll a patch, please provide instructions for users on where to download that code vs including it in the patch.

avpaderno’s picture

Category: support » task
Status: Active » Closed (won't fix)

As there have not been replies from the OP about what reported in comment #8, I am marking this report as won't fix.

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer