Tim, All,
When we last did the build scripts for trinity, Tim suggested that each build script contain reference to the GPL. I had submitted all build scripts for Arch with:
# # All modifications and uses of this file are licensed under # the software for which this file was made for, should the software # be under an Open Source License, at least version 1.9, defined # by the Open Source Initiative. In other cases, this file is automatically # released to the Public Domain. #
I've noticed the current scripts omit the statement. For submitting/updating scripts, is this something that is wanted? If so, does it need to be updated in any way? It could be more readable legally.
Tim, All,
When we last did the build scripts for trinity, Tim suggested that each build script contain reference to the GPL. I had submitted all build scripts for Arch with:
# # All modifications and uses of this file are licensed under # the software for which this file was made for, should the software # be under an Open Source License, at least version 1.9, defined # by the Open Source Initiative. In other cases, this file is automatically # released to the Public Domain. #
I've noticed the current scripts omit the statement. For submitting/updating scripts, is this something that is wanted? If so, does it need to be updated in any way? It could be more readable legally.
-- David C. Rankin, J.D.,P.E.
The license agreement for anyone who has commit access states that if a license block is not included on a file, the file is placed into the public domain when it is uploaded to the TDE GIT repository.
Feel free to clean up any legal statements on the files in GIT; this is not my area of expertise. ;-)
Tim
-
David C. Rankin -
Timothy Pearson