4 ms·

Looks like we see eye to eye on this one. Basically what I said is that the license (technically without the disclaimer) needs to appear (the ISC license choose

Looks like we see eye to eye on this one. Basically what I said is that the license (technically without the disclaimer) needs to appear (the ISC license chooses that language) somewhere. That's it. Put one copy of it somewhere (not sure if it needs to be visible to the end user) and your good to go. (Assuming that the license includes the copyright notice at the top.)

dalke 12y ago
I find your answer somewhat grating. I will explain why. We do not see eye to eye. I'm not trying to "figure this out together". I 'figured this out' years ago. I'm pointing out that you are using the wrong terminology, and trying to correct your understanding. We are not at the same level. For example, you said "not sure how you'd satisfy the condition without [a credits page]". That's the wrong terminology. It's a copyright notice and a permission notice. That doesn't require a "credits page". Though those notices could go on such a page, there's no requirement that there be a "page", and the term "credits page" adds needless terminology. By repeating meaningless or at least ambiguous phrases like "You have to retain the original copyright", and by using new and irrelevant terms like "credits page", you are adding to the confusion around copyright. Further, in your response to jeffmould you said "You're not contradicting anything I said, are you?". The thing is, you have since made a contradiction. jeffmould said that the code from ProjectA which is in ProjectB is not subject ProjectB's license. You said that the code is subject to a dual license. This is a post-hoc contradiction.
- teamhappy 12y ago
  Fair enough. > It's a copyright notice and a permission notice. That doesn't require a "credits page". Of course it doesn't. I tried to come up with a real world example because people (obviously) have a hard time figuring out what it means. I also added that the "credits page" might just be a folder full of licenses somewhere inside your project's directory structure. I hear you though. > jeffmould said that the code from ProjectA which is in ProjectB is not subject ProjectB's license. You said that the code is subject to a dual license. This is a post-hoc contradiction. I said it could be subject to two licenses. It doesn't have to, of course. You've also mentioned license compatibility in your other comment — I think you're trying to explain to me that my license can't revoke any rights granted to you by "the other" license. Does that sound about right?
  - dalke 12y ago
    "not sure how you'd satisfy the condition without one" doesn't fit with "Of course it doesn't." Regarding the second point, code from ProjectA, released under the MIT license, which is in ProjectB is not subject to ProjectB's copyright. This was jeffmould's scenario, and this code is not subject to two licenses. The ProjectB developers must do some creative act to the code before they can assert copyright on the modified code. Copying code from multiple sources is then subject to both licenses. It is also possible that with enough changes ProjectB is no longer subject to the original copyright from ProjectA. Quoting from http://www.ca10.uscourts.gov/opinions/13/13-6181.pdf http://www.ca10.uscourts.gov/opinions/13/13-6181.pdf : > A corollary of the “sameness” requirement is that “[c]opying deleted or so disguised as to be unrecognizable is not copying.” See v. Durang, 711 F.2d 141, 142 (9th Cir. 1983); see also Int’l Ass’n of Machinists & Aerospace Workers, AFL-CIO v. Winship Green Nursing Ctr., 103 F.3d 196, 203 n.6 (1st Cir. 1996) (“Even if a work is copied, however, no copyright infringement exists if substantial changes render the work unrecognizable.”); Warner Bros. Inc. v. Am. Broad. Cos., Inc., 720 F.2d 231, 241 (2d Cir. 1983) (“‘[A] defendant may legitimately avoid infringement by intentionally making sufficient changes in a work which would otherwise be regarded as substantially similar to that of the plaintiff’s.’” (quoting 3 Nimmer on Copyright § 13.03[B] at 13-38.1 to -38.2 (1983)). Which means that you could, with sufficient changes to the code, revoke rights granted by the other license. This is how Berkeley extracted itself from the AT&T license for Unix.

dalke 12y ago

I find your answer somewhat grating. I will explain why. We do not see eye to eye. I'm not trying to "figure this out together". I 'figured this out' years ago. I'm pointing out that you are using the wrong terminology, and trying to correct your understanding. We are not at the same level. For example, you said "not sure how you'd satisfy the condition without [a credits page]". That's the wrong terminology. It's a copyright notice and a permission notice. That doesn't require a "credits page". Though those notices could go on such a page, there's no requirement that there be a "page", and the term "credits page" adds needless terminology. By repeating meaningless or at least ambiguous phrases like "You have to retain the original copyright", and by using new and irrelevant terms like "credits page", you are adding to the confusion around copyright. Further, in your response to jeffmould you said "You're not contradicting anything I said, are you?". The thing is, you have since made a contradiction. jeffmould said that the code from ProjectA which is in ProjectB is not subject ProjectB's license. You said that the code is subject to a dual license. This is a post-hoc contradiction.

teamhappy 12y ago
Fair enough. > It's a copyright notice and a permission notice. That doesn't require a "credits page". Of course it doesn't. I tried to come up with a real world example because people (obviously) have a hard time figuring out what it means. I also added that the "credits page" might just be a folder full of licenses somewhere inside your project's directory structure. I hear you though. > jeffmould said that the code from ProjectA which is in ProjectB is not subject ProjectB's license. You said that the code is subject to a dual license. This is a post-hoc contradiction. I said it could be subject to two licenses. It doesn't have to, of course. You've also mentioned license compatibility in your other comment — I think you're trying to explain to me that my license can't revoke any rights granted to you by "the other" license. Does that sound about right?
- dalke 12y ago
  "not sure how you'd satisfy the condition without one" doesn't fit with "Of course it doesn't." Regarding the second point, code from ProjectA, released under the MIT license, which is in ProjectB is not subject to ProjectB's copyright. This was jeffmould's scenario, and this code is not subject to two licenses. The ProjectB developers must do some creative act to the code before they can assert copyright on the modified code. Copying code from multiple sources is then subject to both licenses. It is also possible that with enough changes ProjectB is no longer subject to the original copyright from ProjectA. Quoting from http://www.ca10.uscourts.gov/opinions/13/13-6181.pdf http://www.ca10.uscourts.gov/opinions/13/13-6181.pdf : > A corollary of the “sameness” requirement is that “[c]opying deleted or so disguised as to be unrecognizable is not copying.” See v. Durang, 711 F.2d 141, 142 (9th Cir. 1983); see also Int’l Ass’n of Machinists & Aerospace Workers, AFL-CIO v. Winship Green Nursing Ctr., 103 F.3d 196, 203 n.6 (1st Cir. 1996) (“Even if a work is copied, however, no copyright infringement exists if substantial changes render the work unrecognizable.”); Warner Bros. Inc. v. Am. Broad. Cos., Inc., 720 F.2d 231, 241 (2d Cir. 1983) (“‘[A] defendant may legitimately avoid infringement by intentionally making sufficient changes in a work which would otherwise be regarded as substantially similar to that of the plaintiff’s.’” (quoting 3 Nimmer on Copyright § 13.03[B] at 13-38.1 to -38.2 (1983)). Which means that you could, with sufficient changes to the code, revoke rights granted by the other license. This is how Berkeley extracted itself from the AT&T license for Unix.