I understand that Shindig is released under (what appears to be) a pretty stock Apache license, which is great.
My question is, if we were to use some or all of the Shindig javascript, and override certain parts of it, what's the policy on the resulting code? Does it have to be also released under an Apache license? (Ie, copyleft-style) If the license statement has to be included (which I'm assuming it does?), does the shindig code have to be separated somehow to delineate what the license covers? IANAL, but it seems from the Apache license[1] that copyleft would only attach if the code was not "separable from" the Shindig source. Does minifying/compressing the Shindig javascript count as a "modification" that must be specifically declared? Does serving the javascript count as "distribution", or would all of this only matter if we were to release the code as a separate package? (That is, if we made it available for download for other sites to use; we don't plan on doing this, AFAIK.) I suspect that my employer would not mind if our javascript needed to be open-sourced (since, after all, Javascript is somewhat "open" by definition), but I'm just trying to see if I can avoid a conversation with an IP lawyer if possible. Thanks! -- Isaac Z. Schlueter [1] http://www.apache.org/licenses/LICENSE-2.0 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
