People who code: we want your input. Take the Survey
9

all his app is copyrighted This statement is almost certainly true, in the sense that probably all the code is covered by copyright protection and that one or multiple persons or companies hold those copyrights. As soon as you write something down and it meets a very simple test of creativity (there is more than one way to write it), then what you wrote is ...


5

You posit that A writes code and publishes it, then B takes it, makes copyrightable modifications to it, and republishes the resulting work. You ask what the copyright position in this resulting work is, and whether such activity is lawful. The result would indeed be copyrighted, as the Berne Convention requires, but the rights would vest in more than one ...


4

If the file is entirely your own work, without dependencies that aren't public domain, it's technically not required to preserve anything in the minified version. However, keeping a copyright notice in won't hurt anything, and is probably a good idea. If the file contains work from others, you are bound by whatever license you received that work under. This ...


4

Yes, you should keep copyright and license notices in minified files as well. In case you haven't written the code entirely by yourself but have also included code under open source licenses (like MIT or BSD), you are legally required to preserve such notices. As an alternative to keeping the notices within the files, you could also have a separate page that ...


3

Is my understanding correct? Yes, your understanding is correct that you can use libraries under those licenses in your monetized app. And do I need to perform any extra procedures to be fully compliant with these licenses? The screenshots below mention the "license and copyright notice" and "state changes" conditions. It is not really ...


2

It is good to have a copyright notice next to the license notice in your files. That give the users of your code some indication who the rights holders are. A properly formatted copyright notice has the format Copyright <year> <rights holder> where the year is a list or range of years in which (copyright-significant) changes to the file were ...


1

Placing a note in README or such that "directory xyz is under licence BLA-4.1.2, see xyz/BLA.txt for details" should be plenty (and copyright notes in the different files, as appropiate). What exactly is the translation? Add translations for messages and documentation? Rework so that messages are in English? Work to use something like GNU's gettext(...


Only top voted, non community-wiki answers of a minimum length are eligible