Boostrap licensing I try to understand thoses licenses' differences. If I build a website that allows users to browse and book a city trip, would the Standard License be enough ? I've read it a dozen times and I feel like its incoherent from a paragraph to another. Examples of Standard License Use: A marketing site for a paid application (where the Theme and it’s components are used only on the marketing pages) The Full Standard License - Basics You are licensed to use the Item to create one End Product for yourself or for one client (a “single application”), and the End Product can be distributed for Free. Make unlimited copies of the single End Product as long as the End Product is distributed for free You cannot sell the End Product except to one client.
While I agree that the license required for your use case isn't particularly obvious to me, the page you have linked to includes the following paragraph: Need help picking your license? Just shoot us an email at themes@getbootstrap.com and we’ll help you decide which license makes sense for your needs! So in this case, my recommendation would be to get in touch as described, that way you will know for sure that you are properly licensed.
Copyright and patents are two very very different things. Copyrighting a standard means the wording of the standard can not be copied without the copyright holders permission. It does not protect the ideas expressed in the document, just the way those ideas are expressed. IEEE standards, for example, are copyrighted by the IEEE and therefore you can't make a copy of the Ethernet specification, you need to buy it from them. That has nothing to do with implementing an Ethernet device. To implement something described in a technical specification might or might not require one or more patent licenses. The authors of the standard may not even be aware that something they require for the standard has already been invented and patented by someone else. Many standard bodies do impose a requirement on participants in the standard's creation that they offer licenses to any patents they own that are needed to implement the standard on a fair and equal basis to all. It is called FRAND - the acronym for fair, reasonable and non-discriminatory licensing.
Recall the basic principle of copyright law, as detailed in 17 USC 106: The copyright holder has the exclusive right to make copies; prepare derivative works; or distribute copies by sale, rental, lease, or lending. Other people can legally do these things only if they are given permission by the copyright holder, typically via a license. (Remember, the literal meaning of the word license is permission.) Often, the copyright holder will require a prospective licensee to accept various terms and conditions before the license will be granted. If there is &quot;no EULA&quot;, or if there is one but the purchaser has not agreed to its terms, then the purchaser has not been granted any such license, hence does not have permission to do any of the things listed above. If they do so anyway, it is illegal copyright infringement and they will be liable for damages. To use a firewall analogy, copyright law is &quot;default deny&quot;. So let's take your questions one by one: Do they own the software? US law has no concept of literally owning software. The closest thing is owning the copyright, which the purchaser certainly does not. It still belongs to the vendor that wrote the software (or whoever they may have later transferred it to). Can they legally alter the code of the program they purchased? No, that would be preparing a derivative work. The copyright holder has not granted them a license to do that. (There are some exceptions for purposes such as reverse engineering and interoperability, see 17 USC 1201(f)). Can they legally redistribute it No; again, that is the exclusive right of the copyright holder, and the purchaser has not received their permission. or transfer ownership? Maybe, if the first sale doctrine applies. Its application to software is complicated. The user has a better case for being able to sell the software if it exists as some tangible object which is transferred (physical media, pre-installed on hardware, etc). Can they legally modify the code of the program for others who have also purchased the same package? No, that would be preparing a derivative work. Can they take that software and install it on a secondary machine? No, that would be making a copy.
I see no reason to doubt your conclusion; since it's not allowed by the license it's forbidden by copyright. As you figured it, you gain the right to use these tools by obtaining one of those 3 Visual Studio licenses. A Visual Studio Code license is free, so it makes business sense that it doesn't include a license for Microsoft C++ Build Tools. I.e. you can't claim it's an "obvious oversight", as there's a justifiable business reason.
You are free to sell or not to sell to whoever you like (unless it is illegal discrimination, like not selling to white Christians), but it doesn't make a difference, because anyone who buys the software from you can legally sell it on to anyone they want. So you cannot control who ends up owning the software. If I want the software and you don't sell it to me, and I still want it, I'll just ask a friend to buy it and give them the money. Other people would just get a pirated copy if you refuse to sell to them (and would have very little bad conscience since they offered you cash and you refused to take it). You can put terms into a license, and in the USA this is binding. The customer may not agree with the license, and in that case they have the right to get a refund for the software. In the EU, I don't think a license is binding, so you'd have to sign a legally binding contract with the buyer. Apart from all that, you have very little chance to find out if the software is used against your wishes and to do anything about it.
It depends on what you are selling to the enterprises. You could be selling just a licence to use the program, and retain all the rights on the source code. You could be selling the rights to the source code. For #1, the source code is yours and you can do what it pleases with it1. In fact many programs offer both an open-source licence (which usually forces the user to make its changes to the code publicly available) and a commercial one (which allows the user to keep the modifications of the source code for themselves). For #2, the source code is no longer yours so it is not up to you to decide what to do with it. 1I am assuming no other agreements imposing limits on those; for example that none of your contracts to your customers have a clause forbidding you from making the code available to the public.
You also retain the right to license the work to others. Therefore you can sell similar rights to MusicBook and anyone else, as long as you do not grant an exclusive license (you have already licensed another party to distribute). They do not gain the right to sub-license your work. If you had executed a copyright transfer, you would have no rights to the work whatsoever (leaving out moral rights for jurisdictions that have them and where they are absolute).
A licence is your permission for others to use the work within the specific terms of the licence. You never license yourself, you license someone else or someone else license you. If you are the sole right holder of a work and you do not assign or transfer your copyright interests to others, you retain all rights regarding the work. Licensing your work under a CC licence does not make it impossible for yourself to use it commercially in the past, present or future. Of course, permissive licences like CC-BY might decrease the commercial value of your work since anyone else could reuse your work freely with minimum restrictions. But that does not prevent you legally from use your own work for commercial purposes. The exact choice depends on your wish on other aspects of using your work. For example, CC-BY-NC would require the licensee (essentially, anyone else not having another overriding agreement with you) to attribute/give you credits in order to use it non-commercially only, but they may remix and adapt your work as they wish as long as they credit you and the purpose is non commericial. You may also add an ShareAlike (SA) requirement where if the licensee creates an derivative work based on your work, they must license their derivative work using CC-BY-NC-SA as well. The last kind, CC-BY-NC-ND (NoDerivatives), would not only require credit when the licensee uses your work, but also prevent them from creating derivative works from your work.