Quote:
Originally Posted by nexialys
No, but you can't apply a copyright that infrige the Jelsoft License if your work is based on vB coded ...
|
Well, the whole discussion from the beginning was about other people's work. I don't think anyone was suggesting to infring on Jelsoft's copyrights. vb.org is owned by Jelsoft, so trust them to watch out for themselves if they find any hack here on vb.org was infringing on their copyrights in any way. They will let you know about it.
Quote:
if you release a software that plug into vB, that is different. the software you work with is licensed your way, and may not be the same kind of license or copyright than vB... but it can't give you any right over vBulletin...
GPL and usually all other licenses work the same... you can apply restrictions, copyrights or trademarks, but not licensing that is opposite to the product you work on.
|
Not sure what issue is being addressed here. You don't need any copyrights over anyone else's copyright to establish your own copyrights. It would be rediculious for anyone to think that because they have some copyrighted material that works with vB, that they can claim copyright over the whole thing? That's just silly, and I don't think anyone remotely suggested it.
Quote:
if you code a piece of vBulletin and this piece is integrated in the software, you can't think of a way to protect your code but not the rest... that's why there are some relations between the license and the tool you work with.
|
Not sure what you mean. You can always protect your code and/or portions of your code if you so desire. There are many hacks from the past that are now part of stock vBulletin. What Jelsoft does is contact the author to get their permission. You'll find those in the credits page.