4 ms·

You get to choose the license that works best for you. http://savannah.gnu.org/maintenance/DualLicensing/ http://savannah.gnu.org/maintenance/DualLicensing/

• conradk 11y ago
  Isn't MIT compatible with GPL though ? If it is, what's the point of having both ?
  • deleted 11y ago
    [deleted]
  • billyhoffman 11y ago
    From a business's perspective, the MIT license is similar the BSD license: you can incorporate MIT licensed code into commercial products/proprietary code and only have to include copyright notices. GPL has source code disclosure implications which can be deal breakers for some businesses.
    • gruez 11y ago
      I think he was asking why anyone would choose GPL, considering MIT is more permissive in every way.
  • simple10 11y ago
    Making something dual licensed allows for the next dev to make modifications and then release those mods under his/her preferred license. You could make a mod of favicon.js and release your mod under GPL to ensure any further modification of your code and your favicon.js branch stays under GPL.
    • deleted 11y ago
      [deleted]
    • vbernat 11y ago
      It's possible to release a mod under GPL when the original license is just MIT.