Who are the copyright holders of softwares that students develop during their studies? The outputs of a software developed from scratch by a student during his/her studies are used in writing his/her thesis. Can the student's supervisor or the University claim to be a copyright holder of the software? What if the student was paid by the University as a Research Assistant?
The general rule is that the author of the software owns the copyright, so that would be the student. This is regardless of whether the student writes the code for fun, or for a thesis. If a student is hired to write that code, then it kind of depends on the university rules, and who hires the student. In the case of a "work for hire", the employer owns the copyright. However, it is non-trivial to determine whether that principle is applicable in the case of a student hired by the university. In part, it depends on which country this is in because work for hire laws are not exactly the same everywhere, and in part it depends on the details of the employment my a university. In a typical US institution RA appointment, it would come down to university policy – some universities declare that copyright in all student-written software is retained by the student. You would need to look for something resembling an "IP Policy" – here is a sample, note that such policies are subject to revision.
The software being free and open source has no impact on whether it infringes any patents or violates any copyrights. Copyrights attach to fixed representations of creative work in a tangible medium (e.g., the actual code and graphical elements of the software in question). As long as you aren't copying the copyrighted work of someone else, you should be in the clear. So, if you write your own code from scratch, or rely on code that you're allowed to use (e.g., "free" software with a permissive license that allows it to be used freely), you should be fine. On the other hand, if you copy a chunk of code that you aren't allowed to use, and then change the variable names so that it's superficially different, you're likely violating someone's copyright. Patents are a much more difficult question. To determine whether you would infringe any patents, you would have to read the independent claims of every patent that might be related. If you perform all the steps of any one of those claims, then you are infringing that claim (and therefore, the patent in which it is found). Unfortunately, this is much easier said than done. First, it may be difficult to search for all the potentially relevant patents, and once you've found them, there may be far too many to read. Second, claims are written in a type of language that is specific to patents, and someone without experience in patent law may not understand them correctly. Finally, the terms in the claims may not take on their plain English meaning, but rather may have been defined by the language in the rest of that patent, so it's possible that you might incorrectly think you were in the clear based on a misunderstanding arising from that. All that said, it may be best to go ahead with implementing an idea and then waiting to see what happens. Chances are that the implementation will arguably infringe some patent in some way, no matter what's done. But chances are also high that there will never be any worrisome enforcement action taken against it by a patent owner, simply due to the difficulty and expense associated with enforcing patent rights.
It's not fair use. Fair use is when you do something that normally only the copyright holder can do. Playing a video game is the ordinary, intended use of the work. In the United States, ordinary use is not protected by copyright. 17 USC 106 sets out the rights protected by copyright. The include copying the work, producing derivative works, distributing the work, and so on. None of these are ordinary use. Someone could perhaps argue that you are creating a derivative work. I doubt that argument would work because you are not taking any protectable elements from the work. But if anyone did argue that, it would make sense to also argue that if that's so, your use would still be covered under fair use because it's transformative, does not substitute for the original work in any way, and takes very little of the work.
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.
Yes. The license itself is really just one sentence long, and states explicitly that this is allowed. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
I presume the input is text: "my original text" is assumed to mean you wrote (created) the text. That means that you hold the copyright to the text, and only you can authorize a derivative work (such as a synthesized recording). Therefore, you hold the copyright to the recordings as well. The crucial consideration governing that right is that you "created" the work, meaning that there is a modicum of creativity. However, if you did not create the text and your only function is to host an automatic process where users can create a synthesized recording, then whoever created the text has the right to the text and derivative works (i.e. the synthesized output). Automated processes like (unassisted) OCR or wav-to-mp3 conversion would not count as being "original", nor would automatic text-to-speech, so you don't gain copyright just from making an automatic work-creating tool available. On the assumption that the conversion involves a component of Chrome, you can use the service per the terms of service, though you cannot "reproduce, duplicate, copy, sell, trade or resell the Services". This might limit the extent to which you could make this conversion available to others, depending on how, exactly, you could do such a thing (does it duplicate the service?). As they say, Google owns all legal right to the Services, but Google obtains no right from you for any content created through their service. There is no restriction in the TOS against using the service for commercial purposes. Even if there were, that would not assign copyright in the recording to anyone else, it would just mean they could sue you for violating the TOS.
Germany may be different, however in the United States this would be considered work-for-hire and the employer would be the rightful owner of the source code. Regardless of jurisdiction, and from a more practical point of view, you are better off not having a copy of the source code. Using it as reference or example in the future could easily turn into (unintentional) copyright infringement. If, in the future, you write code you would like to be able to freely keep and reuse in any project, make sure the owner/employer licenses it using something like the BSD, MIT, or ISC license.
As the copyright holder you are free to license your work however you want. The fact that you have licensed your work under a CC license to one group does not prevent you from licensing it to someone else under a different license with different terms. This is true even if the CC license could apply to this other person. The CC license doesn't restrict what you can do with your own work. It only restricts what other people can do when they choose to use your work under the terms of the CC license.