If I remember correctly much of my work at the university involved using GPL'd software. I don't mean using gcc to compile the code, but sometimes taking source code (in parts or in whole) and embedding it in the software that I was writing.
If this is the case, then doesn't my code also become GPL'd? I just re-read the GNU GPL and noticed that the last clause states that the author must write to the original author of the software for permission. What if the author refuses to release the code for commercial purposes?
If it is the case that the code becomes GPL'd, is the university obligated to rip out the GPL'd source code before licensing the software? This could pose a problem (legal or moral) for those that want to release the software to make money. Can this argument be used to keep the software in the public domain?
Slashdot Mirror
If I remember correctly much of my work at the university involved using GPL'd software. I don't mean using gcc to compile the code, but sometimes taking source code (in parts or in whole) and embedding it in the software that I was writing. If this is the case, then doesn't my code also become GPL'd? I just re-read the GNU GPL and noticed that the last clause states that the author must write to the original author of the software for permission. What if the author refuses to release the code for commercial purposes? If it is the case that the code becomes GPL'd, is the university obligated to rip out the GPL'd source code before licensing the software? This could pose a problem (legal or moral) for those that want to release the software to make money. Can this argument be used to keep the software in the public domain?