Tag Archive
amateur astronomy awk bash b[e] supergiant cartoon conference convert evolved star exoplanet fedora figaro fits fun galaxy iraf large magellanic cloud latex linux lmc machine learning magellanic clouds massive star matplotlib meteor mypaper paper peblo photometry planet pro-am pyraf python red supergiant scisoft skinakas observatory small magellanic cloud smc spectroscopy starlink talk ubuntu university of crete video x-ray yellow hypergiant
About licensing
Stumbled upon the various different licenses I though to write down some conclusions (if I really got into any…).
A nice comparison table of free software licenses is given in the Wikipedia where it is easily to see which licenses allow: (i) the link with other licenses and (ii) releasing under different license. So, in this table it is obvious that the GNU General Public License does not allow any change or link in order to preserve the license through the works, while the GNU Lesser General Public License allows only the link with other licenses. But that’s not the same with the permissive licenses like BSD or MIT. That means that these licenses (including the Python’s license) allow both link and distribution with other licenses, which makes them not compatible with copyleft licenses (with the best representative the GNU GPL).
Moreover, IRAF‘s license (Wikipedia / IRAF) is provided free of charge but under various licenses (MIT and some non-free parts). So its license is not really clarified and certainly not compatible with GNU GPL. Although Python provides the opportunity to connect with other licenses and redistribute code under GNU GPL the use of IRAF’s tasks does not allowed it as a whole package. So, the license for code that combines these packages cannot implemented under a copyleft license (like GNU CPL). It seems that a more suitable license would be a Modified BSD (like PyRAF’s license).
[edited on Dec 16th:] Actually since Python and MIT’s license of IRAF (& PyRAF) allow license changes, then scripts that use these tools can have whatever license the author wants, since Python and IRAF/PyRAF are distributed separately.
Thanks to Jann K for clarifying a little more what I have written before!