Hello community,
In other post, we asked: if we could use our BSD-2C licence for the development of "extra" for the "MODx community" and Mr. Jason replied us that YES! could be done.
Well, the problem is we do not know how to we behave, in the case of standard functions or files standard procedures.
Example:
If our file "build.policies.php" does the identical operations, made in the file "build.policies.php" of "extra Quip"
but will be changing the names of the "Policies" of "Quip package" by the names of our "Policies". as we have to behave with copyright header?
We know that all the source code file "build.polices.php" of "extra Quip", is written by Shaun McCormick for Quip product for which the copyright is yours no doubt some, and we are not loving vain to attribute source code if this source code is not ours.
I continue with the question, its copyright header is this:
/*
* Quip
*
* Copyright 2010-11 by Shaun McCormick <[email protected]>
*
* This file is part of Quip, a simple commenting component for MODx Revolution.
*
* ...
*/
But if we apply this file to our package, we know it is not "Quip package" and our package is a completely different to "Quip package", is not a derivative of "Quip package", and is not, an extension of "Quip package", simply we would be using the source code file "build.policies.php" as a standard of abstraction for our package.
So the question is this:
what would be the correct copyright header in this case?
would correct this header?:
/*
* This code based on Quip package
* Copyright 2010-11 by Shaun McCormick <[email protected]>
*/
/*
* VES
*
* THIS SOFTWARE IS DESIGNED AS A NATIVE ADD-ON FOR MODx CMS
* THEREFORE MAY CONTAIN SOURCE CODE IMPLEMENTATIONS
* STANDARDIZED BY MODX, LLC. AND PROTECTED BY THE GPLv3 LICENSE.
*
* **
* Copyright (c) 2012 Emmodded Project
* All rights reserved.
*
* This code is derived from software contributed to Emmodded Project
* by Maurizio Spoto <[email protected]>
*
* ... BSD license here
*/
We know that our questions may bore you, we are somewhat noob in this mixed-use and mixed-use source code of open source licenses.
but try to do the right thing in our project and we are finding hundreds of problematic like this on quoted.
at various levels not only in the web application level. (service servers, bootloaders, proprietary drivers, proprietary sicurity algorithms, ufh this a crazy world )
We know exactly what kind of freedom, will be our source code, but do not want our freedom obstacule or collide with other licenses and they are never removed anyone's original copyright.
Regars.
