Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 6 of 6
  1. #1
    Regular Coder Apothem's Avatar
    Join Date
    Mar 2008
    Posts
    380
    Thanks
    36
    Thanked 25 Times in 25 Posts

    MIT License conditions?

    I'm not too savvy when it comes to licenses and such. So suppose I license my product to GPLv3, and that my software is dependent on another program that is MIT licensed. Does that mean that my program itself is really MIT licensed, and not GPLv3? Or does it mean that the program I am using is still MIT licensed, but my program itself is GPLv3 licensed?

  • #2
    Supreme Overlord Spookster's Avatar
    Join Date
    May 2002
    Location
    Marion, IA USA
    Posts
    6,278
    Thanks
    4
    Thanked 83 Times in 82 Posts
    It really depends upon how you are using the GPL licensed software and MIT software together. The MIT licensed software cannot infringe upon the GPL license and vice versa.

    http://en.wikipedia.org/wiki/GNU_Gen...n-GPL_programs
    Spookster
    CodingForums Supreme Overlord
    All Hail Spookster

  • Users who have thanked Spookster for this post:

    Apothem (12-24-2011)

  • #3
    Regular Coder Apothem's Avatar
    Join Date
    Mar 2008
    Posts
    380
    Thanks
    36
    Thanked 25 Times in 25 Posts
    The other software is a library for my own software; my software includes/imports its library to make use of its functionality.

    From the link, I've only understood "it can only be decided in court"...

  • #4
    Super Moderator Inigoesdr's Avatar
    Join Date
    Mar 2007
    Location
    Florida, USA
    Posts
    3,647
    Thanks
    2
    Thanked 406 Times in 398 Posts
    Quote Originally Posted by Apothem View Post
    Or does it mean that the program I am using is still MIT licensed, but my program itself is GPLv3 licensed?
    The library, or whatever you are using, maintains the MIT license, and you have to keep a copy of the MIT license with it when you distribute it. It doesn't affect how you license the overall application. The MIT license itself is pretty short and simple. The GPL on the other hand is quite verbose, but there is a lot more to it.

  • Users who have thanked Inigoesdr for this post:

    Apothem (12-24-2011)

  • #5
    Regular Coder Apothem's Avatar
    Join Date
    Mar 2008
    Posts
    380
    Thanks
    36
    Thanked 25 Times in 25 Posts
    How would I keep it? Do I keep the license file in the same directory as the library? I'm not sure how I would reference it.

  • #6
    Super Moderator Inigoesdr's Avatar
    Join Date
    Mar 2007
    Location
    Florida, USA
    Posts
    3,647
    Thanks
    2
    Thanked 406 Times in 398 Posts
    Quote Originally Posted by Apothem View Post
    How would I keep it? Do I keep the license file in the same directory as the library? I'm not sure how I would reference it.
    I believe that is up to you. Most people will either keep it in the same directory as the library, in the program's root directory, or in your readme/docs in my experience. You don't need to "reference" it per se, unless you mean in your documentation.

  • Users who have thanked Inigoesdr for this post:

    Apothem (12-24-2011)


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •