Hi,
I asked for proper licensing on a project I was going to package and the question came up, whether config files should have a license header.
The ticket at their issue tracker is here: https://sourceforge.net/tracker/index.php?func=detail&aid=2869635&gr...
The config file can be accessed here: http://rcracki.svn.sourceforge.net/viewvc/rcracki/rcracki_mt/rcracki_mt.ini?...
What is your advise here?
Regards Till
On 05/24/2010 07:30 AM, Till Maas wrote:
Hi,
I asked for proper licensing on a project I was going to package and the question came up, whether config files should have a license header.
The ticket at their issue tracker is here: https://sourceforge.net/tracker/index.php?func=detail&aid=2869635&gr...
The config file can be accessed here: http://rcracki.svn.sourceforge.net/viewvc/rcracki/rcracki_mt/rcracki_mt.ini?...
What is your advise here?
In general, I would not consider config files to be copyrightable, unless they did something complicated or unique. In the example above, IMHO, neither is true, so it is fine to not have a license header.
Rule of thumb here is to ask upstream if they feel it that the config file is a copyrightable work. If yes, then it needs a license. If no, then it is fine to not have one.
~spot
-
Till Maas -
Tom Callaway