| Author |
Message |
link
Regular
Joined: Dec 24, 2004
Posts: 56
|
 Posted:
Tue Sep 06, 2005 11:57 am |
|
Does Anyone know the Rules on modification and re-release of altered php-nuke products?
If i rework php-nuke and re-release it with a good deal of changes. What are the legalities?
Is it still php-nuke or can i call it something else as long as php-nuke is in there something.
Example... phpnuke platinum.
its still phpnuke... lots of add on.
another example.
nuke royal... still php-nuke
But phpnuke incorporates phpbb and its not phpbb or phpbb2 its phpnuke
?
Thanks Ill Take My Answer Of The Air....
Mike |
| |
|
 
|
|
hitwalker
Sells PC To Pay For Divorce
Joined:
Posts: 5661
|
| Posted:
Tue Sep 06, 2005 12:08 pm |
|
it doesnt matter..
as long as you leave all credits alone..
you can call it FBhacknuke...  |
| |
|
|
|
|
link
|
| Posted:
Tue Sep 06, 2005 1:11 pm |
|
But i can add my own credits as well correct? |
| |
|
|
|
|
hitwalker
|
| Posted:
Tue Sep 06, 2005 1:17 pm |
|
sure,like compilation by or whatever...
or if it contains stuff you made /written /coded yourself... |
| |
|
|
|
|
Raven
Site Admin/Owner
Joined: Aug 27, 2002
Posts: 17088
|
| Posted:
Tue Sep 06, 2005 2:26 pm |
|
The rules of the GNU/GPL are what apply, not anything specific to phpnuke. |
| |
|
|
|
|
link
|
| Posted:
Tue Sep 06, 2005 3:48 pm |
|
OK ok.
I thought there where specific rules. Or maybe policies that have been followed in the past... other than standard.
Thanks Both of You Guys. |
| |
|
|
|
|
64bitguy
The Mouse Is Extension Of Arm
Joined: Mar 06, 2004
Posts: 1164
|
| Posted:
Tue Sep 06, 2005 4:24 pm |
|
Raven is right in that GNU/GPL rules apply.
The biggest issues that you need to be aware of are:
1) Credits. Evey file has existing opening credits. These cannot be altered. Though they can be AMMENDED. In other words, you can add credits after the existing comments, but you can't alter those that are there.
2) Copyright Notices. You can ammend Copyright notices if you have recoded a solution; however again, you cannot remove any of the existing credits. You must give the authors or developers or people that have existing credits their due. You can add your information to those notices if you modify the code.
In closing, I would mention that if you do modify code produced by others with FIXES, you should send the authors/porters those revisions. It makes little sense to have "forks" of existing Nuke modules or blocks.
Compliations are a different story as (for example) with Nuke Platinum, it would do little good to a module author for TechGFX to send back a Nuke Fork Specific modification. If there are bug fixes in the released module, that is one thing, but then again, at that point you are not the new author of the solution, but merely applying bug fixes. Again, if you send those back, you are also validating that your bug fixes are in fact fixes that can become standardized into the module/block, in which case the authors usually give you credit for fixing those bugs. If you puruse nuke code, you will find tons of commented examples of, "Bug Fix by xyz person to fix xyz problem".
In the case of a new Nuke distribution, again, you wouldn't be changing any core code credits, nor would you alter any copyrights, but rather you would merely ammend the credits inside files to include an additional comments section that identifies that the block, module or function was included with your distribution.
For example, inside the modules/Downloads/index.php you would see:
Code:/************************************************************************/
/* PHP-NUKE: Web Portal System */
/* =========================== */
/* */
/* Copyright (c) 2005 by Francisco Burzi */
/* http://phpnuke.org */
/* */
/* Based on Journey Links Hack */
/* Copyright (c) 2000 by James Knickelbein */
/* Journey Milwaukee (http://www.journeymilwaukee.com) */
/* */
/* This program is free software. You can redistribute it and/or modify */
/* it under the terms of the GNU General Public License as published by */
/* the Free Software Foundation; either version 2 of the License. */
/************************************************************************/
|
You can ammend that with your custom nuke distribution to read:
Code:/************************************************************************/
/* PHP-NUKE: Web Portal System */
/* =========================== */
/* */
/* Copyright (c) 2005 by Francisco Burzi */
/* http://phpnuke.org */
/* */
/* Based on Journey Links Hack */
/* Copyright (c) 2000 by James Knickelbein */
/* Journey Milwaukee (http://www.journeymilwaukee.com) */
/* */
/* This program is free software. You can redistribute it and/or modify */
/* it under the terms of the GNU General Public License as published by */
/* the Free Software Foundation; either version 2 of the License. */
/************************************************************************/
/************************************************************************/
/* Distributed as Part of Joe Blow's "Nuke Special" Version 1.0 */
/* http://joeblow.com */
/* Expect only the best from Joe Blow! */
/************************************************************************/
|
But you would not touch the Copyright.php or any Copyright notices at all of any of these solutions.
Hope this helps.
Steph |
_________________
Steph Benoit
100% Section 508 and W3C HTML5 and CSS Compliant (Truly) Code, because I love compliance. |
|
|
|
|
link
|
| Posted:
Tue Sep 06, 2005 5:13 pm |
|
hhaha... cool
thanks steph |
| |
|
|
|
|
|
|
![[Valid RSS]](https://www.ravenphpscripts.com/images/valid-rss.png "Validate my RSS feed"){kind=small}
