× Components and Libraries for Graphics Development, discussions, problems and suggestions.

Question uEControls

  • Miguel Risco
  • Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
4 years 9 months ago #8381 by Miguel Risco
uEControls was created by Miguel Risco
I was read about copyrights problems with codetyphon, but also I was read that codetyphon's developers do not erase the author copyright notices from the original source of the control. But It is not totally true in the case of ueControls. The "about" property was removed with no justification. I'm requesting to the codetyphon team to remove the uecontrols from their controls library.

Please Log in or Create an account to join the conversation.

  • Sternas Stefanos
  • Sternas Stefanos's Avatar
  • Away
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
More
4 years 9 months ago - 4 years 9 months ago #8383 by Sternas Stefanos
Replied by Sternas Stefanos on topic uEControls
Sir
the Mozilla Public License Version 1.1 give us the "Rights" to :
  • to use, reproduce, modify, display, perform, sublicense and distribute the source, and modified versions of the source;
  • patent rights to use and make available the original code (where relevant);
  • to distribute works which contain the code in combination with new code, and to license the new code in any way the distributor wishes. The contributor grants these subtly different rights:
  • to use, reproduce, modify, display, perform, sublicense and distribute the source of their modifications;
  • patent rights to use and make available both the modifications and the entire work (original code plus modifications);
  • to distribute works which contain the code in combination with new code, and to license the new code in any way the distributor wishes. Both these grants are subject to the following conditions:
  • all distributed copies (original or modified) must include the source code or advice on how to obtain the source code;
  • all modifications are described in accompanying documentation;
  • any patent rights necessary to operate the software are clearly described in accompanying documentation;
  • all copies of the code, original or modified, have a statement of copyright and an exclusion of warranties attached;
  • all modified files must be distributed under the MPL. New files containing entirely new code need not be distributed under the MPL. As can be seen from these grants and provisos, the MPL differs most significantly from the GPL in the way that it governs how works containing the MPL-licensed code can be distributed and licensed. Put simply, someone can take an MPL-licensed work and build upon it with new components. The resulting work can be distributed with the MPL covering the use of the original work and any licence covering the rest. Clearly in this way a company could add closed source components to an MPL-licensed work and thus build a proprietary product.

Please, read again the Mozilla Public License Version 1.1

"About" property is part of the source and code functionality, NOT part of MPL 1.1
We modify the code functionality follow ALWAYS the Mozilla Public License.

Our team suggestion is you to put your name in to "Exhibit A" of Mozilla Public License.
We don't have any problem to put any name in the License Exhibit A
Exhibit A - Mozilla Public License.

"The contents of this file are subject to the Mozilla Public License
Version 1.1 (the "License"); you may not use this file except in
compliance with the License. You may obtain a copy of the License at
https://www.mozilla.org/MPL/

Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific language governing rights and limitations
under the License.

The Original Code is ______________________________________.

The Initial Developer of the Original Code is ________________________.
Portions created by ______________________ are Copyright (C) ______
_______________________. All Rights Reserved.

Contributor(s): ______________________________________.

Alternatively, the contents of this file may be used under the terms
of the _____ license (the  "[___] License"), in which case the
provisions of [______] License are applicable instead of those
above. If you wish to allow use of your version of this file only
under the terms of the [____] License and not to allow others to use
your version of this file under the MPL, indicate your decision by
deleting the provisions above and replace them with the notice and
other provisions required by the [___] License. If you do not delete
the provisions above, a recipient may use your version of this file
under either the MPL or the [___] License."

NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.

PilotLogic Architect and Core Programmer
Last edit: 4 years 9 months ago by Sternas Stefanos.

Please Log in or Create an account to join the conversation.

  • Miguel Risco
  • Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
4 years 9 months ago #8387 by Miguel Risco
Replied by Miguel Risco on topic uEControls
"all modifications are described in accompanying documentation;"

You dont describe the modifications, and also you do not justify any improvements, you simply copy the source code and remove the about information to hide the real author from the user point of view. I'm sure that it is not the spirit of the license.

Please Log in or Create an account to join the conversation.