-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlicense_notes.txt
16 lines (10 loc) · 1.71 KB
/
license_notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
License notes
To easily comply with points 1, 2 and 3, distribute license.txt (you can change the name if you need to) just add the following text (or something similar) to your README or About dialog:
This software uses ThomasJepp.SaintsRow.
For more information about ThomasJepp.SaintsRow, see: https://github.com/tomjepp/ThomasJepp.SaintsRow.
The license for ThomasJepp.SaintsRow is included with this program in the file "ThomasJepp.SaintsRow license.txt".
Point 4 means that if you modify the ThomasJepp.SaintsRow library or the included applications, you must make it clear to people who download your modified versions that they are not the original versions and that you have modified them. You must also still comply with points 1, 2, 3 and 5.
To comply with point 5, if you have changed the source code of the ThomasJepp.SaintsRow library or any included applications as part of your release, you must also release the source code to those changes. This license continues to apply to those changes.
Point 5 does *not* apply to third-party software that merely references or links to an unmodified version of the ThomasJepp.SaintsRow library.
For instance: if you create a program that uses an unmodified version of ThomasJepp.SaintsRow.dll you don't have to release the source code of that program. You do still have to comply with points 1, 2 and 3.
If you create a program that uses a *modified* version of ThomasJepp.SaintsRow.dll you don't have to release the source code of that program, but you DO have to release the source code to your modified version of ThomasJepp.SaintsRow.dll. You still have to comply with points 1, 2 and 3, and you must make it clear that the source code to ThomasJepp.SaintsRow.dll has been modified.