<div dir="ltr">Thanks,<div>more explanation:</div><div><br></div><div>I have all licenses and they are all MIT License, but for example, if a PHP code page includes more than 5 parts of codes from that different MIT License Projects<br>if I add all my Licenses at the top of the file is it enough? so at this point, the license of all used codes are added to the file with other licenses(may include license and it was not used).<br></div><div><br></div><div>so is it ok if I add the license text to the top or bottom file that the code is used in, but not specifying which code is for this license text?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 10, 2020 at 12:16 AM Ashkar Dev <<a href="mailto:ashkardev@gmail.com">ashkardev@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br>Thanks for replay<br>These are explanations of my question:<br><br>I mean if I get code from a project or get the full project that is under MIT License,<br>how I can do this while I use that codes in my Web Application :<br><br>if I have a page and it includes some codes, some of them are mine code and there is also some part from some MIT Licensed Projects so is it legal to add all licenses at the top? I mean not adding the License directly with the code but at the top of its file.<br><br>because I am on developing a project and used MIT Licensed codes of others and I collected the Licenses but now I'm not sure which code is with which license and also the code was may be modified so if at each of my code files I add just all license texts is it enough right?<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020 at 3:00 PM <<a href="mailto:license-discuss-request@lists.opensource.org" target="_blank">license-discuss-request@lists.opensource.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send License-discuss mailing list submissions to<br>
<a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:license-discuss-request@lists.opensource.org" target="_blank">license-discuss-request@lists.opensource.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:license-discuss-owner@lists.opensource.org" target="_blank">license-discuss-owner@lists.opensource.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of License-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: MIT License (Thorsten Glaser)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 8 Apr 2020 13:04:55 +0000 (UTC)<br>
From: Thorsten Glaser <<a href="mailto:tg@mirbsd.de" target="_blank">tg@mirbsd.de</a>><br>
To: <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
Subject: Re: [License-discuss] MIT License<br>
Message-ID: <<a href="mailto:Pine.BSM.4.64L.2004081302220.31902@herc.mirbsd.org" target="_blank">Pine.BSM.4.64L.2004081302220.31902@herc.mirbsd.org</a>><br>
Content-Type: TEXT/PLAIN; charset=utf-8<br>
<br>
Ashkar Dev dixit:<br>
<br>
>can you explain the point that says to include the license of used code,<br>
>but can it be included inside the file but not directly with copied code?<br>
<br>
Not sure I understand you directly, but:<br>
<br>
If you redistribute some MIT-licenced work which has documentation,<br>
and the documentation is part of the distribution, it?s enough if<br>
the licence is reproduced in the documentation.<br>
<br>
In all other cases, you have to include the licence with the work<br>
itself.<br>
<br>
As an example, you cannot just distribute a minified version of<br>
some MIT-licenced ECMAscript library. You have to either add the<br>
licence as comment into it or put the licence in documentation<br>
that?s distributed along. (Note that minified equals compiled,<br>
not source, so, to count as Open Source, you have to also make<br>
the source code available.)<br>
<br>
IANAL, TINLA.<br>
<br>
bye,<br>
//mirabilos<br>
-- <br>
15:41?<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of License-discuss Digest, Vol 97, Issue 4<br>
**********************************************<br>
</blockquote></div>
</blockquote></div>