Is recreating a proprietary game legal? I was wandering how is that open source projects on GitHub that aim to and in many cases succeed to recreate beloved games from the 2000's are not taken down? I think it's great and all, but if I am to recreate some NES game for example like &quot;super mario&quot;, will my game be illegal to distribute for free, and should I really care if it isn't legal, as long as no one in their right mind is going to sue me for an old 80's game?
will my game be illegal to distribute for free, Yes and should I really care if it isn't legal, I don’t know if you should care. The worst that can happen is that they can sue you for damage. Depending on how many downloads you get, that can be a lot or a little. as long as no one in their right mind is going to sue me for an old 80's game? People very much in their right mind will sue you. In the US, that’s $750 to $30,000 per download. If you get 1k downloads at $750 that’s $750,000 — well worth rolling the dice on a lawsuit.
germany I am reasonably sure that works like this would be Public Domain, i.e. not copyrighted in the first place. In Germany, copyright (or more precisely, Author's Right) can only be held by a natural person, which is a legal term of art that essentially means &quot;human being&quot;. There are two groups of natural persons involved here: the programmers and the creators of the works which are part of the training set. However, I can't see how either group could have a reasonable claim of copyright. Note: there have been similar discussions about GitHub Copilot, an AI that writes code for you. It is my understanding that the process used by GitHub Copilot is roughly comparable to the process used here. With GitHub Copilot, there have been instances where significant snippets which are part of the training set have appeared in the output with only minor alterations. In this case, it is likely that the original author will have copyright over that portion of the output. However, IFF a human being were actually involved in selecting specific works, then there is probably a copyright based on the creative decision of selecting this particular work and rejecting all the others. This is similar to the classic textbook example of a driftwood sculpture: the creative process here is not creating the sculpture but choosing to pick up this particular piece of driftwood instead of the hundreds of others on the beach. So, if you simply generate these works and publish all of them, there is no copyright. If you generate a large batch and then select a certain number, then the person who made the selection might hold a copyright.
The first thing that people need to do is to quit over thinking it. That being said, I'm going to see if I can tackle your problems one by one, before summarizing and providing my own opinion: Many users don't care if their code is copied. I'm like that. I left a couple comments on Shog9's post that read this: Good point: Licensing does not prevent careless or malicious use. I'm surprised about how many people are thinking that this license will let them steal their code, because it's already happening right now. I don't want to sound pessimistic, but when thousands of people break a license/law/contract, it's a bit of a lost cause. You're not significantly damaged in a direct way, so honestly, let it go. All I want is to make sure that no one can come up to me if something of mine screwed something on there side. Aside from that, I don't care about people who don't attribute me: chances are, they have no moral sanity, and I will appreciate the people who do, and help me out. As it is, I'm 16, I share what I know with a good heart, and in a well-spirited manner, and at the end of the day, knowing that I was able to help someone out makes my day. I don't mind if my code is copied. I know that people will copy my code whether I like it or not, but I also know that there will be people in the world who will say "thanks", and will try to attribute me where possible. I feel good about that. That being said, I don't care. But the person who uses my code does. The license that affects all Stack Exchange posts are licensed under the Creative Commons Attribution Share-Alike license, or CC BY-SA. Code contributions don't fit well with this. This excellent post on Open Source explains why it's discouraged for code. What these people want is a code-friendly license, so that they can stay in the clear when it comes to copyright issues. The next thing they want, is for someone to come after them over some licensing issue. You may think that people are good, but you never know the world around you. They can be evil. For other users, they don't mind their code being copied to another post, as long as there is a link to the post and a mention of the original author. Most people post with good intention. There's not that much of an issue from a legal perspective either: The license allows people to copy and paste into answers of their own, and since the license remains the same, there's no issue to get into. The license allows it, and contributors kind of have to acknowledge it. I don't think anyone cares what happens to code that is less than 3-4 lines at least. I can probably agree. Such code probably wouldn't be eligible for copyright anyway, since it's so trivial. Many jurisdictions have a "Threshold of Originality," which means that simple things can't be under copyright. Stack Exchange does not probably want people to own the code they submit. For example, Stack Exchange has (and probably wishes to retain) the right to keep even deleted posts in the visibility of the high rep users (even if the author is against it). Wait what? You may be right that it is in Stack Exchange's interest to host content. After all, they get hits, which helps them as a business. It is illegal for companies to host illegal content. If somebody sees objectionable, copyrighted content hosted on Stack Exchange that they would like removed, then they need to file a DMCA Takedown Request. This is also why moderators, like myself, cannot process legal requests. The reason why Stack Exchange doesn't act themselves, even if they see something that is copyrighted and objectionable, is because it's a form of liability. When YouTube began removing copyrighted content themselves, they received a wave of lawsuits (If you remove some, you need to remove all. Why didn't you remove mine? being the argument). The plaintiff's won those, and when YouTube did nothing, they weren't liable at all. If a user wants to have their content taken down, it's tricky. You need to look at the Terms of Service for Stack Exchange: (quoting Section 3) You agree that all Subscriber Content that You contribute to the Network is perpetually and irrevocably licensed to Stack Exchange When Stack Exchanges gets your content, you grant them an irrevocable license to your contribution. This is pretty standard across a lot of sites: it's just a way to secure data and stay in the clear of licensing issues. At the same time, it doesn't seem fair for SE to acquire complete ownership of the content. The user must still have the final say, if the content is to be used for purposes not already agreed upon in the licence. They don't. What users have done is that they have provided a license of their content to Stack Exchange. This is done, again, through their Terms of Service: You grant Stack Exchange the perpetual and irrevocable right and license to use, copy, cache, publish, display, distribute, modify, create derivative works and store such Subscriber Content and to allow others to do so in any medium now known or hereinafter developed (“Content License”) in order to provide the Services, even if such Subscriber Content has been contributed and subsequently removed by You. The user grants a license to their content to Stack Exchange, but they do not assign or relinquish copyright. The code still belongs to them. It's important not to conflate the user contribution policy, with copyright assignment. You are still free to add an additional license to your content (known as dual or multi-licensing), and have a copy for your own use. Stack Exchange will always host a copy licensed under the CC BY-SA license. Stack Exchange can expect a high level of decorum and respect for laws from its users. At the same time, it cannot expect redundant attributions anywhere and everywhere, because one of its main aims is to not waste the users' time. Not only Stack Exchange expects it, but many copyright laws in various jurisdictions require it too. There's a concept known in many jurisdictions known as moral rights. These are rights that are irrevocable, whether you like it or not. Generally, these include attributions, disclaimer of liability, and other rights as well. Even if your work is in the public domain, you still retain these moral rights. If memory serves me right, the right to be attributed is revokable under United States copyright law. Therefore, attribution becomes more a courtesy, when the right is revoked. Licenses such as CC BY, and CC BY-SA still require attribution as a part of their licensing terms. What defines attribution is generally up to the person who uses the content. If memory serves right again, one can not demand how to attribute. There should be a clear-cut way to determine what is code and what isn't. The code formatting indicators on SE may not be adequate because some users simply use backticks, or 4-space indented text for other not-so-codey text. Personally, I feel like making the entirety of a post under both the Creative Commons license and whatever proposed code license they use is the best option, and allow people to use moral judgement to determine the most appropriate license. The concern comes about people who lack such judgment. I bet these same people don't follow the existing license anyway - and are a lost cause. We made it through! There will always be debate on the license of choice. Some people want the GPL, a license that's apparently closer to the status quo of Creative Commons license (I disagree that it's a good match), while other's want permissive licenses, such as the MIT or the Apache licenses. I'd prefer the permissive type, since it allows use in closed-source applications, and grant more rights (i.e. less restrictions) to the people that use them. I'm not going to right much because my hands are tired, but I'm sure if you've got more questions about the open source licenses themselves, you can probably ask on Open Source Stack Exchange.
If any elements of the game are protected by copyright, then you cannot reproduce those elements (17 U.S.C. §106) unless your reproduction falls under a fair use exception (17 U.S.C. §107). Elements that may be protected by copyright include: artwork specific language on each card the aggregate effects of the cards (i.e. copying a single card's effects might not infringe copyright, but if you copy the effect of a bunch of the cards, such that you are taking expression of the original author's creativity, that might infringe, even if you change the words used) Whether an element of the game is protected by copyright is a fact-intensive question that would depend on the specifics of the game. Whether your copy infringes is likewise a fact-intensive question that would depend on what you copy. Fair use is also a fact-intensive, case-by-case analysis, but in my opinion, it is likely that creating a computer program derivative work (17 U.S.C. §101) of the game for your own personal education would be considered fair use. From a practical standpoint, even if it were not fair use, it would be near impossible for the copyright owner to discover. Posting the code on GitHub tips the scales away from fair use because of (17 U.S.C. §107(4)): "the effect of the use upon the potential market for or value of the copyrighted work." But, none of the factors are determinative on their own. You ask: I likely cannot simply change all the names of the various cards to something else, right? I agree. In my opinion, the selection and arrangement of the effects attributed to each card is an expression of the author's creativity, and no matter what you call the cards, copyright in the game would be implicated if you retained the effects associated with each card. If I start changing the rules of the game, does that make it legal for me to share my source code, for instance? At some point, it will be an entirely different game, so certainly, in the limit, your work would not be infringing. We can't answer where that line is, but in general, the less of the original author's creativity that you re-use, the less likely a ruling of infringement. Also, in general, the more transformative your work is, the more likely a fair use exception would apply.
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”?
Depends if the artist is a contractor or an employee Let's say I am the person who created Spiderman, but my artist came up with the design of the costume and everything Well, it certainly looks like you didn’t create Spider-Man - the artist did. If they are your employee then you, as their employer, own the copyright. If they are a contractor, then they own the copyright which can be transferred to you under the terms of the contract or otherwise. What if the design was written in paper and then the concept artist represented the written design graphically, does that make any difference? Not really. Here the artist has created a derivative work but since they did so with your permission, that’s fine. The derivative work is a seperate work with its own copyright owned as stated above. How can you make sure you don't face this problem if you hire an artist for your work? You set out in the contract who owns the copyright.
Yes and no. [note, the following is all written about US law. In other jurisdictions laws are, of course, different (though usually not drastically so.)] In the US there are (at least) three different bodies of law that might apply to code: copyright, patents, trade secrets. Copyright covers original expression. Anything you write is automatically, immediately protected under copyright. The copyright applies to the code itself, and anything "derived" from that code. It's up to the courts to decide exactly what "derived" means. One case that's long been viewed as a landmark in this area is Gates Rubber v. Bando Chemicals. The Court of Appeals for the tenth Circuit decision includes a section titled: "The Test for Determining Whether the Copyright of a Computer Program Has Been Infringed." Note that you can register a copyright, and that can be worthwhile, such as helping recover some damages you can't otherwise. Patents are quite different from copyrights. Where a copyright covers expression of an idea, a patent covers a specific invention. Rather than being awarded automatically, a patent has to be applied for, and awarded only after the patent office has determined that there's no relevant prior art to prevent it from being awarded. A patent, however, covers things like somebody else independently discovering/inventing what's covered by the patent. A trade secret could (at least theoretically) apply to some process or procedure embodied in the code. A trade secret mostly applies to a situation where (for example) you're trying to form an alliance with some other company, and in the process tell them things you don't tell the general public. If you've identified the fact that what you're telling them is a trade secret, and they then tell a competitor (or the general public, etc.) or more generally use that information in any way other than the originally intended purpose, it could constitute a trade secret violation. As a side-note: patents and copyright fall under federal law, so they're basically uniform nation-wide. Trade secrets mostly fall under state law, so the exact details vary by state. Absent a reason to believe otherwise, I'd guess your interest here is primarily in copyright infringement. The key here would be showing that one piece of code was derived from the other. That is, it specifically would not apply in a case where there were only a limited number of ways of doing something, so anybody who wanted to do that had to use one of those ways. Since this would not indicate actual derivation, it would not indicate copyright violation.
The words "proprietary format" are important. Are you sure the format is proprietary? If it is, then it's likely protected in which case they might have grounds to sue (but that does not mean they would definetly win). If the format is not proprietary, and so long as you don't share data which is proprietary then I believe you fine. I'm not a lawyer - but I cite GIF files as an example. They were still protected by the US and some other countries until at least the late 90s and there were various threats to open source linux companies who shared code that used the file format. I'm not aware of anything other than threats and never heard of any company being sued, let alone winning or losing. Another example that comes to mind is the RedHat ISO format. My understanding is RedHat could not stop anyone from sharing open source, but they could prevent folks from sharing the format they assembled and shared the open source. Again, I am not sure if it was ever tested in any court of law anywhere.