On Tue, Mar 25, 2003 at 08:25:04PM -0700, Andrew Jorgensen wrote:
Michael Halcrow wrote:
There was some suggestion that you could let BYU own the copyright and still license it under the GPL (maybe), but I don't think that a professor could /advocate/ open sourcing a project done for school. It's unfortunate, but true, that there are legal implications.
So, let me get this straight... I *PAY* to take a class at a university, conceive of a project, use my own equipment to develop the software, use my own time and efforts to write it, and then my school claims to own the copyright for the software I write? I don't think
There's something in the IP policy that says that student coursework is generally not owned by BYU. Unfortunately for many of us that all changes if you're working at BYU at the time (custodial included). This is much the same as what you'll have to put up with in "the real world." Many companies (most?) have policies like this. There are many horror stories about this. Donate to the EFF?
so. My school doesn't own me. If the school funds the development of the software by paying me to write the software, I can understand that. If it's on my own time, on my own equipment, whether it is in conjunction with a class project or not, as far as I'm concerned, *I* am the one who owns the copyright, not BYU.
I know the guy in charge of tech transfer, and it's not hard to find people to talk to if you're willing to wade through their secretaries. I'm going to talk to someone about this and find out what BYU's stance really is.
I will not release code under the BSD license, so some other entity can take advantage of my work without returning it to the community; GPL is the only acceptable license for code that I write and release to the community, to ensure that the community receives maximum benefit from my work.
I won't disagree with you.
smime.p7s
Description: S/MIME Cryptographic Signature
