Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I am an active member of the cloud computing community and am interesting in contributing to Drupal in ways that make it more useful in cloud environments. Initially that translates to making it work with systems like Google Apps (and to that end I have already developed the Grupal module which targets both the User Provisioning API and Single Sign On API) but I am also thinking about issues that prevent Drupal from being used easily in general.
Grupal (http://code.google.com/p/grupal/) is Drupal® seamlessly integrated with Google Apps.
Currently supports
* Creating users in Google Apps when created in Drupal (suspended or enabled)
* Suspending users in Google Apps when blocked in Drupal
* Synchronising passwords in Google Apps when updated in Drupal
* Suspending or deleting users in Google Apps when deleted in Drupal
* Integrated Single Sign On (SSO) - new since 2.x
Features
* Uses Zend Framework for Google Apps APIs
* Open Source (AGPLv3) licensing
* Commercial licensing and support for both Grupal and Google Apps available from Australian Online Solutions (a Google Solution Provider).
* Performance optimisations only talk to Google when absolutely necessary
* Security feature requires Google Apps admin password for all changes
* Ability to intercept and prevent username updates (which break links)
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | grupal-2.0.2.tar_.gz | 36.99 KB | samj |
Comments
Comment #1
samj commentedPlease find attached Grupal 2.0.2.
Comment #2
samj commentedRetrying with smaller file (>1Mb fails silently!)
Comment #3
samj commentedComment #4
avpadernoA Drupal module license is always GPL v2+; any compatible license is not accepted.
Comment #5
avpadernoAlso, any files available from third-party sites should be removed; the same is true for LICENSE.txt, and LICENSE-Zend.txt.
xmlseclibs.php doesn't report to be licensed under GPL License, and therefore cannot be placed in Drupal.org CVS repository.
Comment #6
samj commentedApologies - that was removed from the code itself for this submission but not the site (it's done now - everything's GPLv2).
Sam
Comment #7
samj commentedRegarding xmlseclibs.php, this is for optional but useful functionality (single sign on) and its license, which is included in the file, is compatible with the GPL.
Note that the Zend framework license is also the New BSD License and while there is a Drupal zend project which facilitates downloading and installing it, it appears to be unmaintained (no release in >1year). Perhaps I could add this to my todo list.
I also note that the markdown project (which advertises being included in Acquia Drupal) include[sd] the New BSD licensed markdown library (see: #515048: Module includes 3rd party BSD code in Drupal.org CVS repository.), in contravention of the CVS repository usage policy. So does marksmarty over here.
So which is it - Zend and markdown are OK but xmlseclibs.php isn't? Essentially I don't mind neutering the module to achieve policy compliance but I'd like to understand what the story is first.
Thanks,
Sam
Comment #8
samj commentedSee also #552478: Restrict "self-closing" tags to only void elements in drupal_pre_render_html_tag which I put together yesterday at DrupalCon Paris with pwolanin.
Sam
Comment #9
avpadernoSee Why drupal.org doesn't host GPL-"compatible" code.
GPL-compatible code is not acceptable for any modules. If there are modules including code not licensed under GPL, it will be took the necessary actions; modules used for CVS application are not accepted if they contain not GPL licensed code.
Comment #10
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .