Hi all.
We're rewriting addons.mozilla.org. It's gonna have funk.
We began in CVS, but have recently moved to the spanking new SVN
server. All the "rules" refer to CVS, but I'm assuming they'll be
identical for SVN aye?
Aaaaanyway, questions.
1) Can we have stuff in SVN that's not under the tri-license?
Specifically, I'm looking at:
* cakephp (php development framework) which is under the MIT
license -
http://svn.mozilla.org/addons/trunk/site/cake/docs/LICENSE.txt
* simpletest (testing suite) which is under the LGPL -
http://svn.mozilla.org/addons/trunk/site/vendors/simpletest/LICENSE
* scriptalicious (javascript libraries) which is under the MIT
license -
http://svn.mozilla.org/addons/trunk/site/app/webroot/js/scriptaculous/scriptaculous.js
* The Cake test suite, which uses The Open Group Test Suite License
- http://svn.mozilla.org/addons/trunk/site/app/tests/lib/LICENSE.txt
* Files that have no license at all (doesn't that make them still
proprietary for the initial developer?) which we have written but not
yet licensed
2) AMOv2 - http://lxr.mozilla.org/mozilla/source/webtools/addons/ -
doesn't actually appear to be licensed at all to me. What's the penalty
for that? Additionally, a small number of files have been moved over,
eg. the plugin finder service -
http://svn.mozilla.org/addons/trunk/services/pfs/pfs.php
3) The job of throwing the license at all the files that we've written
has fallen to me, so another question. Does the contributors list to a
file include people who only made minor edits? eg. changed a single
line, fixed a grammatical error, etc.
Thanks,
~Cameron
_______________________________________________
legal mailing list
[email protected]
https://lists.mozilla.org/listinfo/legal
