Howto correctly attribute GPL material in GPL software? If one integrates content (code, fonts, etc.) that is published under GPL in a software application that is published under GPL as well, how to correctly attribute the authors of the integrated parts? In detail it would be interesting to know How to attribute parts that are integrated in source form? (Where licence information is given in the file header) How to attribute parts that are integrated in binary form?
The GPL does require you to keep any existing copyright notices: You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you [...] keep intact all the notices that refer to this License and to the absence of any warranty [...] The GPL also recommends adding a notice to each file: Copyright (C) yyyy name of author - This program is free software[...] From my reading of the GPL, if the software you modify contains such notices, which is likely, you must preserve them. This effectively attributes the original author. However, as far as I can see, there is no requirement to have a list of acknowledgements (as is customary in scientific papers), which lists all the software you used. How to attribute parts that are integrated in source form? (Where licence information is given in the file header) If you keep the original file header (and possibly add to it), that should be enough. How to attribute parts that are integrated in binary form? As far as I can see, there is no additional attribution required for distribution in binary form. The GPL requires you to supply the source code along with the binary form, so the attribution in the source code will be available.
Here are the jury instructions. These describe how to evaluate witness testimony, burdens of proof, and the four-factor fair use test, among other things. The jury had to answer yes or no to the following question: Has Google shown by a preponderance of the evidence that its use in Android of the declaring lines of code and their structure, sequence, and organization from Java 2 Standard Edition 1.4 and Java 2 Standard Edition Version 5.0 constitutes a "fair use" under the Copyright Act? They answered yes. Juries do not explain their reasoning (different jurors might even have different reasonings), but the assumption is that they followed the jury instructions to arrive at this conclusion. To be clear, the issue wasn't reimplementation of 37 Java APIs, but a more limited taking, including "the declaring code and the structure, sequence, and organization".
Names of people, institutions, and events are not protected by copyright. Things that have occurred at events like math tournaments are facts, and may be recounted, in your own words, with no fear of infringing any copyright. Facts are never protected by copyright, although a particular description of facts could be, and so could a particular selection and arrangement of facts. Specific math techniques and their names are not protected either, and may be described without infringing copyright. The items you mention in the question are: video game / movie references and names No copyright issue here. common integration bee problems No copyright issue here. names of a university / math competition organizers No copyright issue here. integration techniques and formulas No copyright issue here, unless you copy an extensive description of a technique without rewriting it in your mown words.. using someone's Overleaf Latex package to format the book This depends on the license for the package, but there is not likely to be an issue. In short I think you are worrying over issues that are in fact non-issues.
Is it ok to copy the game concept and even with mostly similar content like "fighting", "building houses" etc ? Yes, but ... I should also mention that pretty much my whole User Interface is based on the User Interface from "Parallel Kingdoms" Is copyright violation. Ideas are not protected by IP law. The tangible representation of those ideas (art, words, layout, format etc.) is protected.
Software doesn't infringe any patents. Creating a product that includes the software may infringe the patent, and may infringe that patent because the software is included, but the software itself doesn't. Software on its own doesn't have any effect that could be patented, only as part of some machine. On the other hand, if you want to distribute software that is under the GPL v3.0 license, then a requirement is that you give everyone a patent license for all patents that would be infringed by using the software (as part of some machine), and if you are not the patent holder, then in practice that means you are not allowed to distribute the software. With your grand plan that you write software and then let the end users do the patent infringement, that will backfire in two ways: First, you'd be likely sued for contributory patent infringment, because it is you who enables the patent infringemnt. Second, you can be sued for copyright infringement because you have no license that allows you distribution of the software, depending on the Open Source license used.
There is no provision for automatically relicensing infringing works (for example, distributing a program that contains parts covered by the GNU GPL and that is therefore a derived work will not automatically place the infringing program under GPL, even if that is the expected way for derived works to comply with the license. Instead, the derived work becomes at the very least undistributable, as there are competing copyright holders that disagree.
In the EU, software license resale is legal, even if explicitly forbidden by terms of any EULA or other contract imposed upon the parties. To quote the European Court of Justice's press release on its ruling in a case in Germany between Oracle and a German reseller, An author of software cannot oppose the resale of his `used' licences allowing the use of his programs downloaded from the internet. [...] The principle of exhaustion of the distribution right applies not only where the copyright holder markets copies of his software on a material medium (CD-ROM or DVD) but also where he distributes them by means of downloads from his website. Where the copyright holder makes available to his customer a copy – tangible or intangible – and at the same time concludes, in return form payment of a fee, a licence agreement granting the customer the right to use that copy for an unlimited period, that rightholder sells the copy to the customer and thus exhausts his exclusive distribution right. Such a transaction involves a transfer of the right of ownership of the copy. Therefore, even if the license agreement prohibits a further transfer, the rightholder can no longer oppose the resale of that copy. There are many such companies in the EU who resell software legally, including used OEM Windows licenses that are far cheaper than retail copies. This is, in my opinion, a fantastic thing -- but undoubtedly has been behind the trend towards time-limited licenses rather than perpetual ones, which we all arguably suffer from today.
There is no contract between you (the licensee) and the licensor of the software. The creator of the open source software just says "here's the software, you may use it if you like, as long as you fulfil some conditions. ". No contract, no liability. I think the developer would only be liable if they intentionally created software that causes damage. (Which has happened, some open source browser plugins have recently been modified to run bitcoin mining software, or worse. I suppose the miscreants could follow all the GPL rules or whatever license is used).