Slashdot Mirror
Losing My Software Rights?
vintagepc writes "Having written a piece of software as part of my research employment, I now face (and will later face again, with other software I've developed), the issue of intellectual property rights. The legal department stated that if I was paid by the University to produce the software, the University would own all rights to it. This is supposedly black and white, not a gray area. However, I was hired as a research student, not directly by the University, and also via a research award (NSERC). Furthermore, it turns out that faculty members here, in fact, retain their intellectual rights to any software they write. At this point, I can still back out, since I have not explicitly agreed to the conditions, but this decision must be made soon. So, I turn to the Slashdot community to ask: Are they allowed to completely strip my rights to the software? If anyone has had any similar experiences, then what was the outcome? Additionally, is this a normal action, or do I have some maneuvering room?"
All you can do is negotiate. What you sign away is law.
Support my political activism on Patreon.
get it in writing.
God, schmod. I want my monkey man!
Talk to a fucking lawyer.
Or back down.
Do what all the other cool grad students who are changing the world are doing and open source it!
These are all very good questions, but you should not be asking Slashdot, you should be asking your attorney. Not having one is no excuse. For something like this, with the ramifications being as big (and permanent) as they are, you need to get one.
If you produce it in your free time and it isn't related to your work, then the company is unfairly trying to take your work.
If you are simply doing what they ask you to you are doing your job.
The question here is, did the University get the grant or did you? Would you have been able to get the grant if you weren't at the university because of the credentials of the institution? Were you hired as a research associate into an existing area that is managed by someone else?
If so, put your ego aside and accept that you are growing as a professional.
Now if you have the credo to be a principal researcher then find an institution that will provide you the room you want to have more ownership of your IP.
Too often we think we are the only ones who can do what we do when in reality there are many talented developers out there.
We have to accept as a profession that we are driven by business needs at some point.
According to NSERC no (NSERC Grant Award IP Policy) Specifically, "The Agencies do not retain or claim any ownership of, or exploitation rights to, intellectual property or copyright developed with grant funds. These rights are owned by the Institution and/or by the inventor." You need to check with policies you have in place with your institution. Many universities do claim IP and it is usually addressed in the student handbook, or somewhere in university policy. Look at stanford they own google's page rank patend.
Trying to install linux on my microwave, but keep getting a kernel panic...
> Are they allowed to completely strip my rights to the software?
Um, they are allowed to ask for anything they want (that is not illegal) in a contract, and you are allowed to either sign it or not. If you are paid by them and write the software on their time and sign a contract saying they own it, you don't HAVE any rights for them to "strip".
You are also allowed to negotiate, although I wouldn't hold my breath...
Yes they can take away all your rights to the software, but no you shouldn't allow them to do it.
First, I've been a grad student at one university and a professor at another, and I've always avoided signing these agreements. It turns out that if you just avoid signing them and aren't too confrontational about it, you can easily slip through the cracks.
Second, you should talk to your professors and see if they will allow you to develop software publicly under some irrevocable license like the GPL or BSD. With revision control software like git, it's pretty easy just to throw the repository on your home page and make everything you do available to the world (including yourself) on a royalty-free basis. Import some GPL-ed third-party code into your project for extra protection.
Finally, sometimes professors do try to exploit grad students for the purposes of launching their startup companies, etc. If you feel that you are going to be in a position where your research is compromised (for instance because your results are no longer reproducible by the community), then you should find another research group to work with!
You're in Canada, right? There's a reasonable chance that your university has a law department. Visit and find someone there who can answer your question based on their expertise in IP and contract law. After all, you wouldn't ask Slashdotters about excising intramedullary spinal cord tumors, because most of us don't have a firm background in neurology. What makes you think we're any more qualified to provide a meaningful legal opinion in your jurisdiction?
As a research student you are "hired" by the university. End of discussion. Your tuition and stipend are paid to you from research grant money that is owned by the university/professor.
Faculty members at some universities may retain their intellectual property rights. This is because there is a separate contract negotiation that takes place between faculty and universities. You [the student] are not part of this agreement.
At every PhD institution I know of, Teaching Assistants and Research Assistants are employees. In fact, third-rate employees. You get no health benefits, you get no retirement benefits and you get no intellectual property benefits. Basically, you get no benefit other than an effective scholarship.
You're screwed. They own your software. It is black and white.
I will never live for sake of another man, nor ask another man to live for mine.
Of course, this is slashdot, and IANAL. But having a little experience, this is my take on things:
If your creative duties were supervised by the University - that is, they told you what program to write, and how to write it, and your duties included writing code - your chances of winning a court case in your favor are very small.
Teachers and professors are in a different category because, generally speaking, they are not producing a "work for hire" - but are instead hired for their role as a teacher or lecturer. The University does not retain creative control over their work; does not proscribe what is produced; and does not require them to produce code as part of their duties. That is, the code is incidental to their work. Thus, they can often retain copyright of the code they produce.
From your description, this does not sound like the case at all. Instead, from your terse description, I, and a court, could reasonably conclude that you were hired to write code (among other duties), and hence, your employer owns the rights to it.
Unless you have a well-documented case to the contrary, it would be safest to assume your University's legal department is correct.
The society for a thought-free internet welcomes you.
several posts say talk to an attorney, in detail, when they can READ your contract, and they're right. IANAL. However, since this is the Internet, I want to take this opportunity to point out several substantial flaws in your submission.
0. Posting here and not getting an attorney. Fail.
1. A purely ownership and non-personal right like this, it's very unlikely there's any prohibition against you signing it away. (Unlike, e.g. some noncompetes which are SOMETIMES unenforceable.) Fail.
2. If you sign this when you obviously (and demonstrably - you posted it here!) thought they intended it to mean you had no ownership, the courts will not look kindly on you turning around and saying you don't believe that. That's called 'bad faith'. Even if the contract WAS weak, if it's clear that both parties understood the same intent, usually that's what happens.
And there's a good reason for that. Knowingly signing that when you clearly believe they mean that if you don't intend to carry it through makes you a liar.
Fail.
3. That the faculty, who have a totally different contract, get to keep their work has no bearing on your contract. Fail.
4. The faculty don't even meet the standard you set out - which is 'if you're paid TO develop software' - which they aren't. They're paid to uphold the educational mission of the institution and do their research. The actual software is (at least contractually) secondary.
I'm not telling you not to take the job -
I only see two glimmers of hope here:
- If the UNIVERSITY's contract with NSERC specifies something different, you count point that out to them.
- I don't know if this is in your goalset, but depending on the U, if you WANTED to open source your project (whatever license) the U may allow that - and you MIGHT be able to get them to approve allowing that BEFORE hiring you. YOU will still own none of it. They'll own all the rights to sell a closed source version, etc., and they could un-open-source their future versions. (Which, if you were GPL, no one ELSE could legally do) But they can't exactly 'unlicense' the code they agreed to release.
Looking for freelance Actionscript (Flash/Flex) or ColdFusion work and/or freelance developers. Email me, put Slashdot
Two things:
First: Lawyers are expensive. Very expensive. Most working people can't afford them very well, much less research assistants or students.
Second: The average city isn't exactly crawling with competent Intellectual Property lawyers. I would say the typical lawyer would say "huh" and maybe get you some boilerplate legal templates to use, and not really help you much beyond that.
I say stand your ground if you have agreed to nothing so far. Losing you completely gains nothing for them, they will cave in. I've never found it hard to allow organizations or institutions to allow me to keep rights to my software, as long as they get to use it.
Love many, trust a few, do harm to none.
Universities are non-profits
You seriously believe that? They only get taxed like that but for some reason they make a lot of "Excess-Revenue". Which will go to a new football field or a building. Then they will still think that after paying 30k in tuition that you owe them and you should donate money to them.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Do you believe in imaginary property or something? Information wants to be free, you know... New York County Lawyer will be helping your University (or whoever else gets a hold of your code) to dodge any and all legal challenges you may pursue — you wouldn't even know, who they are, because the University will bravely refuse your subpoenas against John (and Jane) Does.
In Soviet Washington the swamp drains you.
* Dissy puts on the lawyers hat
As your attorney, I advise you to rent a very fast car with no top. And you'll need the cocaine. Tape recorder for special music. Acapulco shirts. Get the hell out of L.A. for at least 48 hours.
* Dissy takes off the lawyer hat
* Dissy puts on his robe and wizards hat
Er wait...
I just went through the NSERC process for a PGS-D (PhD) scholarship and I was made aware of the different types of NSERC applications. First of all are you undergraduate or graduate? Do you work with a company as well? Was this developed as part of a thesis? Were you funded through some other source?
If you are a graduate with a typical NSERC then you are entitled to the rights of your software. However, the University can publish and distribute the software (not usually code) as they see fit. If you have another funding source (internal? dept? faculty? provincial?) then you may loose the right but not because of nserc. Some jokers say get a lawyer etc.... ya right easier said than done considering you are likely a poor sap. You are better off contacting your student union and getting your graduate student association involved. Get someone with a big mouth that will threaten to go on TV about it. Also go to the heads of department and talk about it. What does your supervisor say? Are you in a lab? It is odd that you post this in the end of the first semester if you were undergrad so I'd say you are graduate. Good luck.
You must have signed something when you started the job... either for the University or for the company/agency you're working for that is under contract to the university. You should read it... as it's quite likely binding. If it states that they own the rights to whatever you produce while employed by them... it's _quite_ likely to hold up should it come to that.
This is somewhat like asking "Can I tell my wife to take a hike and give her nothing?" after you've been married for 45 years. The answer is more than likely "no." You should have known what you were getting into at the outset... after doing all the work subject to an employment contract isn't the best time to ask what your rights are or try to negotiate or open-source something. You can ask, but if they say no, that's pretty much the end of it. Unless you decide to say "screw it" and then steal or open-source the code... which could open you to criminal and civil liabilities.
These are all very good questions, but you should not be asking Slashdot, you should be asking your attorney. Not having one is no excuse. For something like this, with the ramifications being as big (and permanent) as they are, you need to get one.
He should get an attorney, but there's nothing wrong with asking Slashdot first. A good lawyer will happily charge you $250 an hour or more to teach you about very basic stuff, but that's a waste of money and time.
If somebody's charging you $4 a minute, it makes sense go in prepared. And how do you get prepared? Reading about the fundamentals, getting advice from people with similar experiences, making lists of questions to ask, figuring out what to tell the lawyer, and talking about your concerns with peers. And where can he do all of that? Right here. And as a bonus, a bunch of people who will be able to use the knowledge one day will get it for free.
Can anyone name any other occupation where people have such an exaggerated feeling of ownership over what they produce?
Even if you think you own this software, if it's a good idea, people will copy it, or steal the design, and never pay you a dime.
Do it. Do a great job. When the time is right, move on to the next great thing.
Canadian law is very different from US, particularly around work-for-hire and you really need to talk with a local legal-aid office or lawyer.
DISCLAIMER: By reading this post you agree to Great Grandparent post.
A bullet may have your name on it but splash damage is addressed "To whom it may concern."
I paid for that code you wrote it should actually belong to
the public not you or the university.
Got Code?
Comment removed based on user account deletion
NSERC's web USRA web page says:
Who owns the rights to intellectual property from research?
NSERC does not retain or claim any ownership of, or exploitation rights to, the intellectual property resulting from your NSERC funding. However, since NSERC's role includes promoting the use of knowledge to build a strong national economy and improving the quality of life of Canadians, every effort should be made to have the results of NSERC-funded research exploited in Canada, for the benefit of Canadians. You are encouraged to discuss intellectual property rights with all parties and organizations involved in the research.
My read: if the University decides to keep the IP, they can. In fact elsewhere, the Industrial USRA documentation explicitly gives the employing company the IP.
From what you said, I understand that your University's policy depends on if you were acting as an employee or as a student. So, what were you? Did they/will they pay you as a T4 (withheld tax) or a T4A (no withholding). If they payed you with a T4A, they were claiming you were a student, not an employee.
fwiw, I hire my USRAs as T4A
well, obviously they can't claim rights to code that they didn't fund the development of. that doesn't seem like what the University's policy is.
the lesson here isn't to not sign anything you don't agree with (that's just common sense), but rather don't do public research if you're not comfortable with doing public research.
the NSERC seems to be a government institution, so all research that they fund is by definition public research. naturally, academic research is going to remain in the control of the academic institution where it was conducted. this is done in order to keep publicly funded research free and open to everyone in the spirit of academic openness and to facilitate scientific collaboration. you can't accept government funding and then turn around and decide you don't want anyone else to have access to your research. it's not fair to taxpayers for them to foot the bill for proprietary research that is not made available to the public.
in the context of software development, i would expect the university to release the source code under some kind of open source license. if it's a BSD license then the developer who wrote the code should still be able to commercialize his software if he wants to. he has every right to make money off of his code. he just doesn't have the right to accept research funding from taxpayers and then renege on the agreement to make the research/source code public. besides, it would really hinder scientific/technological progress if all public/academic research were tied down with patents and copyrights. waiting 15-20 years after a scientific breakthrough is made before another researcher can build upon it is just impractical.
it's really no different from being paid to do software development for a commercial company. if your employer pays you to develop the software, you can't expect to retain the rights to the code you just sold to them. i mean, what are they paying you for?
I've run into a number of bad contracts and have been unable to afford a lawyer, and was willing to accept pretty much anything just to get working again. All of the flaws you mention are things that have come back to bite me in the ass (well, except for the asking slashdot part).
I've learned that keeping any rights to commercially developed software is unlikely unless you have some kind of weight in the business community. Learning what that really means sucks hard, and that's why I believe that Free Software is ultimately better -- it's not produced in software sweatshops, where the true genius will never get compensated, either in ego, or in money for the full value of their work. Of course, that's why I no longer work in IT. There's plenty of money someplace else, and you'll be treated like a person and not some code creating machine.
"Please describe the scientific nature of the 'whammy'" - Agent Scully
Wolfram, however, had other ideas.
There was a protracted, expensive legal battle, in which Wolfram argued that -- despite the overt cultural backdrop of sharing knowledge -- since he didn't expressly sign his rights away, it was all his, and Caltech could go pound salt. It ended up with Wolfram resigning from the physics department and taking all his intellectual "property" rights with him.
And that's why, to this day, it costs $2500 to buy a copy of Mathematica. And also why that clause is in your contract with the University.
Schwab
Editor, A1-AAA AmeriCaptions
It sounds like adults are required to use language rigidly, express no emotion, and generally not have very much fun.
How about we pretend to be rational instead?
The researcher is paid to research new IP. That is their job. Therefore any new research belongs to the employer. The cleaner is employed to clean. That is their job. Therefore any new research belongs to them.
Not that difficult to understand.
Something that worked well for me in similar situations was this:
Request that the software is released under an open license (in my case, the BSD license), a request that an academic organisation is unlikely to refuse. There is no need to actually give anyone else a copy of the source. When you leave the university, you have full rights as bestowed by the license even if the copyright on the source belongs to "Regents of the University of California", or whoever. Problem solved.
Having said that, if your software is anything like typical academic software (my own included) then the source code will be dreadful and worth next to nothing. It is the ideas encoded in the code that are valuable - and the ownership of those is a whole other argument.
The university may or may not have certain rights. Whether you agree or not doesn't matter, they have whatever rights they have and they don't have whatever rights they don't have. There is no way they can force you to sign over any rights. Either they have these rights, then they don't need you to sign them over. Or they don't have the rights, then you are under no obligation to sign them over. (BTW I was told that in US law, you can't sign over copyrights that don't exist yet. Like the copyright for a book that you are going to write, or the copyright that you are going to develop. For the simple reason that the copyright doesn't exist. The signing over must happen when the copyright actually exists).
Having been through this, there are three likely outcomes in decreasing probability.
Assuming the latter greatness, in my experience the likelihood of the university patenting your algorithm is vanishingly small. But if they do, great! You are a young researcher with a patent. Chances are the Univeristy will profit share ( in theory at least. At one institution the patent office made just enough money to, you guessed it, fund the patent office ). If they don't, you are a young researcher with a patent. Sounds like graduate school gave your career a boost. Ten years down the line I'd rather have a patent under my name than the software I wrote.
In either case, publish. Publishing is the GPL of the academic community. I have had greater success making my source code GPL when I talked to my principal investigator about supplementary materials for publications than at any other time. If this fails at least you'll know whether the algorithm is patented before publication, if it isn't, you will be able to use the algorithm in the future free and clear. If it is, I'll repeat myself: you are a young researcher with a patent AND a publication.
Why are so many /. readers so frightened of work-for-hire arrangements? Copyright is not a birthright. You do not automatically own the rights to things you create.
You are quite right to recognize and debate the issue. But you start from a point of assuming you should retain those rights. Welcome to employment. Usually, you don't retain the rights to things you're paid to create. That the rules are different for professors is irrelevant.
You have the basic equation right -- the deal is what you agree to -- but you seem to be overlooking WHY people are paid to create software. People pay you to create software because (by doing so) the value accrues to them.
Work-for-hire is neither bad nor unfair.
http://drteknikal.blogspot.com/
My university owns code I wrote for some projects, which is why I got it written into the grant application that any code developed on those projects would be released under a BSD license. This means that it doesn't really matter who owns it - I can use it in any project I want to in the future.
I am TheRaven on Soylent News
Lesson 2: you're already into this deal, too late to renegotiate. If you move on to "professor" status, you'll have justification for why you want rights to all software you develop - then.
Try actually reading the law instead of asking a biased bunch of people on a web site. And, if you don't like the conditions, don't take the position.
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
While I agree with the majority of you post...you have me completely baffled at your taxpayer comment. What tax system would you propose we use that doesn't 'hurt ourselves'? And with Obama coming into office...I don't think the system in place will be very friendly to "the rich"..who already pay a disproportionate amount of the US tax.
Anyway, please elaborate...
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
While I agree with the majority of you post...you have me completely baffled at your taxpayer comment. What tax system would you propose we use that doesn't 'hurt ourselves'?
He's saying that the lower and middle class vote for and generally support tax reforms that would only benefit them if they were considerably richer than they currently are, and actually hurt them at their current income level.
Ask any blue collar democrat or bible-belt small town republican or white-collar pointy-haired-middle-manager middle-class joe average whether he thinks we should scrap progressive tax and switch to a flat tax. The number that think this would be a good idea is shocking, given than it will only reduce the tax load on people wealthier than them, and shift that load onto them.
Either these people are categorically bad at math (which is probably true), have delusions about how wealthy they actually are (everybody thinks they are "upper middle class"), or have unrealistic expecations about how wealthy they will be in the near future).
In truth its probably all of the above.
And with Obama coming into office...I don't think the system in place will be very friendly to "the rich"..who already pay a disproportionate amount of the US tax.
The vote for Obama vs McCain was a lot more than simply picking a tax plan, so we can't and shouldn't really equate voting for Obama with understanding how tax reforms will affect them.