Module includes 3rd party BSD code in Drupal.org CVS repository.
jmiccolis - July 9, 2009 - 20:49
| Project: | Markdown filter |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
It appears that this module includes the third-party markdown library (in markdown.php). Unless the rules have changed, this is in violation of the Drupal.org CVS usage policy -> http://drupal.org/node/103704
DO NOT include code from a non-Drupal project in the repository. If your module requires non-Drupal code, provide a link to where the other code can be downloaded and instructions on how to install it.
...please let me be wrong. Please let 3rd party BSD/MIT code be allowed, things would just get easier...
#1
I wrote Grupal a while back to bring Google Apps integration to Drupal and it depends on both Zend and xmlseclibs.php libraries (both of which are available under new BSD licenses). There's a zend project in Drupal which facilitates download/installation of Zend (separately from Drupal) and the xmlseclibs.php file is only necessary for secondary functionality (SSO) but this does seem rather a serious limitation in the extensibility of Drupal and I would very much like to see the restriction lifted. This is in the spirit of all GPL-compatible licenses and while I appreciate the "purist" approach it puts us at a competitive disadvantage to those who are more flexible.
I wonder what the implications for GPLv3 libraries are?
Sam
#2
Yeah, well, we are in violation, right. Good catch. So we need patches for the supported branches of the module to extend the description of the installation and remove this file.
#3
Ok - I'm a bit confused by the lineage of markdown and with the split etc. it's possible that it's already been taken care of. Perhaps one of the resident experts could take a look...
What could be even better is some sort of infrastructure for downloading/managing third-party libraries like this... there's no point rolling one for e.g. Zend if we're not even including the library (nor code to download it). Anyway I need to update my module accordingly and will think about how this might be done then.
Sam