Licenses

[ZiNgA BuRgA]

Most people in the MyBB community don't understand licenses, so it really doesn't matter TBH.
(and it's not like you're going to be slaughtered if you don't follow one of them)

Furthermore, it's debatable as to how licenses really apply on an international scope.  I'll be assuming more typical Western country point of view in the following.  The other point is enforceability - if I deliberately violate your license, it's pointless to you if you can't actually force me to adhere to it.

(08-05-2012 04:53 AM)Sama34 Wrote:  Can I use GPLv3 code in LGPL sofware maintaining the LGPL license, if so, how?

Yes you can - you just include it.  The end user will probably need to follow the GPL part though.

(08-05-2012 04:53 AM)Sama34 Wrote:  Apache License v2 seems to be GPLv3 compatible. If I do want to write plugin that uses code under the Apache license, what are the requirements fo it?

Well you have to read the license for that information, but you can look for a summary I guess.
http://www.oss-watch.ac.uk/resources/apa...http://www.oss-watch.ac.uk/resources/apache2.xml#bo

(08-05-2012 04:53 AM)Sama34 Wrote:  Do i have to add a line before each code stating I took it from a Apache licensed software?

No, that would be excessive and absurd.

(08-05-2012 04:53 AM)Sama34 Wrote:  Lets say I write a function, function();, I have it coded and pasted in a .txt file in my desktop. Today I copy it and paste it in a GPLv3 licensed script, can I copy it tomorrow from the .txt file and paste it in a non-free script?

You wrote the code so you have the exclusive right to do pretty much anything with it.

(08-05-2012 04:53 AM)Sama34 Wrote:  Very confusing when I do like releasing plugins and sometimes I do want to modify other free plugins to no write my own code ¬_¬

All these are open source licenses so if you're releasing them as open source, you have nothing to worry about.

(08-05-2012 04:53 AM)Sama34 Wrote:  .. If I modify a Apache 2.0 licensed script can I released it under the same license with no problems?

Yes.

(08-05-2012 04:53 AM)Sama34 Wrote:  I do use the GPLv3 license when I use other people code (control_object(); ), I don't mind. But when it comes to inserting GPLv3 code in a plugin that is not meant to be all free, or when I want to edit a plugin under the Apace 2.0 license, that is GPLv3 compatible, it is a pain to understand all of this...

AFAIK, a "GPL compatible license" means that code under this license can be included in a GPL licensed project (and vice versa).
It's questionable in a scripting environment how components are linked ("derivative") so there might not really be any difference between LGPL and GPL here.

You should be able to put GPL code along with non-free code, if they're aren't considered derivative.  But you probably shouldn't be modifying non-free code anyway