Does the Apache 2.0 license require attribution on a commercial work on which it is based? I'm using Nativescript which is licensed under the Apache 2.0 license. Provided that I do not intend to change Nativescript itseft, but I'm using it to develop an application, am I expected to give attribution to the license and/or Nativescript in the final app that I deliver?
Yep, you are. You still need to keep the LICENSE and NOTICE files in the repository, if there were any in your copy of the project. These files contain the terms and conditions for the project, and provide attribution to the original developers. If you're trying to attribute in the UI of your application, you probably should. It's considered courteous and in the spirit of open source as well. This is also related: Do I need to include the full text of the MIT license in the UI of my app?
You have a false premise: "it offers the same conditions", and "MIT license is functionally equivalent to CC-BY". These premises are not true. CC-BY: applies to more than just software; it applies to artistic or literary work, databases, other material disclaims endorsement explicitly withholds moral rights explicitly does not license patent rights (MIT license gives anyone who obtains a copy of the software the right to use it, a patent right) prescribes the acceptable forms of attribution Those are just some of the differences.
I'll clarify my understanding of your hypothetical. X authors a comment. StackExchange publishes that comment, under a CC BY-SA 3.0 license, properly attributed to the original author Y edits that comment. StackExchange continues to publish the comment, still under a CC BY-SA 3.0 license, properly attributing the original author, X, but does not give any attribution to Y for their contributions In this scenario, Stack Exchange is properly respecting the license agreement with X. X is still given attribution, and the comment is still CC BY-SA licensed, and it indicates "if changes were made". StackExchange has no duty to X to display who made the changes. Stack Exchange may be failing Y, by not giving them any attribution for their edit. However, edits to a comment are often so minor that they are not copyrightable (deletions, copyediting, link fixing, etc.). If the contribution isn't even copyrightable, it doesn't matter that Y isn't given attribution. Y certainly isn't infringing X's copyright. X is given the required attribution.
You are required to provide a copyright notice on your work, such as putting (c) rhino 2016 in the liner notes. Nothing precludes you from licensing that copyright in any way you want, such as Creative Commons. As long as you aren't in violation of the last sentence (your work is not primarily the samples, and you actually made a song with them), then others should be able to use your work with no restrictions other than what you yourself place on the work. The purpose of requiring a copyright notice on derivative works is to give notice of who the actual author is and distance the original author from the derivative work. If you take their samples and make a song that is later at the center of a lawsuit (copyright, defamation, etc), the the copyright notice will hopefully steer people first to the derivative author and not the original author. That is the purpose of the clause in the copyright grant above.
Pretty much everything you need to know about the ownership and licensing of your material on Medium is in the Medium TOS you contractually agreed to when you signed up with the service. Basically, you granted Medium a license to use the work, but you did not agree to an exclusive license nor turn over copyright to them. Part of that Terms of Service – Medium Policy reads: Content rights &amp; responsibilities You own the rights to the content you create and post on Medium. By posting content to Medium, you give us a nonexclusive license to publish it on Medium Services, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it). In consideration for Medium granting you access to and use of the Services, you agree that Medium may enable advertising on the Services, including in connection with the display of your content or other information. We may also use your content to promote Medium, including its products and content. We will never sell your content to third parties without your explicit permission. You’re responsible for the content you post. This means you assume all risks related to it, including someone else’s reliance on its accuracy, or claims relating to intellectual property or other legal rights. You’re welcome to post content on Medium that you’ve published elsewhere, as long as you have the rights you need to do so. By posting content to Medium, you represent that doing so doesn’t conflict with any other agreement you’ve made. By posting content you didn’t create to Medium, you are representing that you have the right to do so. For example, you are posting a work that’s in the public domain, used under license (including a free license, such as Creative Commons), or a fair use. We can remove any content you post for any reason. You can delete any of your posts, or your account, anytime. Processing the deletion may take a little time, but we’ll do it as quickly as possible. We may keep backup copies of your deleted post or account on our servers for up to 14 days after you delete it. Pertaining to presenting Medium content in an iFrame on another site, this is reasonably close to not allowing that: You may not do, or try to do, the following: ... (2) access or search the Services by any means other than the currently available, published interfaces (e.g., APIs) that we provide;... You can use Embed Code Generator | Embedly to embed an iFrame of a Medium page on another site. But contacting Medium via the email at the bottom of the TOS would tell you for sure if it is OK. Comments on your pieces on Medium do belong to the owner. And You own the rights to the content you create and post on Medium. appears to cover the idea of copying your material from Medium to your own site. If in doubt, ask them.
The Google terms of service do not prohibit using their translate programs to create something that you sell. TOS for using their API would be irrelevant, since that isn't what you're doing. There is no clear copyright issue: as far as I can tell, there is not yet any case law suggesting that the output of a program can be owned by the copyright-holder of the program. (Copyright must be held by a legal person, i.e. an actual person or a corporation, and a program cannot yet be a legal person). A human-performed translation is subject to copyright protection since what is protected is that which is created by the (translating) author, and a program lacks that creative element. A translation owes its existence to the program-user using a particular tool to create the work, be it a pen or a translation program. What is unclear at present is whether a person using machine translation in a permitted fashion to create a derivative work thereby gains copyright to that derived work.
Why do you think Oracle have not been protecting their trade mark? Using a trade mark to describe the product (“Written in JavaScript”, “Seeking JavaScript developer”) is not an infringement and the trade mark owner is under no obligation to, indeed, cannot stop this. Where they are required to defend their trade mark is when it is being used in such a way that there is the risk of confusion that the goods or services could be confused with the trade mark owner’s goods or services. Further, they are not required to defend all breaches, only enough to show that they are actively doing so. Also it is not important that the trade mark be associated with the trade mark’s owner. Do you know who owns the trade mark “Ben &amp; Jerry’s”?
In general, the output of a program is not copyrighted by the author of the program. When you write a novel in Word, Microsoft doesn't own any copyright in your novel. When you prepare financial statements with Excel, Microsoft doesn't own any copyright in those either. There can be exceptions. Some programs (like GNU Bison, a parser generator) actually do output parts of their own source code, and their source code is copyright to the author. To clarify things, GNU made a statement in the license for Bison that officially says they don't have copyright to what it outputs. You should expect programs of this type to have such an exception, and if they don't, maybe ask the author or don't use them.