From: Dan Dennedy <ddennedy@us...> - 2007-04-10 06:51:45
Update of /cvsroot/mlt/mlt/docs
In directory sc8-pr-cvs16:/tmp/cvs-serv16113/docs
Cleanup copyrights and attributions, and move Jean-Baptiste's services to a new kdenlive module.
RCS file: /cvsroot/mlt/mlt/docs/policies.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- policies.txt 30 Mar 2007 06:55:51 -0000 1.2
+++ policies.txt 10 Apr 2007 06:51:39 -0000 1.3
@@ -13,6 +13,11 @@
inigo, albino, and humperdink applications are covered under GPL. Modules
should strive to be LGPL to make them available through the framework as LGPL.
+There are not a lot of rules, but we prefer brackets on their own line,
+indents using tabs, liberal usage of spaces in statements and expressions, and
+no hard line length. The code in src/framework serves as a good example.
@@ -20,3 +25,17 @@
Until we convert to Subversion, which can provide a nice, comprehensive log
please update ChangeLog with every commit.
+Setting Copyright on Appropriated Code:
+You do not want to be accused of copying someone's code and changing copyright
+or license without permission. The license is straightforward: you must retain
+the original author's license unless you receive explicit permission. There are
+a few ways to approach the copyright declaration depending upon the
+intermingling and changes. If you heavily comingle original and new code or
+lightly modifiy the original code, you can retain the original's copyright
+including the years, and then add your copyright for the current year. If you
+can separate the MLT integration from the core subroutines, then you can put
+the core subroutines into a separate file with the original copyright and just
+copyright the MLT integration code as your own. However, if you have heavily
+modified the original code beyond nearly all recognition, you can copyright it
+as your own and attribute the original author as inspiration.
Get latest updates about Open Source Projects, Conferences and News.