Are there any licensing rules regarding code samples that I could include in my book? I'm thinking to write a book where I could need to use some code samples regarding a proprietary software (SAS in particular). So my question is, should I pay something to the software owner just for using some code rows? Or just because I mention the proprietary software name in my book? I stress that these code samples would be written by me, but usable in a software (as SAS is), that is not open source but is covered by copyright.
That a computer language is proprietary does not mean that all code written in that language is copyrighted by the holder of copyright on the language. Anyone may write, and publish, code in a particular language without permission from the language designers, or anyone else, provided that the code is original and is not a close paraphrase of code written by someone else. If the code to be published was created by someone else, permission would be needed unless the code falls under fair use or some other exception to copyright. Permission might or might not have to be paid for.
There is no loophole because a work released in object code form only — without the Corresponding Source — is not released under GPLv3, even if you say it is. GPLv3 only requires them to also provide whatever source came with it False. Providing the Corresponding Source is compulsory (§6 as pointed by @cHao). If they do not have access to it, it means the work has not been released under GPLv3.
There are two common approaches. The first approach is simply to let copyright law apply. Under the default terms, the IT provider has no rights to copy your software. Running software is allowed, of course, and not a problem that you need to deal with vis-a-vis the IT provider. You still can sue them if they copy your software, even in the absence of a contract. That is the chief function of copyright, after all! The second approach is to allow the customer to subcontract third parties to act on behalf of them, while acknowledging that such subcontracting does not dissolve them from any responsibilities towards you. In other words, if the 3rd party would do something unauthorized, you have a claim towards the customer and they have a distinct but related claim towards their IT supplier.
You can license the use of your IP only for certain uses, for example (most commonly) &quot;non-commercial&quot;. The general template of permission is &quot;You have permission to ___ as long as you ___&quot;. What the user is permitted to do, in your scheme, is something along the lines of &quot;only distribute the output in this manner&quot;, or &quot;not distribute code developed with this tool anywhere else&quot;. It's up to you to prove that someone violated that condition, if they did.
If the code is unrelated to your employment you own the copyright no matter if it is written in Visual Studio, on a piece of paper or tattooed on your butt. In the same way a sculptor owns the copyright in their sculpture even if they use someone else's chisel. Using Visual Studio in this way may, however, violated your contract with your employer and/or their contract with Microsoft. Why go there? Visual Studio Community is free.
Assumptions Let us assume that the code involved was created during the period of employment, was within the scope of that employment, and was validly work-made-for-hire (WFH). In that case, the code copyright is owned by the former employer.dn the person who wrote it has no more rights than a random stranger would. I am also going to assume US law. Ownership of Ideas Who owns the ideas, the knowledge of how these libraries work? No one does. In the absence of a patent, no one ever &quot;owns&quot; an idea. ]17 USC 102(b)](https://copyright.gov/title17/92chap1.html#102) provides: (b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work. Derivative Works Copyright law does prohibit anyone making a derivative work from a work protected by copyright without the permission of the owner. A derivative work is one &quot;based on&quot; the source work. The classic case is a translation. Exactly when a piece of software is a derivative work of another is fact-dependent. Bu several things are clear. If the source work is trivial and obvious, ther may not be sufficient &quot;originality&quot; for the source work to be protected by copyright at all. If the source work is not protected by a valid copyright, nothing is a derivative work of it. A &quot;hello world&quot; program, for example, is probably not original enough for any copyright. A straight-forward implementation of a basic algorithm like quicksort is probably not original enough, either. If there is only one way, or only a small number of ways, to express the ideas of the source work, the merger doctrine applies. This means that the expression of the work is merged into the idea, leaving the expression unprotected. When the merger doctrine applies, there is, in effect, no copyright. If a work copies ideas from a source, but none of its particular expression of those ideas, the result is not a derivative work, and is not an infringement of copyright. If a work is definitive, but is also a fair use of the source work, it is not an infringement. The usual four-factor fir use analysis must be made to determine this. In particular, if a work is highly transformative, it is likey to be found to be a fair use. Issues from the Question What if the new code (presumably, in the case of something simple) comes out exactly the same (even if I rewrite it without looking)? That Rather suggests that the work was too trivial to be original enough to have copyright protection at all, or else that there are only a few ways to express the idea, and the merger doctrine applies. But if neither o those were true, this might be an infringement. [* To be coninued*]
Your question mixes up two different aspects of intellectual property. From a copyright point of view, it is perfectly legal to reproduce the features of a one piece of software in another. The functionlity of the software is not copyright (although the detailed look and feel of the user interface might be). However you ask if you, as an employee, can do this by &quot;looking into the code of software X&quot;. Presumably by doing this learn something of the organisation and algorithms used. Even if you avoid direct copying, you are likely to have learned trade secrets of your employer, and publishing these is at least a civil tort in the US, and in some states a crime.
My question is, because I am not making any income from the distribution of the game, would the use of the copyrighted music fall under Personal Use? There are some &quot;private use&quot; exemptions in Australian copyright law but they have some fairly narrow conditions. These exemptions are fairly narrow because the point of copyright law is not to prevent you from making money with someone else's intellectual property but to protect the other person's ability to make money with it. If Alice writes a song and Bob distributes it free of charge, Alice loses revenue. Similarly, it is Alice's right to decide whether that song should be included in a freely available open-source software product, and her right to decide whether to allow that use without charge or in exchange for a license fee.