-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License is MIT? #599
Comments
Copyright and license are two different things.
Whoever writes it owns the copyright. What you permit others to do with it is the license.
Henry Unger
Pulsiam
http://www.pulsiam.com
On Aug 6, 2023, at 1:32 PM, Lucinda-Rakes ***@***.***> wrote:
I'm not sure what is the license of this library and how can I use it. From one angle, its very clear the main repo license is MIT as stated here: https://github.com/illuspas/Node-Media-Server/blob/master/LICENSE.
On the other hand, some of the file in the repo have a copyright notice.
https://github.com/illuspas/Node-Media-Server/blob/master/src/node_http_server.js#L1-L5
//
// Created by Mingliang Chen on 17/8/1.
// illuspas[a]gmail.com
// Copyright (c) 2018 Nodemedia. All rights reserved.
//
Which should I believe?
—
Reply to this email directly, view it on GitHub<#599>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAKCLT4MAAZSVZWEGSMGAWLXT7PNHANCNFSM6AAAAAA3GCMXMQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Got it, thank you for the explanation! |
close the issue btw |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure what is the license of this library and how can I use it. From one angle, its very clear the main repo license is MIT as stated here: https://github.com/illuspas/Node-Media-Server/blob/master/LICENSE.
On the other hand, some of the file in the repo have a copyright notice.
https://github.com/illuspas/Node-Media-Server/blob/master/src/node_http_server.js#L1-L5
Which should I believe?
The text was updated successfully, but these errors were encountered: