The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#71
|
||||
|
||||
Quote:
Most authors, if they are too busy to do it, will allow others to update their hacks, as long as proper credit is given. |
#72
|
|||
|
|||
I will do so, Erwin. Thanks for your reply.
|
#73
|
||||
|
||||
Hmm ... what about Hacks that come with a GPL-Notice?
There shouldn't be any problem modifying/porting them, right? |
#74
|
||||
|
||||
Quote:
|
#75
|
||||
|
||||
Quote:
But what's the answer to my question Is it allowed to allowed/ethical to release ported Hacks that originally came with a GPL-notice (which allows modifications)? |
#76
|
||||
|
||||
Faranth semi copied mine, but gave him permission afterwards . Now I just want a link back to the vB2 version in his post ^_^
|
#77
|
||||
|
||||
Quote:
|
#78
|
||||
|
||||
Quote:
An idea may have been presented in the past but does this mean it is rightfully theirs? Do we have to ask for permission to "use" an idea? NO! |
#79
|
||||
|
||||
There's an easy solution to this, you just need to understand how copyrights work. In a basic rundown, you can create modifications to an author's hack, however, you cannot release the actual modified hack.. but you can release just the modifications. This is what's called "a patch" in the software world.
Basically, create a patch (or directions) to modify the original source which you must distribute independantly of the original source and you are completely in your legal right in the eye of the law. Now, whether or not vB.org chooses to abide soley by the legal stance or instead by a local private stance is another thing. However, from what it seems, vB.org is strictly adhereing to a legal perspective so you should be fine releasing a patch. I hope this helps! |
#80
|
||||
|
||||
Quote:
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|