Hello. I've just noticed trunk revision 6172. It deals with license texts in various code files. It was probably inspired by my mentioning of the licensecheck utility in the merge proposal review guidelines I posted today, and the general remark about acceptable licenses in _new_ code.
The majority of changes is not controversial and consists of updating the address of the Free Software Foundation in license headers. The problem is that the same revision __introduces__ a license text (the GNU GPL) to a number of files, mostly utility scripts, that have been license-less for quite some time. Please note that: - the only people who can release a file under a specific license are its author(s) - if a file is missing a license statement, the proper way to deal with that is to ask the author(s) to provide one, not slap on a license text. An acceptable compromise is to leave the file as it was, instead of assuming a license - a "copyright (c)" statement is useless without an year of creation and/or author - it's a bit... strange to put "copyright (c) 2013" on a file that has existed at least since 2007 in version control BM ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Stellarium-pubdevel mailing list Stellarium-pubdevel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
