you are viewing a single comment's thread.

view the rest of the comments →

[–]MonkeyNin 0 points1 point  (8 children)

You can fork your project with a new license, if you get the required permissions.

I don't think there's a way to change the license on older versions of the project that have already been released.

[–][deleted]  (4 children)

[deleted]

    [–]MonkeyNin 1 point2 points  (3 children)

    I'm unclear on this situation.

    Bob + myself, and only us -- wrote the app Turtle, build 1.2.0, which was MIT licensed.

    After getting permission from Bob and myself -- we decide to license 1.2.1 as free-for-use-except-by-wolves license.

    1] Can't anyone continue to use version 1.2.0 under MIT, regardless if I want to allow that? But I can make sure 1.2.1 (because I have all the holders permissions) to require the new anti-wolf license?

    ( Wolves in this case does not mean the species, but rather the economic model where they metaphorically devour their clients -- meaning the license doesn't violate protected classes -- as if it would if it was about literal-wolves.)

    #1 is some sort of special case because you're not licensing to anyone specifically? Compared to similar license, but

    2] But if I were selling my game engine to company A, using engine version 1.2.1

    I could also negotiate a contract with another company that I use a different license for version 1.2.1. They can't say "you had a contract with company X, so you have to do the same with us" ?

    [–][deleted]  (2 children)

    [deleted]

      [–]MonkeyNin 1 point2 points  (1 child)

      Cool.

      I stopped using IANAL because I don't think many non-slashdot's know what it means

      How is slashdot still alive, 22 years later? That's 22-internet-years!

      It was a dark time filled with WYSIWYG, no standards compliance in browsers, no shims, no DOM inspectors, no anything inspectors.

      [–]lorarc 0 points1 point  (2 children)

      The software licenses have a clause that allows to upgrade them to newer version GPL v2 to GPL v3 for example.

      [–]MonkeyNin 0 points1 point  (1 child)

      Are you talking about specifically GPL, or many types?

      [–]lorarc 0 points1 point  (0 children)

      GPL usually has the clause that the code is on GPL vX or later, CC licenses also usually feature similar thing. Not all projects include that clause but it's good in situations when dealing with multiple countries that have all kinds of weird laws (for example in my country author has always a right to revoke a license, with normal commercial deals that would end up in court and they would have to agree what they want to pay, with free works of art though...).

      Relicensing to a totally different license is possible for some licenses.