Zikula Community

• uheweb
  
  

  • Rank: Helper
  • Registered: Sep 16, 2004
  • Last visit: Oct 21, 2009
  • Posts: 731

  Posted: Jul 20, 2008 - 03:56 PM

  I've been playing with module studio - Thanks Guite! - and even have a nice little module I've created using the base it generates.
  
  I've probably quadrupled the size of the code, so 75% is my own logic now.
  
  ModuleStudio places:
  
  

  Quote

  * Zikula Application Framework
  *
  * @copyright (c) 2008, Zikula Development Team
  * @link http://www.zikula.org
  * @license GNU/GPL - http://www.gnu.org/copyleft/gpl.html
  * @package Zikula_Generated_Modules
  * @subpackage modulename
  * @author AUTHOR (if set in module studio)
  * @url authorURL (if set in module studio)

  
  
  I definitely want to give credit, and its obviously still GPL, but what's the best way to show that I am the author, yet modulestudio provided the base to start from?
  
  I know that derivative works generate a new copyright in their modified form, so I would be the copyright holder of this GPL code (and as its a derivate work, it could never be non-GPL'ed by just myself) but want to make sure I give credit for Guite who put so much work into the initial code generation.
  
  Suggestions? Guite? What do you prefer?

  • 
  •  
• slam
  
  

  • Rank: Team Member
  • Registered: May 03, 2004
  • Last visit: May 31, 2010
  • Posts: 511

  Posted: Jul 20, 2008 - 05:36 PM

  There are two different common practices which later on can withstand legal battles:
  
  1) All authors leave the copyright of their work on a module to the "Zikula Development Team" or the Zikula Foundation, by adding their names to the "authors" line. If the idea behind the GNU/GPL (protecting the live long openness of the project and it's code) is what you want accomplish, this is probably the best solution. It is also the better solution for growing projects with a possible need for dual licensing later on (in order to sell commercial versions, etc.).
  
  2) All authors keep their partial personal copyright by adding their names to the "copyright" line. Specially smaller projects use this method, it leaves more direct legal control to the authors, while providing less protection against big budget enemies. This is common with small projects without any commercial plans for the future.
  
  Greetings,
  Chris
  
  (While I do have legal professional background, this forum is not the place for receiving professional advice. Instead, the above just presents my personal opinion to interested people. For professional legal advice please consult a lawyer of your choice.)
  
  --
  an operating system must operate
  development is life
  my repo

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.