Re: Change license of mkvwriter?

Jerome Martinez <[email protected]> Sun, 22 Jan 2017 22:40:34 +0100
Newsgroups gmane.comp.multimedia.matroska.devel
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============1212130876305213953==
Content-Type: multipart/alternative;
 boundary="------------9F5209454557FEA1C44EC8D9"

This is a multi-part message in MIME format.
--------------9F5209454557FEA1C44EC8D9
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Le 16/01/2017 à 10:48, Matt Gruenke a écrit :
> I also wanted to ask whether we could change the license of mkvwriter 
> (or my fork thereof) from GPL to one of the following:
>
>   * Boost Software License (http://www.boost.org/users/license.html)
>   * MIT
>   * Apache
>   * LGPL
>

If I can suggest, please consider MIT license for the following reasons:
- Trying to avoid proliferation of open source licenses, and this is the 
most used license nowadays [1] [2]
- it permits to avoid compatibility problems, even for open source 
projects, e.g. I had some (weird) constraints with the impossibility to 
use even Apache licensed software in an open source tool because the 
"sublicense" clause does not exist in it and I needed it for complying 
to sponsor constraints.
- it permits to avoid a lot of headaches with lawyers about what you can 
do and what you can not do; I wrote an essay about LGPL issues but 
unfortunately only in French [3]
- it permits to avoid a debate about which LGPL version and option you 
want to use (2.1, 2.1+, 3, 3+?)

The only counter-argument is that if you want to forbid closed-source 
versions, but I see from the other answers that this looks like not a 
wanted constraint.

[1] https://github.com/blog/1964-license-usage-on-github-com
[2] https://www.blackducksoftware.com/top-open-source-licenses
[3] 
https://linuxfr.org/users/zenitram/journaux/mon-evolution-vis-a-vis-du-copyleft

--------------9F5209454557FEA1C44EC8D9
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Le 16/01/2017 à 10:48, Matt Gruenke a
      écrit :<br>
    </div>
    <blockquote
cite="mid:CAJKCwWgSY38wv0_vMnWffJkdW5CPcW9Mgu+7myFuEyCyEKZS+A@mail.gmail.com"
      type="cite">
      <div dir="ltr">I also wanted to ask whether we could change the
        license of mkvwriter (or my fork thereof) from GPL to one of the
        following:
        <div>
          <ul>
            <li>Boost Software License (<a moz-do-not-send="true"
                href="http://www.boost.org/users/license.html">http://www.boost.org/users/license.html</a>)<br>
            </li>
            <li>MIT</li>
            <li>Apache</li>
            <li>LGPL</li>
          </ul>
        </div>
      </div>
    </blockquote>
    <br>
    If I can suggest, please consider MIT license for the following
    reasons:<br>
    - Trying to avoid proliferation of open source licenses, and this is
    the most used license nowadays [1] [2]<br>
    - it permits to avoid compatibility problems, even for open source
    projects, e.g. I had some (weird) constraints with the impossibility
    to use even Apache licensed software in an open source tool because
    the "sublicense" clause does not exist in it and I needed it for
    complying to sponsor constraints.<br>
    - it permits to avoid a lot of headaches with lawyers about what you
    can do and what you can not do; I wrote an essay about LGPL issues
    but unfortunately only in French [3]<br>
    - it permits to avoid a debate about which LGPL version and option
    you want to use (2.1, 2.1+, 3, 3+?)<br>
    <br>
    The only counter-argument is that if you want to forbid
    closed-source versions, but I see from the other answers that this
    looks like not a wanted constraint.<br>
    <br>
    [1] <a class="moz-txt-link-freetext" href="https://github.com/blog/1964-license-usage-on-github-com">https://github.com/blog/1964-license-usage-on-github-com</a><br>
    [2] <a class="moz-txt-link-freetext" href="https://www.blackducksoftware.com/top-open-source-licenses">https://www.blackducksoftware.com/top-open-source-licenses</a><br>
    [3]
<a class="moz-txt-link-freetext" href="https://linuxfr.org/users/zenitram/journaux/mon-evolution-vis-a-vis-du-copyleft">https://linuxfr.org/users/zenitram/journaux/mon-evolution-vis-a-vis-du-copyleft</a><br>
  </body>
</html>

--------------9F5209454557FEA1C44EC8D9--

--===============1212130876305213953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Matroska-devel mailing list
[email protected]
https://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel
Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel
--===============1212130876305213953==--