It is a IP infringement to use a proprietary graphics API from a company? Let's say the author of a operating system or graphics driver wants to implement Apple's Metal graphics API (application procedure interface) instead of the open Vulkan graphics API from the Khronos group. Will a license be required in this case?
In Google LLC v. Oracle America, Inc., 593 U.S. ___ (2021), the US Supreme Court addressed the reproduction of a subset of the Java API. The majority assumed for the sake of argument that the Java API was protected by copyright, but went on to hold that the reproduction was a fair use. We shall assume, but purely for argument’s sake, that the entire Sun Java API falls within the definition of that which can be copyrighted. We shall ask instead whether Google’s use of part of that API was a “fair use.” Unlike the Federal Circuit, we conclude that it was. So, it is an open question whether an API is protected by copyright, but the precedent from the Federal Circuit will be persuasive authority. The Federal Circuit held that the API is protected by copyright and the Supreme Court did not upset that conclusion. Second, the factors that led the court to conclude the reproduction of part of the Java API was fair use could turn out another way in another fact scenario. Some of the reasoning seems to generalize, but some seems specific to the Java development ecosystem. Briefly, the court recognized: API authorship is a creative process, but is &quot;functional in nature&quot; The reproduction was intended to assist interoperability; it was commercial; there was no evidence of bad faith The amount of code taken was a small amount of the entire Java work, an amount consistent with its goals The market harms to Oracle were dubious My prediction is that there will continue to be significant case-by-case uncertainty as to the applicability of the fair-use defence in this context.
They have copyright in their additional text, and possibly in things like their visual design choices (fonts, layout etc). They may also have introduced a few deliberate typos to detect any literal copies from their version (rather as mapmakers add a few imaginary features to their maps). None of this creates any rights to the original text. You are still free to produce your own copies of the original text. Just get it from some other source so you can be sure not to include anything of theirs.
Your understanding of the GPL is a bit off. GPLed code doesn't generally force you to GPL the output of the program, but that's just because the output of the program is normally not a derivative work of the program. For instance, if you write a novel in Emacs, your novel is an entirely original work. The fact that you used Emacs as a tool doesn't mean that your novel is somehow based on Emacs. This generator is different. It generates sprites by putting together art assets made by the program's creator. That means that the output contains a substantial amount of content made by the program creator, which means that it would likely be covered by the program creator's copyright. If the content was licensed to you under the GPL, you normally have to abide by GPL restrictions when you redistribute the content or incorporate it into your own program. Copyright holders can, if they want, grant additional permissions to their content and allow you to incorporate that content into nonfree software. For instance, the GCC compilers have an additional permission for their runtime libraries to let you use them in any GCC-compiled code; without that permission, GCC could only be used to compile GPL-compatible code. But unless the copyright holder has granted those permissions, when program output contains large amounts of their copyrighted content you're bound by the GPL when using it. In this case, the program specifically says that the art is dual-licensed under GPLv3 and CC-BY-SA-3.0. Since the generator's output is a combination of premade art assets (the buttons just let you tell the program which art assets to combine), the output is a derivative work of those assets. You can't use it unless your use is compatible with the GPL v3 or CC-BY-SA-3.0 (either works, since dual licensing lets you pick either license).
The MIT License (as distributed by OSI) does not include an attribution requirement beyond the requirement to include the copyright notice in any re-distributed copy including derivative works. The same is true of the description of the license as described in the Wikipedia article. If you sent back to the maintainer a modified version including your own contributions with an MIT license notice and your name in the copyright statement, that is a new work released under that license. The maintainer (or anyone else) may not lawfully use your work or incorporate it into a new derived work without complying with the license terms, which require retaining the copyright notice. By distributing the combined work using a copyright notice not including your name, it would seem that your license is being violated. You could contact the maintainer with a request that your name be included in the notice or your contributions be removed. If that is not accepted, you could use a take-down notice, or file suit. That last would involve significant costs, of course.
Yes, that’s allowed. Under the Stack Exchange terms of service, content you upload is licensed to Stack Exchange Inc. on a non-exclusive basis under CC-BY-SA 4.0. The terms of service do not give Stack Exchange the copyright to your contributions, and a non-exclusive license means you are not promising Stack Exchange that “only Stack Exchange will be allowed to use this content.” That means you can continue to do whatever you want with your own content and do not need to mention Stack Exchange at all. The only restriction is that you can’t stop Stack Exchange from continuing to use your Stack Exchange content under CC-BY-SA 4.0, and since it’s a Creative Commons license you also can’t stop anyone else from using your Stack Exchange content under that license.
The GPL doesn’t require you to distribute the software to anyone. The only requirement to distribute something is that if you do distribute the software to someone as a binary, you must also distribute the source code to them at no additional charge. The focus of the GPL is ensuring freedom for people who have copies of the software, not ensuring that the software is available to the world at large. Because your final deliverable is source code, you’ve already complied with the requirement to distribute source alongside object code. You have to comply with the requirements in section 5: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”. c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. You have to license the software to the company that hired you under the GPL v3 (since parts of it were licensed to you under GPL v3), so you can’t stop them from distributing it to the world. But nothing requires you to distribute it to the world.
A translation is a devivative work - the copyright owner has the exclusive right to these So, yes, translation is prima facie copyright infringement. Strictly speaking, if you translate it, it's a derivative work because you exercised creativity in making the translation; what Google translate does is not a derivative work, it's a copy because there is no creativity. Either way, only the copyright owner can do (or authorise) this. Whether it's legal or not depends on if what you are doing falls within one of the exceptions to the applicable copyright law such as fair use or fair dealing. Attributing the original author does not, of itself, allow translation. Additionally, I'm not able to find the copyright documentation for the site link I provided above. What is "copyright documentation"? Copyright exists the moment a work is created and no further documentation is required. Essentially, I could translate the whole documentation by myself to avoid this problem. No, you can't - see above. If copy-pasting the google translate is illegal, then exactly how much must I edit, move around sentences, change words, and such until the text is no longer plagiarized? All of it. If you were, based on your own knowledge of the software, to write a manual without any copying o the existing manual, that would not be copyright infringement. Is this plagiarism or copyright infringement? It's copyright infringement - plagiarism is an academic misconduct issue not a legal one. where can I check the copyright for the above link? The site you linked has "Copyright © 2020 Acquia, Inc. All Rights Reserved" in the bottom left corner which identifies the copyright holder, the date and prohibits all copying ("all rights reserved"). This isn't necessary but it is helpful. If you really want to do this, contact Acquia, Inc and ask for permission.
The creator of the software doesn't provide any warranty. If you feel confident in the quality of the software, nothing stops you from providing a warranty. If the software doesn't meet your guarantees, you will have to pay out because you provided the warranty, depending on the terms. Not the creator of the software because they explicitly didn't provide any warranty. If that's what you want to do, go ahead. I wouldn't. You don't have to republish under the BSD license, which you wouldn't. You must attach the license terms, which clarifies the role of the original creators, and that they don't give a warranty. Doing this allows you to copy the software. It doesn't mean you can't provide a warranty.