I understand from the GNU Licensing compatibility matrix (http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility) that what I need to do is permissible. But I want to take a quick dip here to avoid headaches and wasted time/effort in the event that I misunderstand.
There is a widely used PHP class for Google maps that implements the JavaScript API v3. (The primary Drupal Google mapping modules are 'legacy dependent' with code bases written to API v2.) This API v3 library/class I want to use is licensed under LGPLv3.
My wrapper/extension module needs to subclass this LGPLv3 class in order to make its functionality work within Drupal. The actual source files for this library/class will not be included in my module and I will point folks to the Google Code repository where this is freely available. However, it is essentially impossible to subclass and override something else without including bits and pieces of the parent class if only to map to the naming conventions, parameters, etc. necessary to have a functional subclass.
So my bottom line question is: Can my proposed module be included in the DO repository?
My assumption is that this module would, in effect, be interpreted as itself being licensed under the GPLv3 license when 'conveyed' (that is, downloaded and used by any recipients) while all of Drupal and its 'host' repository is and remains GLPv2+.
Thanks for clarifying,
--Sohodojo Jim--