A fundamental rule of Drupal CVS is that only GPL'ed code can be checked into the repository. However, this project has the Alchemy API checked in, which is not GPL.

From the Alchemy API README (which doesn't seem to be included here):

COPYRIGHT AND LICENCE

Copyright (C) 2009-2010 Orchestr8, LLC.

This library is free software; you can redistribute it and/or modify
it under the same terms as PHP itself, either PHP version 5 or,
at your option, any later version of PHP 5 you may have available.

CommentFileSizeAuthor
#1 tagging.remove_alchemy_api.patch35.67 KBrfay

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Needs review
StatusFileSize
new tagging.remove_alchemy_api.patch35.67 KB

Here's a patch to remove the Alchemy API files and change to depend on Alchemy module's loading (which uses the libraries module by default) and also its configuration of the API key, which will make this quite a lot easier to use.

proindustries’s picture

proindustries commented

Just to confirm - Randy's patch works fine. I was about to submit a patch for the same issue, but he beat me to it. :)

eugenmayer’s picture

eugenmayer commented

Well currently it looks like the submodule gets removed within the next release. The author is not fixing any bugs and iam not going to support it within my time.

As an alternative the module can be a new project on drupal.org and maintained by someone else direct - still work with tagging of course.

gagarine’s picture

gagarine commented

In fact sub-module "Alchemy tagging suggestions" from alchemy provide exactly the same functionality with a better interface (you have a admin to setup an API key...). So you can certainly drop the module tagging_alchemy_suggest...