Using cc lite as an API for additions
| Project: | Creative Commons Lite |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I am working on adding some functionality to cc lite (like importing data from cc API, adding additional licenses, or giving users a way to add additional license choices (like GnuFreedoc, Dual licenses, etc).
I am looking for feedback, because I am thinking that if the intention is to keep cc lite a slim and simple funtion module, that maybe I would instead submit these changes as an additional contribution module, that would require cc lite, but then would expand on cc lite.
I wasn't sure, but it seemed that cc lite was originally created to be a stripped-down version of http://drupal.org/project/creativecommons and if that is still the intention, then it seemed to make sense to me to use cc lite as basic module to build off from, without actually needing to put all of the new code and changes into cc lite itself, but instead create some new modules that add the new functionality.
What do you think? How should I submit major new changes? As patches, or new modules?
#1
Yes, still the module has intention to stripped down version of creativecommons module. This will be a good idea to allow user to add additional licenses by user. I think it should be submitted by patch and add that to new release.
#2
So, if I come up with code that pulls data from creativecommons api, then maybe I should offer that as separate contrib module that works well with cc lite?
Ok, will submit patch as soon as I can for user-added licenses.
#3
For anyone waiting for that module:
You can try out Creative Commons and Copyrights computed field and node type which I just posted for adding your own licences. Then apply one of the many node access modules to secure the granunalrity of each license you create.