Skip to main content
10 events
when toggle format what by license comment
Oct 28, 2020 at 15:27 comment added Fenton @dan.mwasuser2321368 when you distribute software, you need to supply the licenses for each part. You can either keep the licenses intact next to each component, or roll them all into a file that lists each component and licence.
Oct 22, 2020 at 1:22 comment added dan.m was user2321368 What I can't seem to comprehend is how that paragraph,"Permission is hereby granted...", which I'm required to include if I want to distribute my work which uses Yannbane Awesome Library, is only applicable to Yannbane, and not my new work. I don't see how the term software, in "a copy of this software" doesn't apply to all the software I gave/sold them.
Jan 22, 2019 at 14:43 comment added Prakash P @HBhatia No, it does not make any difference. Just include the MIT license when you distribute your SAAS product.
Nov 15, 2016 at 8:24 comment added HBhatia What if my application is a SAAS (Software as a service). Does it make any difference?
Jan 31, 2016 at 10:34 comment added ptim This is the first answer I've found that addresses my circumstances as a freelance dev using third party components.. tx for the link to the Firefox license!
Sep 28, 2015 at 10:07 comment added Fenton With the final clause, the copyright notice must be shipped with the software, so it makes no difference that it is just binaries, you still need to include it.
Sep 28, 2015 at 5:01 comment added André Fratelli Do these notices have to be included when distributing binaries or just source?
Dec 8, 2012 at 20:45 vote accept jcora
Dec 6, 2012 at 10:21 comment added user281377 Exactly. It's not unusual for a large product to include several such copyright notices. For example, check out about:license in Firefox.
Dec 6, 2012 at 10:12 history answered Fenton CC BY-SA 3.0