Are licenses on &quot;source available&quot; products binding? There are a number of companies which make their source code available in various public forums like Github or Gitlab. These products are not open source, but the source is available for public commentary or research purposes, or simply for the appearance of transparency. Of particular note, Gitlab themselves makes their enterprise edition source code available.The code in this repository has a license located here. I have usually assumed that source code licenses are only relevant in the event that you attempt to prepare a copy of the software, not if you build/otherwise use it for personal (or even organizational) purposes. Thus, my question is: can you acquire a copy of the source code for a &quot;source available&quot; product without binding yourself to the terms of the license that is distributed with that source? If you do, can you build/run it without being bound by said license?
If you do, can you build/run it without being bound by said license? No, you cannot. Because there is no way to &quot;build/run&quot; it without making a copy. You copy the sourcecode, before you can run your compiler. That is the copy you are making, not copying the file that results from this process. A valid question might be, are you bound by the license? Well, that is up for lawyers and a court to decide, but in all countries I know, copyright is automatic for anything worth copying. And the copyright holder can grant licenses to people to allow things. So arguing you are not bound by a specific license would mean you would argue that you are bound by the legal default, which in most countries is &quot;You cannot copy that. At all. Unless you have explicit permission&quot;. That argument would sound like &quot;I stole all 10, because the offer of buy-one-get-one-free was not legally binding&quot;. Maybe it wasn't. But that doesn't mean you get to do something unrelated illegal instead. Now, there are many exceptions for &quot;personal use&quot;. You can sing any song in the shower. I would assume you can compile any program there, too. You just cannot use that program for anything worthwhile, the same way you cannot record your song in the shower and sell it.
Udemy claims that all the videos and course content are copyrighted, but does that also hold for the material of the course? Yes, all the material is copyrighted. Ideas are not, material and content is. it would be really useful to me if I could take a large part of that code ... I want to know if I am allowed, by the law, to use this code for commercial purposes, or is it protected as the intellectual property? Yes, it is protected, specifically it has copyright applied and you may only use it if the license it is distributed under allows you to - in some cases this may be a permissive license, or the code may be obtainable legitimately from another source under a permissive license, in which case its usable. But in many cases, it may not be distributed under a permissive license or indeed any license, and in such cases you will not be permitted to use it. The license under which the code is released depends on the individual course, and in many cases the source code repository or download site for the code for the course. Check their for a license.
may require that you obtain license rights from third-party owners or licensors of content that you include in your text inputs (Emphasis mine). Based solely on the excerpt above, yes, you have the copyright on the audio files if you created the source material, as you are the creator, using Amazon Polly as/to generate a "tangible medium". One of the central rights granted by copyright is to control translation into a different medium (in this case, from text into audio), as is the right to control distribution, which is what this excerpt is talking about. "Third party" in this case means neither you nor Amazon. Basically, Amazon is informing you that using their software on someone else's copyrighted material does not grant you copyright on the audio recording.
The MIT license is non-exclusive. If S is the sole copyright holder, S can issue any other non-exclusive license in parallel, and can also stop offering the software under the MIT license. However, open source licenses such the MIT license are generally understood to be irrevocable, so S cannot prevent other people from using the software who already received it under the MIT license terms. But: only if S is the sole copyright holder. There is no particular reason to believe that S would be the sole copyright holder. One does not gain a copyright ownership just by supervising other people, although an employer might gain copyright ownership over works created by employees (e.g. the US “work for hire” doctrine). That the copyright notices only mention S's name is an indication that S might be a copyright holder, but that's neither sufficient nor necessary for showing that S holds sole or joint copyright in the software. This leaves three relevant scenarios: S might be the sole copyright holder, in which case, yes, S can effectively discard the MIT license. This might be the case e.g. if there was some other copyright assignment, outside of the MIT license. What copyright transfers or assignments are valid depends on the local laws, e.g. some jurisdiction do not recognize copyright as transferable and at most allow the assignment of economic aspects of copyright. S might not be the sole copyright holder, but have additional permissions to the work. For example, there might have been extra licensing agreements, outside of the MIT license. Or S might have special rights for a work of joint authorship, if and only if the jurisdiction recognizes such additional rights. S might not be the sole copyright holder and not have any agreements outside of the MIT license. Then S has no additional rights, and is bound by the terms of the MIT license. This doesn't have to be a problem: S can still pretty much do whatever S wants with the code, as long as S fulfils the license terms. These are pretty simple: just keep a copy of the copyright+license notice with any copies of the software the students created.
Yes. This is a frequently asked question on the foundation's homepage, and answered without ambiguity (source): Can I use a Raspberry Pi in a commercial product? This is a very common question, and the answer is yes! Once you have bought a Raspberry Pi, it's yours to do with as you wish. You would be in good company too, as in fact the Raspberry Pi is regularly used and sold for commercial applications third parties. Note that this the default consequence of a contract of sale in all jurisdiction I know of (but I am not a lawyer): The seller does not retain property rights in the particular item, and by the mere selling of the item implies there are no other rights that might prevent the buyer from using it as they wish. Apart from the particular computer now in your property, there are other legal requirements: &quot;Copyleft&quot; softweare: Large parts of the Raspbian software are licensed under &quot;copyleft&quot; licenses (importantly, versions of the General Public License, GPL). These licenses are meant to provide your customers with the means of reproduciing and building upon the &quot;copylefted&quot; software. You will need to provide your customers with the source code to those software items, the tools and documentation needed for building, and a written notice. Your own programs need not be licensed under a &quot;copyleft&quot; license, provided that you don't build on (distribute &quot;derative works&quot; of) &quot;copyleft&quot; software. The open source licenses involved are not meant to exclude commercial use, and there are helpful compliance guides available ( a, b ). Non-free software: Make sure to not include non-free software, like Mathematica or Oracle Java, which are not licensed for commercial redistribution. Trademarks: Your use of the words &quot;Raspberry PI&quot; or the raspberry logo is subject to restrictions, as is usual with trademarks. Speaking of the logos: You can request permission to use their &quot;powered by Raspberry Pi&quot; logo. Market regulations: You need to abide by regulations, for example safety and electromagnetic interference. Repackaging the Pi might mean you'll need to test and recertify your product, I'm not an expert. Video codecs: Some Raspberry Pis (up to 3) include specialised video decoding hardware. If you want to use it with the MPEG2 codec, you'll have to buy an activation key for small one-time fee per device - £2.40 for MPEG2, £1.20 for VC-1; other codecs are already activated. I don't think you'll need a license even for commercial, for-sale devices, but I am not your lawyer. Just to be clear, nothing prevents your buyers from cloning your software. (This is not a consequence of you providing the Raspbian source code - they can just clone the contents of your SD card.) While you can retain copyright in your own code, you'll probably have no effective means of detecting infringement. However, the physical design of the rest of your device will not be affected. Your business model needs to account for this fact.
Yes, a work with no license is All Rights Reserved, reserved meaning the creator of the work. Who is the creator of the work ? Everyone who contributed it, unanimously. Yes. If people contributed any copyrightable part of your work, in theory you cannot add any license or grant any right to use/reproduce/whatever the work without their unanimous agreement. That's very cumbersome, and almost nobody really does that, but it's what the law is. Big serious companies and repos require contributors to waive their rights on the code they contribute, by agreeing to a contributor's agreement. For example, python/cpython requires you to give your contribs a license allowing the python org to do essentially what they want with it, even though you retain copyright over them. If your project is not so serious, I suggest it should be enough to make the license clear, and that by contributing people are agreeing to place their contribution's code under the license. If it's a free license, that's all you need.
How can you get in trouble? If they see any code you wrote for them show up in your open source project. They own the code you write on company time. Even if your code goes into an open source project owned by the company, you still don't own that code. The only way you can own it is if they directly tell you that you may put it into your open source project. If you make your open source project private so nobody else can see the source code, but they see your side business has the same features you wrote for them. You can try to get around problem #1 by hiding your open source project. But if they see the same features in it that they told you to write for them, they can become suspicious. They might force you to reveal the source to them in court. If you don't want them to see it, they may force you to share it with a third party who is bound by an NDA. The third party can compare your code to theirs and report if you copied any code. Even if your work is not directly related to the company products, your work for them can be a company secret. You reveal that, and you are in trouble. You say your work improves internal procedures, but is not directly related the company products. If a company can reduce its cost, it can lower its prices and still make more money than their competition. That gives them a competitive edge over other businesses. By revealing how your employer does its internal work, you give that competitive edge to their competition. Although you say your open source project does not violate rule #4 - "does not reveal company secrets" - all three explanations mentioned above say it does. What can you do? Quit and start your own company based on your open source project. If you quit, you should do it before you write any code related to your project for your employer. Ask your company to fund your project. Talk to your boss and anybody else there who might be a stakeholder. Tell them what you can do. Make a deal with them that you get to work on your project during work hours. Maybe they could turn it into an additional source of revenue for the company. That changes you from a potential loss into a valuable asset. Their competitors might end up buying products based on your code. Many companies would love for their competition to pay them. Ask your employer to allow you to turn your work into your open source project. Some companies require employees who work on open source projects to give their employers a royalty-free license to use and modify the work as they wish. Ask your employer if they would use a product based on your project. You can start a side business (with your employer's blessing), and turn them into your first customer. They get access to a beta product before their competitors do. Promise them they get it free or at a hefty discount for a year or two before the competition even knows what you have. The first option is win/lose. You win and your employer loses. The other three options are win/win. Good luck!
The law itself wouldn't specify what origin of code can be retrieved and then executed. The terms of service of Google would be what would restrict you from doing this or not, including what consequences you would have if Google discovered this. I can say that as a developer, I have created assemblies in C#, sent them to a server and my application downloaded them and executed them. In my case the assemblies were compiled from script code that the user created themselves and so they knew this was happening. There is no law that dictates that a particular block of code must go through a vetting process by Google prior to running. A quick check of Google's terms of service say that they do not allow this kind of updates. Here is a quote: An app distributed via Google Play may not modify, replace, or update itself using any method other than Google Play’s update mechanism. Likewise, an app may not download executable code (e.g. dex, JAR, .so files) from a source other than Google Play. This restriction does not apply to code that runs in a virtual machine and has limited access to Android APIs (such as JavaScript in a webview or browser).