1

After a user installs my application, where in the app's install directory should I place information regarding 3rd party software (e.g. FOSS) licenses? Should I just append it to my EULA? Is there some sort of convention or standard that I should following to make it easily scan-able by license detection scripts?

  • 1
    What scripts? Why should you care? It's your software, put it where you like. – david.pfx Aug 11 '14 at 4:01
3

You probably ought to do both - place it in your EULA as well as providing a LICENSE.txt (or equivalent) file. That way, your end users are aware of the licenses prior to accepting the terms of your license as well as being able to go back and reference the licenses later.

Most packages place the LICENSE.txt file in the application root folder, but to my knowledge there's nothing preventing you from putting it in a logical place. If there's a convention, it's to place the file in the root of the application folder.

If you have a large number of licenses, then you may want to create a folder underneath your application called Licenses and list all of the applicable licenses.

| improve this answer | |
1

If you look at other software that makes use of FOSS you'll usually find the information available through the about option in the menu. For an example have a look at the Chrome or Firefox about screen/page.

| improve this answer | |
  • 1
    What if my app doesn't have a UI (e.g. command line program/server)? – Darwyn Aug 11 '14 at 0:47
  • 2
    @Darwyn: Then you could reproduce the licenses if the app is started with an appropriate commandline switch (e.g. --license), similar to the common --version switch. – Bart van Ingen Schenau Aug 11 '14 at 6:34

Not the answer you're looking for? Browse other questions tagged or ask your own question.