If a project is open source does that mean I can integrate it

>>240595
Maybe. Read the terms of the license.

File: Screen Shot 2016-12-23 at 10.16.58 PM.png (95KB, 577x428px) Image search: [Google]

95KB, 577x428px

>>240596
Here's the license.

So do I just include a
>Copyright (c) 2016 Plotly, Inc
And a link to the license in each page including plotly and I should be good?

>>240600

You might want to read on open source licenses.

Here's a good rundown of the MIT license: https://en.wikipedia.org/wiki/MIT_License

From what I can tell, you're free to do pretty much whatever you want with it, so long as you include a LICENSE file with the MIT license on it. I think so, anyway. I'm not too versed on open source licenses. But I think the wiki entry is a good place to start.

>>240603
Here's a site explaining it

https://tldrlegal.com/license/mit-license

>>240600
You need to include the actual license, not just the copyright statement.

But you can include it in the source code; you don't need to display it to the user. Google "obnoxious advertising clause" to see the difference.

If you do have an "about..." page that lists the copyright status of the work, then it would be factually correct to include the library's copyright line, but there's no legal requirement to have an about page, and no requirement that an about page actually be correct.

File: image.jpg (149KB, 750x560px) Image search: [Google]

149KB, 750x560px

>>240600
Here's Apple using MIT code in iOS.

There's no copyright statement in the places the code is used, but there's a "legal notices" page for the entire OS, and that includes the copyright statement and license in its entirety.

It does it for every piece of OSS in iOS, so it's like ten meters long.

>>240738
>>240734
Ahh that makes a lot of sense. So basically the entire license along with the company's copyright? Thanks family