Copyright on Developer&#39;s Website I've been trying to find concrete information about developer's copyright. If a developer has its own website (in terms of business [card]) and the projects that are part of the portfolio were projects created and sold by a company, does the developer have some sort of rights to the work? After all, even though the client payed, the designer designed it and sales brought the project to the company, the programmer made it «tangible». What rights should and should not be attributed to the developer? Is it okay to use this projects as part of the developer's portfolio?
The fact that a developer is showing off work that he/she has done for other another company doesn't imply that that developer owns any copyright to the work. In Canada, see the Copyright Act, § 13 (3): Where the author of a work was in the employment of some other person under a contract of service or apprenticeship and the work was made in the course of his employment by that person, the person by whom the author was employed shall, in the absence of any agreement to the contrary, be the first owner of the copyright and § 13 (4): The owner of the copyright in any work may assign the right... In the US, see 17 U.S.C. § 201 (b): In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. and § 201 (d): The ownership of a copyright may be transferred... "What rights should and should not be attributed to the developer?" That is a business decision to be made on a case-by-case basis. Advice about the prudent balance of copyright between an employer/client and employee/contractor is legal advice. "Is it okay to use this projects as part of the developer's portfolio?" If the developer can link to public use of a product that he/she developed for a company, then the developer is not violating copyright by simply advertising that they worked on the product and linking to, without reproducing, the work. If the developer for whatever reason maintained copyright ownership in the code and other assets, it would not be copyright infringement to reproduce those as part of the portfolio. If the developer did not maintain copyright ownership in the code or assets, reproducing those may be copyright infringement, dependent on whether the copyright owner allowed the developer to reproduce those elements, or if the reproduction is fair use. There may be other laws or contracts implicated, though: non-disclosure agreements, trademark law, among others.
Do you have an explicit permission by the artist? Does the artist give a blanket permission to anyone which covers this kind of use of their work (a license)? If no, then you commit a copyright violation when you use their work for your blog. This applies to practically any country which signed the Berne convention which is almost everywhere in the world. Having no commercial interest is usually not an excuse to violate copyright. Regarding which jurisdiction applies when you, your website and the copyright holder are in different countries: I opened a new question about this.
Person A has to have created the data to hold copyright; for most kinds of data this has no legal effect because facts are not protected by copyright. A mineable database probably does not have the necessary creative elements for copyright. An algorithm is not protected by copyright (it might be patented). Person C's program is copyrighted. The product created by D is probably copyrighted, depending on what degree of creativity is involved in their transformation. If the transformation is automatic then no, but if creative judgments are applied to the output of the program then maybe. Though the resulting product is another database of facts, and the facts cannot be protected. In terms of "using the model", only C and possibly B have any control. If it is necessary to validate the software using A's data and A has kept the data secret, C might negotiate with A to use the data, in order to complete his program, and that could give A some interest in the program.
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*]
It's really your client that should be asking these questions. Writing the app is perfectly legal. So you can enter a contract with that client to write the app and deliver it to them, ready to be put on the Google Play store or the App Store (entering a contract needs to be done carefully, obviously). I'd make 100 million percent sure that the contract states clearly that you have zero responsibility if the app is rejected or removed for non-technical reasons, and that the legality of actually selling and running the app is also not your responsibility. The reason is that I very much suspect that running the app might be illegal, and that the chances of getting it permanently on one of the stores are rather slim. And solving those problems is outside of what a software developer can competently do.
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.
What happened is that you created a legal mess. You are obviously on the hook for copyright infringement. The maintainers of the project will scramble to replace your code with newly written code. They will likely ask your company which code they are complaining about - that puts your company into the problematic situation that they shouldn't identify code that isn't theirs, that it will be hard to sue for infringing code when they didn't give the project maintainers a chance to fix it, and that everything they identify will be replaced. Since it is your actions that caused the trouble, anyone suffering damages from your actions can sue you.
The general idea of such an app is not subject to copyright protection. Ideas never are protected by copyright. So creating an app based on the functionality of a fictional app would not be a copyright violation. The logo might, if it is original enough, be protected by copyright. Any or all of the "name, the logo and the color scheme" might well be subject to trademark protection. (Names and other short phrases are not protected by copyright.) You would be wise not to use these identifying elements of the show, but instead create ones sufficiently different that no reasonable person would be confused into thinking that your app had been used on the show, or was sponsored, endorse, or approved by the show or its creators. An explicit disclaimer saying that you are in no way associated with the show or its creators, and your app is not approved by or endorsed by them would also be wise. Otherwise you might be accused of trying to pass off your work as affiliated with they show, or to trade on the show's reputation and fame. Whether you make your app an open source work is not in any way relevant to copyright or trademark claims. Whether you charge for your app is of only limited relevance to a copyright claim. Whether you sell or market your app, or use it to advertise some other product or service is relevant to a trademark claim, as trademarks are only protected against their use "in trade" which generally means commercially. However, non-commercial use of a trademark may constitute "dilution" of the mark, which may give rise to a cause of action against the person using it.