Policy on copying a "snapshot" of open-source dependency into the Shindig
codebase
----------------------------------------------------------------------------------
Key: SHINDIG-623
URL: https://issues.apache.org/jira/browse/SHINDIG-623
Project: Shindig
Issue Type: Question
Components: Features (Javascript)
Reporter: Lev Epshteyn
The opensocial-template feature prototype is currently dependent on the
JSTemplate library released under the Apache license by google.
Currently, the feature.xml file links against the head revision in SVN on
code.google.com, but this is dangerous as the head revision may change
unexpectedly. (In fact, I am currently working with the author of that library
to alter it so that it doesn't leave quite so many entities in the global
namespace.)
So it may be a good idea to grab a code "snapshot" of the library as is (which
currently works with the OST prototype) and check it into SVN - the idea being
that this library gets updated when we are ready to move to a newer version.
However, I'm not sure what the policy is for bringing in third-party dependency
code. Please advise.
Alternatively, I can try working with the library author to come up with some
kind of a release scheme where we can link to a specific and stable release,
but this may be more time consuming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
