Releasing a unique hack mostly using other people's stuff

Originally Posted by tamarian

Are you saying that any work contributed here becomes the property/copyright of Jelsoft?
There are many hacks that do not change any vB code.

No, but you can't apply a copyright that infrige the Jelsoft License if your work is based on vB coded ...

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.

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.

??EDIT

Originally Posted by MarcoH64

Also posting in some areas i think.

Originally Posted by the system

To download hacks and get support you will need...

...
we can have an announcement or something that tell us where we can't post if we're unlicensed... like: you can read but can't post here if you are unlicensed... be3cause actually, i don't get support, i simply discuss... and i can also post in my own releases to Give support... as Give is not Get...

[tamarian]

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.

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.

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.

[Marco van Herwaarden]

Originally Posted by nexialys

we can have an announcement or something that tell us where we can't post if we're unlicensed... like: you can read but can't post here if you are unlicensed... be3cause actually, i don't get support, i simply discuss... and i can also post in my own releases to Give support... as Give is not Get...

I actually am not really sure, thought i remember something like that. Think the service request for example is closed to unlicensed for posting.

[Marco van Herwaarden]

Originally Posted by nexialys

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.

How about if i write some Windows Software and release it under GPL. My software would be depending on some windows function calls one way or the other.

Or if you release commercial software for linux, linux is open source.

Where to draw the line?

[sketch42]

Originally Posted by MarcoH64

How about if i write some Windows Software and release it under GPL. My software would be depending on some windows function calls one way or the other.

Or if you release commercial software for linux, linux is open source.

Where to draw the line?

that windows example isnt the greatest because if i choose to release it as free its my perogative... and if i choose to sell it MS can't make any claims on it just because my software is dependant on theirs

[tamarian]

Originally Posted by sketch42

that windows example isnt the greatest because if i choose to release it as free its my perogative... and if i choose to sell it MS can make any claims on it just because my software is dependant on theirs

Did you mean "MS can't make any claims"? Which does make sense, since MS is competing with many other software makers who make products for Windows.

[sketch42]

Originally Posted by tamarian

Did you mean "MS can't make any claims"? Which does make sense, since MS is competing with many other software makers who make products for Windows.

yes i meant cant

what makes sense that they can or cant make claims??

[Marco van Herwaarden]

Originally Posted by sketch42

that windows example isnt the greatest because if i choose to release it as free its my perogative... and if i choose to sell it MS can't make any claims on it just because my software is dependant on theirs

That was exactly my point.

[sketch42]

Originally Posted by MarcoH64

That was exactly my point.

Ahhhhhhhhhhh .... ok

[mfarmerhi]

nexialys, sorry to hijack the thread, but I wasn't able to PM you or Email you through your profile here.

Could you check out your thread here: https://vborg.vbsupport.ru/showthrea...049#post742049

I'd REALLY appreciate any help you could give.

~ Mark