Slashdot Mirror
Can Employer Usurp Copyright On GPL-Derived Work?
An anonymous reader writes "I am a recent graduate, and I've been working on my own on a project that uses GPL-licensed libraries. Later a university department hired me, on a part-time basis, to develop this project into a solution that they needed. The project's size increased over time and soliciting help from the open source community seemed like the obvious thing to do. However, when I suggested this, my boss was not interested, and it was made clear to me that the department's position was that copyright of the whole thing belonged to them. Indeed, by default work created for an employer belongs to the employer, so I may have gotten myself in the same trap discussed here years ago. Even though I want to release my code to the public I don't know whether I have the legal right to do so. I did start the project on my own. And, since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project. Also, the whole project relies on GPL libraries, and without those libraries it would be useless. Can they still claim copyright and prevent me from publishing the source code even though it is derived from GPL software?" Some early commenters on the submission pointed out that it matters whether the libraries were licensed under the LGPL vs. the GPL.
The employer may be committing a GPL violation. You should bring that up with your employer and also inform them that it can cause a lot of badwill.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
All the work you did for them belongs to them. However, they may not be legally entitled to use it how they'd like. If it's based on GPL code and they don't want to release the whole thing under the GPL, they'll need to rewrite the sections under the GPL before they can have their way with it.
Let's be clear. You have no rights to do whatever you want with the code you wrote for them.
A lawyer will be able to help you.
What you need to take away from all this is the same simple advice Homer gave Bart. "Never try"
All you gain from trying to make this software GPL is a lot of heartache and lost time. In the worst case, you can lose a lot of money to lawyers and ultimately the whole source base and copyright.
Was it worth it?
Working for a university on a part-time basis.
Seriously, how can they lay claim to work performed on one's own time if it's part-time? Besides; don't tell people what you're doing. Post it online without using your legal name or informing your employer. If by sheer coincidence they find it, it's already too late.
Even though I want to release my code to the public I don't know whether I have the legal right to do so.
That sounds like "you need to talk to a lawyer" material.
IANAL, but my guess is that if it's in your contract, you'll probably need to demonstrate that you weren't aware of that at the time you signed the contract in order to keep copyright (or control of licensing) on your work. However, given that they hired you to develop a GPL product, it seems silly that any extended code produced is not also GPL licensed.
Ask me about repetitive DNA
HAD you done this on your OWN TIME using your OWN RESOURCES then this isn't part of the "temporary employment" you were in.
Sadly, you didn't. While you included open-source projects to be successful faster... the end result has a copyright owned by your employer.
THEY CANNOT use this without properly administering the rights of the open-source projects they use. These are license-dependent... and I'm guessing by your email that some? or all? are GPL.
It's a thorny issue, but there is an EASY ANSWER and a HARD QUESTION.
EASY ANSWER: Your university can contribute YOUR contributions under the GPL and open-source it.
HARD QUESTION: Which licenses of the software you used have conditions which PREVENT that software from being used in a software program/package with a conflicting license, and which NON-conflicting license would your "temporary employers" be willing to live by so that they can continue to use it.
Otherwise, your "temporary employers" are in potential violation of the licenses of the software included in the package they are using.
Nobody said this was simple.
E
I'd also like to note that I work for a large company that knowingly pays me to do exactly this all day. I write proprietary software using GPL libraries and such all day. We just don't distribute it.
What does your contract of employment say ? Does it say anything about copyright ? Did you read it before you signed ?
Do you want to continue to work for someone who attempts to steal your property ?
Gah. Every time this kind of story gets posted to Slashdot we go through the same conversations.
You entered into the employment and provided them with the code base, they most likely have a claim to it.
All the work you did for them is work-for-hire, they own it.
There's nothing wrong with using GPL libraries for internal proprietary software.. the GPL is a *distribution* license, you haven't said anything about distribution so I'm assuming they're not distributing it, in which case the GPL is irrelevant.
There's lots and lots of source code in the world, plenty of it is free for you to hack on, move on.
How we know is more important than what we know.
If your project is only used internally, i.e. if it's not distributed, the GPLedness of the libraries you're using plays no role. If you're not distributing, the GPL places no restrictions whatsoever on what you do with the libraries. Now, since you started the project before getting paid to do so, it might be the case that the step where you so to say 'gave' it to the university counts as distribution, and then there would be no alternative to an at-least-GPL-Free license for your project, but that is something you should ask a lawyer about, not slashdot.
You could have just transferred the generic part of the code back home.
No one would have given a damn.
You could even truly claim, you worked on the stuff on your free time.
Somethings it is better for both parties to not talk about the issues.
Patents Drive Free Software as Hurricanes Drive Construction Industry
1. The code you wrote is probably your employer's.
2. The rest (the GPL code you used) is not.
This means that to distribute the code you wrote they would need to abide by the terms of the GPL or rewrite all of the GPL parts. I've heard solid arguments in both directions as to whether internal corporate use counts as distribution, but when talking internal only it may be a moot point if none of the other users care to request the source.
If binaries are being distributed outside your organization without the offer of source and such, it's a clear cut violation.
I used to get high on life, but I developed a tolerance. Now I need something stronger.
Before they can have their way with it, yes - but they can use it internally - just as I can make derived works from GPL code and use them however I want, myself or in my company. What I can't do is distribute it, sell it, etc... but if I base my employers in-house time-tracking system on some GPL code - the company is under no usage restriction whatsoever, and is under no obligation to share those changes with anyone else.
If they do want to distribute the stuff outside their organisation, they'll have to do so under the terms of the GPL - other than that scenario, they can do whatever they want internally.
Well, I'd say that there are multiple issues at hand. First of all, I'm pretty sure you can release the original code that was around before you started the job without any issues. If you were to release the additions and modifications you made after the employment started, that code is rightfully theirs. After all, they hired you to work on the project for them, they didn't contract you to make changes to your open source project.
Location is an issue that might come up with the GPL. Different countries would interpret the GPL differently. Just because it's been tested (more or less) in the states doesn't mean that it's been tested elsewhere. Given the time of your posting, I'm assuming you're somewhere outside of the U.S. and therefore the requirements of the GPL aren't necessarily clear.
I had a similar project at one point. I would never use the GPL as I believe in free software, so I use a modified BSD license. But when my employer decided they didn't want to continue making my code open, I wrote it over (it was only 15,000 lines, so it took a few weekends) and BSD'd it. It's still not as complete as the original, but it's functional enough to be useful to others now.
I recommend that you keep in mind that you work for your employer and if you feel your employer has violated your trust, you're welcome to leave. Additionally, if you violate their trust, they're welcome to release you from your agreement.
While it may be legally OK to release the code as GPL, it doesn't mean that your employer will agree with your decision and may decide that they'd prefer to work with someone who's more attuned to their wants and needs.
Right - which is perfectly acceptable.
It seems to me like the best way to avoid this sort of problem is to fork the original project and develop each version in parallel. (basically, keep development separate at all times, no code sharing between the two AT ALL after the fork, etc.) That way, you get to keep control over your version and the employer gets their own customized version with all the necessary proprietary enhancements. Sure, it's double the work, but everybody wins and gets what they want. Since the pre-existing GPL code in the proprietary version is also in the original version, (assuming you release it at some point) it probably wouldn't be a GPL violation, but I could be wrong.
"It is a denial of justice not to stretch out a helping hand to the fallen; that is the common right of humanity."
you own your work by default. This applies in the absence of any other agreement. If you are an employee, your employment contract may override this.
As said previously. anything you did on your employer's time using their resources is automaticaly copyrighted to them. You just work for them. Its a standard clause in all job contracts (you can hope yours did not have this specified and get away with it but i doubt it). Even a clerk all the spreadsheets i create to make MY job easier in matter of fact belong to the company. So if I miraculously discovered the cure for cancer using these spreadsheets I have to fortfeit that discovery and rights to the cure to the company that I work for. Sure we sell tyres but copyright rules in contracts are rules :)
However as far as the finished product being marketable and made profit from by your employer. That is a licencing issue on its own. Unless your employers's project fully commits to the GPL therefore keeping in line with the libraries licences then there should be no problem. If they want to branch off and breach the licences then they will have to remove the libraries that are in breach and wind another way to make it work. Or code their own.
Is your company distributing the binaries? If not, then they have no obligation to release the code. The GPL allows for modification and use within a company. It also never says that you must release your code freely on the internet, only that you must provide the source code to people who receive the binaries (if they ask for it). Once again, if your company isn't releasing binaries, they have no obligation.
Qxe4
According to your post, you were hired to work specifically on your project that you already started on your own. And you didn't think that ownership of the copyright would be a problem? It didn't occur to you that you needed to put that in your work contract?
Never bring any code you did at home to work without a written agreement that it belongs to you. Never even use an open-source software that you have contributed to.
Exact laws will vary from place to place which is why you need to get a lawyer, but in general it's very common that anything you do at work as well as anything work related you do at home belongs to your employer by default. If the line between work and your own projects becomes slightly blurry you need a written agreement to avoid any misunderstandings.
Yes, they absolutely own the copyright if the terms of your employment make the software you write on the job a work for hire (almost certainly the case unless you have an explicit exception in your employment contract).
They also cannot legally violate the GPL, but they will not even if they keep the source unpublished as long as they provide the source code with any binary distribution to another party.
The key here is that the GPL does not force you to distribute the source unless you distribute the binaries--and even then, you only need to provide the source to the people to whom you distributed the binaries.
They own the parts you wrote as an employee of theirs. They don't own the parts you wrote before being an employee of theirs - though have fun proving which parts are which...
No you can't publish the source code that they own or release it under the GPL. If they distribute it then they will need to in order to comply with the license of those libraries and of the portion you wrote before being their employee (though I can see an argument that since you used that code in your work for them you gave them a license to use it as they see fit, not sure if that would fly though). They might never distribute it though.
Yes, IANAL. Yes, trusting me for legal advice would be really stupid. Yes, those are just my opinions and understandings of how these things work.
I have no clue about the legal matter. However, if you're going to use your own code for employment, perhaps you should have taken a snapshot of it, and forked it?
Basically, whatever progress you did from the beginning belongs to the company while being paid on the clock. Your original code prior to employment belongs to you. But I seriously doubt you can go back and implement their code or process back into your original pre-fork code.
Life is not for the lazy.
I can't stress enough that the people who are suggesting talking to a lawyer are right.
Still, if I may hazard a guess, if you started the project before you were hired, and you have a standard relationship to your employer, there's a good chance that both you and your employer have a claim to the overall work, because it contains parts that you wrote on your own, and parts that you wrote as their employee. In this case, then yeah, you don't have ownership nor license to the parts that they own--and over time, those parts may have become inseparable from the original parts that are yours.
Are you adequate?
They can have it, and they have the right to own it.
However, if there's even a tiny little bit of GPL code involved, they'll have to release the software under the GPL to their users and provide them with a means to access the sources. That, however, doesn't mean they have to distribute it.
What kind of software are we talking about?
Can you prove that you started the project as a GPL project?
Even if you do, can you prove your employer knew it was a GPL project and would continue to be so?
Otherwise, you've created an unlicensable project. However, unless they distribute it (out side of their organization) they can keep using it as-is.
Say you work for a big company like Google or Goldman Sachs, and their magic secret program uses libraries and other code distributed under the GNU GPL license.
They are under no obligation to publish as they use the code internally and do not distribute anything.
What if an employee leaves the company and takes the code to the magic secret program with him? It uses GNU GPL licensed code, which grants _him_ a license to redistribute it, because he has a copy of the program already.
Banu
I thought the GPL only applied if you wanted to distribute your code, if you keep it in house (which your employer wanted to do?) Then it doesn't matter, but if the sold it to another party they would have to release the source code...
Are you an employee or a contractor? As an employee, the onus to fall on the right side of the GPL probably falls on your employer. But as a contractor, you yourself might be legally responsible for proper adherence to legal rules around the GPL. They are, after all, hiring you to know this stuff.
As for ownership of the code you created before you were hired: ask HR for a copy of your contract. There is probably a clause in there granting them specific rights, but they might not cover everything. They will definitely walk away with a license for everything and ownership of the code that you created for them, but they might not own the code that you created before you were hired.
And if they don't want you to, you can't published the extended version of the code. They definitely own that. And welcome to the new academia, where all knowledge is a secret to be jealously guarded.
The ______ Agenda
IANAL and this is not legal advice. If you really care about this, you should pay for advice from someone who is a lawyer.
That having been said...
Any software you produced for them for which you directly received W-2 wages belongs to them regardless of the terms of the GPL. It is entirely their choice whether or not to release it under the GPL. They may or may not be violating the GPL if they do not, however any damages from that violation will be monetary; they will not compel the software be released under the GPL.
Any software you produced during hours for which you did not receive a wage reported on an IRS form W-2 almost certainly still belongs to you, regardless of any papers you may have signed prior to writing it. They can't stop you from releasing it, but they can very likely release you from their employ and/or withdraw any other association you may have with them if you do.
A letter from GNU's lawyer to their lawyer can go a long way towards resolving the matter. Writing such letters is one of the reasons the GNU folks keep a lawyer in their employ. Avail yourself of the benefit.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
IANAL. If you care about this, get one.
Is the project really worth the trouble? Both you and the department failed to take the proper steps when you were hired. If you push the issue, they may fire you. You'd likely be blackballed from ever working for the university again. If the matter goes to court, you might scare off future employers down the line. Companies get very scared at the idea of someone introducing GPL poisoned (their frame of mind, not mine) code into their products without disclosing it.
Unless this is some amazingly cool and important project, it might be worth just taking it as a lesson learned. Don't ever use code that requires a license in your employers' software without documentation (and for something like this, keep an extra copy at home), especially if it's something you wrote. Cover Your Ass (CYA).
Down the line after you leave the university's employment you might go back to your code prior to be hired and release that but it still might be pushing it. You might be legally right but that doesn't mean that you can afford a Pyrrhic victory.
Did you begin the project as a student (prior to being paid), particularly in any way related to a class? If so, some universities attempt to apply IP ownership to students' work.
From my understanding of the GPL, you were fine creating software that relied on GPLed libraries and not GPLing it, provided you didn't release it. The place where it kicks in is when you distribute (say, to the university). At that point, you were obligated to put your code under the GPL. Did you do so and if so, was it formal?
Assuming that there's no student clause, you own the copyright on everything you wrote prior to them hiring you. They most likely own everything after that. For you to have legally distributed the initial code to them, it would have to have been GPLed. If it wasn't formally GPLed, they could try to put you on the hook for using unlicensed software in what you wrote for them.
They could GPL their portion of it and everything would be solved. Or they could eliminate all of the original code and still use the GPL library and be legal so long as they don't distribute it.
You can get a GPL program, put a Public Domain part, add a Very Closed Source code, compile the whole thing, and work with it. You can't distribute the result, but you can use the result.
You can make a GPL program, get hired to continue working on this program, add a Public Domain part, add a Very Closed Source code... and the result can be distributed only if you donated to your employer your work wen you was hired. So probably can't be distributed.
IANAL.
-Woof woof woof!
I'm part of the IANAL chorus, but I still have to say that I think these early commenters are wrong. GPL vs. LGPL is about licensing, i.e., permission granted by the copyright holders, directly or indirectly, to make use of a work in a given fashion. The main questions that the submitter has are about the actual copyright, i.e., who has the right to license or forbid others' use of the work.
Is it possible to do two distinct forks simultaneously, if you're the one doing the coding on both forks? Couldn't your employer argue that your contributions to the personal fork are inevitably derived from the code you wrote for their fork? And if you write your fork first, and then soon thereafter write the employer's fork, isn't the employer's fork inevitably derived from your personal fork, since you wrote both?
I think a single person simultaneously (or even with weeks) writing both forks is a bad idea, at least from a legal "who owns this code" standpoint.
" I've been working on my own on a project that uses GPL-licensed libraries."
" since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project.
assuming you licensed it under the GPLv3
No, you were not employed by them at the time and had licensed it under the GPL. When they hired you, no copyright is transfered. even if you did build on the software it was GPL and has to stay GPL which means you have copyright over the entire code, except for the libraries. while you transfer copyright to your employer on code you make during your employment, they have to agree to the GPL to modify it and thus the copyright goes back to you.
GPL Quote:
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
-END-
basically, they can have copies, they can run it, but they can not modify it unless they agree. if they do not agree they may not modify it and use it or it breaks copyright. since they are modifying it they have agreed, so you should be allowed to release it as you wish.
BUT:
if he does give it to someone to work on it who is directly under the control of him and they do not give it out to some one, then it may not be a violation
GPL Quote: ... This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
-END
I'm not in anyway close to a lawyer =p
so you may want to call the SFC and ask them about it
http://www.softwarefreedom.org/about/contact/
Someday we'll hit the human carrying capacity. And the band will just play on.
NAL, but here is my interpretation
1) The work you did prior to being employed by them belongs to you. Unless you agreed to assign those copyrights beforehand they have no rights to that code. In practice proving what was yours before hand might be difficult.
2) The work you did for them is a derivative work. While they have rights to the new code (depends on the specific laws but generally that is the case), they have no right to your original code so it might well be useless without the original code.
3) The GPL clause only kicks in on distribution - non distributed changes are not required to be GPLed
4) If they use the GPL librarys and distribute the code, then they would be obligated to distribute the code changes
"I am a recent graduate, and I've been working on my own on a project that uses GPL-licensed libraries..."
Where you started with coding can have some issues too, if the code you developed on your own was also developed on university computers they may have some claim to that too, especially if you developed the code for an assignment or something similar. This too can be dependant on factors such as the country you are in, and how it may relate to the license the libraries are under.
In the end, as long as the employer has no intention of distributing your code, then they own all the code you have developed for them, and as for GPL or LGPL licensed libraries, there should be no violation issues.
I'd also like to note that I work for a large company that knowingly pays me to do exactly this all day. I write proprietary software using GPL libraries and such all day. We just don't distribute it.
That could come back to bite them quite badly. What if one department gets spun off as an independent business at some point in the future? Not solving this problem up front could create some hidden costs for your employer.
http://michaelsmith.id.au
Why is code so different? I worked on a construction site. I would like to open the building up to shelter the homeless, but now my employer is saying that the building I worked on belongs to them!!!
Your employer is (very likely) paying you out of my tax money. I - and you, and her, and everyone else - owns that code, not them.
If you were blocking sigs, you wouldn't have to read this.
All the work you did for them belongs to them.
You don't know that. You are just guessing. He was "hired" but what does that mean? What does his contract say? Lots of people are hired to work on things which don't belong to their employer. He says "I did start the project on my own. And, since no written or verbal agreement was ever made to transfer copyright over to my employer"; that means that their software is a derivative work of software which is legitimately his copyright. Who owns the development after that point may be more complex. Most likely them. Depending on where he is he should probably resign now and send a cease and desist notice asking them to immediately destroy all unlicensed copies of his software. It's probably a complex decision which will depend exactly on what who said to who when, but on the information in the summary you can't make that decision.
=~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
Yes, the the employer has no rights to the code written *before* you were hired. That is copyright to you. All the stuff you wrote while working for them is theirs.
All the work you did for them belongs to them. [...] You have no rights to do whatever you want with the code you wrote for them.
It depends on the jurisdiction, and possibly what kind of employer it is. In particular governmental and some other public employers have restrictions in some countries - e.g., in Finland university teachers and researchers have copyright to what they create in their work. Also, there may be nationally binding agreements with trade unions that have similar effects on some professions.
As a rule, though, with a private employer, and in some countries with all, you are right.
This is a question that can only really be answered by a lawyer familiar with your circumstances and the laws in your jurisdiction. For example, by default, in Canada, if you're hired as a contractor to produce a work, you retain the copyright on that work (or so I was taught in my 100-level Business Law class). However, I don't believe this is true in the US. It's also not true in either country if you're hired as a salaried employee.
But really, plenty of other people will be offering legal advice, and the reality is that this matter won't go to court because it's not worth the time or money for you or the university. You can get a lawyer's opinion that you're in the clear to release your work, but even that's only so helpful to you -- if you threaten or bully your employer, that may just set them against you. (On the other hand, it may be just the thing! Maybe they need to see that you won't be pushed around. Different people respond to different tactics.)
The most elegant solution to your problem is politics. Convince your boss's boss and your boss's respected colleagues that your work would be better off shared -- people's opinions are ultimately derived from the opinions of the people they respect. You've made good use of an open-source base, right? Make sure they understand that there's value in tapping into that community. Allay their fears. Show them the positive side. Get people on your side.
If you can swing this right, it won't matter what the legalities are because the one of the university's officers will sign a waiver disclaiming interest in the code and you'll be in the clear for sure -- and your boss will be pleased at having done something good.
Sure, you should have got the signature before you started working; then you wouldn't have to spend cycles on this problem. Still, it may be fixable.
And if that doesn't work, just remember: the implementation is twice as good and ten times as quick to write when you've done it once before!
That could come back to bite them quite badly. What if one department gets spun off as an independent business at some point in the future? Not solving this problem up front could create some hidden costs for your employer.
why would this be an issue? I believe the GPL only obligates the distributor to provide source code to the distributee, not the rest of the world. Assuming said spinoff gets to retain access to the source code and modify the product however they want internally, then there is still no violation.
The contract didn't convey copyrights, therefore the copyrights are still his, NOT his employer.
Copyrights must be transferred by explicit contract. Not "oh, you paid me, so I guess your demand must be right".
Since the work contains GPL stuff, the university get a non-transferrable license to the combined work and a transferrable right to distribute/sell to others under the GPL.
Absent any contract specifying ownership transfers, it's still the author owns copyright.
NOTE: if the university don't abide by the GPL they are in license violation even if the contract DID convey copyrights unless they have the GPL part taken out.
This is no different tan any other copyright license.
It doesn't matter what they want - you're in a much stronger position than them.
The copyright on the original, developed before you were employed by them, very probably belongs to you. The final project is a derived work of this original. Distribution of a derived work requires the consent of the copyright holder of both the original and derived work - you can prevent them from distributing the project at all (even internally) by refusing to grant a license of the original work. Simply 'remind' them that they do not currently have the right to use the final project at all.
An easier problem than they have with BSA. After all, the spun off company won't have the original license and that original license will have the parent company on it not the spin-off. Therefore they'll need a new license for all commercial software.
This is an additional cost for the company when spinning off a branch.
NOTE: the GPL is satisfied if BOTH the parent and the spin-off get GPL rights to the code. This doesn't cost anything.
That could come back to bite them quite badly.
FUD.
It'll get sorted out like any other license problem, commercial or non-commercial. It's no big deal.
It is impossible to say what's right here without knowing a lot more about the situation. Are the libraries GPL or LGPL licensed? Are you merely linking with the libraries, or is this product a modified version of one or more of the libraries? Is it being distributed outside your employer's organization, or only being used internally?
This strikes me as mostly correct, except that it's not clear to me that (1) is quite accurate in the submitter's case. We don't have the details here, but my money would be that the submitter's situation is more like the following: when Alice started using her original code under the employ of Bob, she didn't tell Bob in any way that she was licensing that code to him under GPL--and in fact, I would bet that there was no conversation about licensing at all. So Bob has some sort of implicit, non-GPL license to Alice's original code, that allows him to at least use the code and modify it for his own uses.
The legal resolution of this situation would come down to either getting Alice and Bob to explicitly agree after the fact on what that license is, or failing that, having a judge decide it. My guess, however (and I am very much NAL), is that Bob can't claim that he has an implicit license to distribute Alice's code, since the contract between them (I guess) doesn't give Alice any special consideration that could be construed as compensation for granting such a license. In simpler terms, if Bob wants to claim strong rights over Alice's original code, and he can't prove that she explicitly granted him those rights, he better be able to prove that at least he somehow paid or compensated him for that code beyond what he paid her to extend it.
Are you adequate?
Fork it from the version before they hired you.
But I think you misunderstand something.. You can perfectly write proprietary software using GPL libraries and distribute it, the only part which you also need to publish is any alterations to the used libraries. So if you only USE libraries you can keep your own code closed source (or not distribute the sourcecode)..
If they do not distribute the extensions to the public, then you have no right to publish it. If, however, they distribute the extensions in any form, they must comply with the licenses of the libraries you referred to (the ones your project originally relied on.) If those libraries are GPL, they must include all their code under GPL (and if those libraries are LGPL, they must not statically link them.)
I'm assuming here that you never publicly released the code you worked on before you were hired; in this case, your code was never released so it was never under any license, and you would have a hard time proving which parts of the code belong to you. As others have said, the most important part here is whether you actually released any source code before you were hired.
That could come back to bite them quite badly. What if one department gets spun off as an independent business at some point in the future? Not solving this problem up front could create some hidden costs for your employer.
One thing to remember if you don't worry about the source code itself, but about obligations that you might enter into by using GPL'd software: By distributing executable + source code _together_ you have done everything that the GPL demands from you. Nobody has any rights towards you at all. So if you spin off another company, give them the executable and the source code.
If you don't do it that way, then suddenly _anybody_ in the world has the right to request source code from you.
I'd say most people interpret the GPL's distribution requirements as only applying once the project has been distributed externally.
The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
The FSF does not have standing to sue unless they own Alice's work that Bob is distributing. Alice would have to assign copyright of her code to the FSF for them to be able to do so.
Are you adequate?
Leave the university and do a "code rewrite", as long as they can't prove you copy and pasted the work that you did under their employment, they have little legal standing and unless this is a real programming gem I doubt they will send the lawyers after you... just look at what happenned to SCO.
Even if they do violate the GPL and distribute the program, you do not have any right to release the code against your employer's wishes (only a judge has the ability to force the release of code). If you do so, you will be sued or possibly charged under trade secret laws.
Everything you've coded is your employer's property and although the GPL may supersede their ownership rights, there is still a hierarchy of rights of which you are not a part of.
consult a lawyer, but IMO the key thing you said is:
"I did start the project on my own. And, since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project."
it was yours to start with. they paid you to do some extra work on it. there was no transfer of license.
they may "own" any of the work-for-hire stuff you did while employed by them (depends on the nature of the employment - usually, in simple terms, if you're a contractor, you own your work but if you're an employee, they do) BUT THEY DO NOT OWN THE COPYRIGHT, AND THEY DO NOT OWN YOUR PRIOR WORK.
BTW verbal agreements are worth the paper they're written on - doesn't matter what they claim you said, if they can't produce a signed transfer agreement, it means nothing. same as if an employer verbally agrees that you will get paid quadruple for working overtime, unless that's standard practice where you work it's unenforcable unless it's in writing. and same as if the salesman says you can opt out of the contract at any time for any reason without penalty - if it's not what the contract says, it means nothing.
never trust a verbal agreement. they're worthless. this is true anywhere, not just in employment.
BTW, crap like this is why i *NEVER* sign an employment agreement without carefully looking at the clauses to do with ownership of work. if it says anything other than "what i do during work time on work equipment is yours, what i do on my time on my own equipment is mine" i send it back for another edit. i've had one or two bosses quibble about that until I ask them if they want to start paying me for 24 hours a day rather than 7.25.
(that question was always a good answer to the occasional managerial whinges about long hair and beard too)
You should have read your contract before you signed it, but if you didn't, then now is definitely the time to do it.
Does the contract say anything about who owns the code you write during working hours? Does it say anything about who owns the code you write during off-hours? And, since the project was apparently based on a private project that existed before employment started, does the contract say anything about that?
If the contract doesn't say anything, then the employer probably doesn't own any of the pre-existing code, and can only use it with your permission (though you should always check what kind of weird legalities exist in your legislation). Maybe permission was implicitly given, but who knows, it might still give you some leverage. You might be able to claim that your implicit permission was based on the equally implicit assumption that the rest of the code would become part of the same (open source?) code base.
"the department's position was that copyright of the whole thing belonged to them"
It doesnt matter what license the department releases the code under, it will still belong to them, only a license transfer will make it not theres.
If they merge other peoples copyrighted work with theres then neither party owns the copyright to the whole thing.
Maybe suggest releasing the code but maintain there own seperate fork, it would provide some accountability/transparency, might help with feedback and bug reports.
It could allow "outsiders" to experiment in taking the code in new directions that management are risk/averse to, if it works out then the company can implement feature/idea with there own money (being careful not to infringe).
work done as an employee is typically owned by the employer, but it's my understanding contractors own the copyright unless specified in the contract. They are self employed and can distribute code with whatever terms they agree upon.
It depends on the country laws, contract and employer.
My contract is based on french telecom legal template which says:
- code specific to the assigned work: all copyrights belong to the employer.
- code *not* specific to any assigned work:copyrigths are shared by the employer and the employee (you need an agreement to work on that code). Namely if the employee departs from the company, he will keep the copyrights.
Of course, there may be more about this in the french law (I was told, french copyrights on code always belong to the employee). And of course, an employer aware of the open source ways would let the copyrights go to the employee or at least be shared.
The main issue with the shared copyrights: the employer would have the right to close the code produced by the employee. And that's a very big issue for GNU GPL coders! You know... those guys who want to have the best open source code installed by default on all systems.
Use the identity of someone else to contribute to the GPL project.
But they MUST keep the code GPL, because it's based on GPL code.
GPL clearly states even the owner of copyright on given work can't remove GPL from it.
By hiring you to continue to work on a GPL'd code, they set themselves up for it. The code still IS GPL.
The worst they can do is to keep it "closeware", e.g. GPL code used only internally, never distributed at all. But if even one copy ever "leaks", it's out in the wild and free for all.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
If they own the copyright they can choose not to license it under the GPL to the public. They can then choose to delete the
entire source tree. I'm not too sure if they can't also compile the source files into binaries but assuming they can, where the
buck stops is linking with GPL licensed code that is not explicitly covered by the LGPL. Right. No linking allowed. Whatever
they do, if the executable contains GPL licensed code they can not run it. Even debugging the program and even if they
step only through non-GPL code, it's not permissible. To the IANAL who said the GPL kicks in when you distribute it, that
is not true. You shall have no use of GPL code even for internal in-house purposes unless you fulfill all stipulations in the GPL.
For example when you modify GPL code (a single character in a source file is enough) and even if you just use that in-house
you are required to publish the modification or the license grant by the copyright holder is null and void.
In short they can either try and replace whatever GPL code there is if that's at all feasible or they can choose to scrap it
entirely. If the portion of code that is _possibly_ owned by the university is useful or can be easily made useful by itself
then they are free to do that as well and choose to do with that what they will.
You have to distribute source with binaries or offer to provide source to anyone who asks, good for three years. (at least for GPL 2). There is a small exception for academic institutions to only have to provide source to direct recipients of binaries, IIRC. Been a while since I read the GPL.
In Liberty, Rene
How intelligent - suggesting that someone blatantly violate copyright law in order to release code they don't own the rights to under GPL...
Did you start the project as part of your course, or was it totally outside the University? Your post suggests that it was outside of Uni but if it was for your final year project or some such thing, then the Uni probably own it all, not just the parts you implemented while working as a staff member. I remember that all the code I wrote for any course work was owned by the Uni not me. Somewhere in the course literature there is the small print that few people read, usually at some point above where you sign your name.
As I see it the situation is this:
Poster has small GPL project
Poster takes employment to develop project into a solution
Employer claims copyright of solution and original GPL code incorporated
Now as the author of the code the poster could release it to someone on terms other than GPL (dual licensing). The question is whether he has done so, intentionally or otherwise. It is certainly possible that the contract of employment said that all the copyright of all sources used in the solution will belong to them. The only ting they can't do is remove the GPL from the original project, other people will still have the right to use and develop that.
If you can prove that your program is a modification of a GPL'ed program or if it uses GPL (not LGPL) libraries, then getting permission to give away, or even better, sell, just one copy of the program to another entity, would mean the source could be free afterwards: you would have the obligation to hand over the source under GPL as well.
So try to find a party that will buy the software, and would free the source afterwards.
Please note, that it's not enough to sell the software within your university; nor would it help to sell the software to another party that is not interested in freeing the source (because that would just get you two organisations using your imprisoned code).
That's LGPL.
Any time you work where you are producing intellectual property, you should insist on conditions (on paper) that allow you to retain rights where they are generated. If you have a brain that they want badly enough, they're not going to say no. I do (admittedly I don't work with FOSS) and no employer has worried about it yet.
For example when you modify GPL code (a single character in a source file is enough) and even if you just use that in-house
you are required to publish the modification or the license grant by the copyright holder is null and void.
You're wrong.
http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
"The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization."
if you wrote the software using the employers time and resources, its their project and you had no right to decide on the licence without their consultation anyway. if you wrote it on your own time and resources and you decided that the GPL was the licence to go with, you have a conflict or interests in bringing that software into your employer. the only real way to get around this is to have two seperate branches of the product, the closed product for the employer and the open source gpl version that you produce in your own time
portfolio
I hope http://www.gnu.org/philosophy/university.html helps. You may also ask the funding body for help if it is an external one. Finally there is the Freedom Of Information Act. But first try to resolve this within the institution you are working for. Resolving means that you get a copyright disclaimer.
You can do whatever you want with the code you originally brought into the project.
What you have developed since is basically just a huge patch for which the copyright belongs to your employer.
Thei are not in GPL violation as long as they do not distribute the software.
Your employer is wrong, when he states that the have copyright of the whole thing. They don't own your original code, but it doesn't really matter much.
Why dumbasses fall for all that "your work done here doesn't belong to you" bs, I will never know. Unless you expressly give ownership of your copyrighted works over to your employer via contract or other legally-binding paperwork, if it is your "original work" IT IS YOUR IP!!! As it is "your" IP, they have no right over it's use (unless you've entered into a service contract or licensing agreement previous to it's creation), or distribution! However in the case of GPL libs and such, I believe that even "YOU" are not legally capable of re-distributing it (unless you've credited the "creator" with contribution ($$$) or attribution (some note in your code attributing the material's creation to it's "real" creator) , so your employer's claim of ownership of the GPL'd sections is faulty and moot.
-Oz
The key words here are:
no written or verbal agreement was ever made to transfer copyright over to my employer
No contract = no copyright transference. I am not a lawyer, I am not your lawyer, talk to a lawyer before doing anything else; but in my opinion, the employer doesn't have a leg to stand on in this instance.
This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Release the code you wrote before you were employed as GPL licensed code. That code belongs to you, you can do what you want with it, and while they might like to claim ownership of it, the only way they can do that, is if you give it to them. Read through your contact as well . . . .
I don't know which country you are in but in the UK for example, this is just not true. Copyright absolutely rests with the creator unless there is an explicit transfer of ownership stated in the employment contract. Any part of the work he created before joining them is his. Anything he created while working for them only belongs to them if the appropriate clause is in the employment contract.
This is somewhat pedantic, but I think it is important to point out that you are writing free software. You are giving your "customer" (i.e., employer) all the freedoms necessary to be free software. You're even giving them the copyright (I assume). You can't get any more free than that from your perspective. Whether or not they choose to distribute it further is their business. They are perfectly free to do so under the GPL. But they don't have to if they don't want to. That is their freedom.
Of course it is also proprietary, meaning that your employer holds exclusive rights to the software and these freedoms. Because they are the only users of the software, free and proprietary are not mutually exclusive. Again, while this pedantic, I think it's important for people to understand what "free as in freedom" really means. Doing what you are doing is perfectly fine from a free software perspective.
This is somewhat confusing to me. The person in this question started the project on his own, BEFORE he started working for the university. As such, shouldn't he still own the copyright for it unless he explicitly transferred the copyright over to them?
Atleast all the code he had written before he started working for them are his as far as I can understand, but how about the code he has written afterwards? It is still part of a project he started and owned.
Also doesn't every recipient of the binary+source get permission to redistribute that?
Justice is the sheep getting arrested while an impartial judge declares the vote void.
Universitys automaticaly hold interlectual copywright over any application that has been created during your time at university or at least mine did.
Read your contract. What does it say about copyrights?
By the way: where are you located? If you're in the EU, chances are you own the copyrights.
In short: read up on local authors rights and copyrights. Trademark laws do not apply.
Also, do you work on this project in your own spare time? If so, chances are you can shove the GPL down the throat of your employer.
Also doesn't every recipient of the binary+source get permission to redistribute that?
Yes, they retain that right. The main point he was making is that you are only required to make the source code available to someone you gave the binaries to, not the general public. That is one point of the GPL that often gets misunderstood, you do not have to give your GPL code to the public per se, only to those who you selected to have the binaries. If they further distribute the binaries, you are not responsible to provide the source code to those 3rd parties. This means you can sell GPL binaries, and only provide direct copies of the source to those customers, and never the "public". This is a feature of the GPL, not a bug.
Tequila: It's not just for breakfast anymore!
And, since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project.
In the US, transfer of copyright must be in writing. They do not own what you created on your own unless you sign something. A contract upon hire would have taken care of this. If you signed no such contract, they own bupkis.
Let me reiterate:
The default with regards to copyright law is that the author has copyright and it *must* require a *written instrument* to sign over copyright. The law is _very_ clear on this issue.
This is what SCO tried to get around with the Asset Purchase Agreement. Since there was nothing saying they bought Novell's copyright to SysV Unix, they don't own it. They lost twice, once in front of a judge as a summary judgment, and later in front of a jury.
Don't be bullied.
Don't put up with this shit.
--
BMO
You give them the source? Unless they then also intend to distribute it, what's really the problem.
People replying to my sig annoy me. That's why I change it all the time.
again, IANAL, but I think this is the way the legal system sees it...
or to phrase this in a more technical way:
person X releases a project P under the GPL
Y hires a set of people Z to work on P. they develop P'
the contract between Y and Z basically says that the people in Z sign their ip rights to the code they developed on their worktime over to Y (I think this is the point where they think you signed ALL rights to the project over?)
but because of the license, Y must release P' to X
I don't think this circumstance changes, just because X \in Z...
The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
You have to distribute source with binaries or offer to provide source to anyone who asks, good for three years. (at least for GPL 2). There is a small exception for academic institutions to only have to provide source to direct recipients of binaries, IIRC. Been a while since I read the GPL.
You need to go re-read the GPL then. Let me help, here's the relevant part of GPL 2:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
The relevant parts of GPL 3 are sections 4 through 6, but they only add to the older license. In particular, they allow distribution via the Internet, but they do not force such distribution; you can always use the older methods.
Nothing for 6-digit uids?
First: If the project was under the the GPL and the libraries are under the GPL, the result must be under the GPL.
Second: Depending on where you live, you might or might not have given over the rights to your employer. You need to take your contract to a lawyer in your country and ask them. As usual, slashdot is _not_ the place to get specific legal advice; we can just blabber about generalities.
Thing is: The GPL does not matter unless you distribute the software to anyone. Before that, the licence does not matter. So you need to check the _second_ point first. When/If you release the software and the libraries are GPL, it's a clear-cut case.
No idea if your employer can go after you for "wrongfully leading them to believe they owned this stuff" though...
Pardon my bluntness, but that's relativist bullshit. The code is written by an employee of a company which has no intention of publishing its own software under an open source license. I emphasize the ownership because it is not the programmer's code at any time. He does not write free software which he licenses to the company, which then merely chooses not to redistribute. He's an employee of the company, so the program is effectively the company's creation. If you write a program on your own time intending to sell binaries and to never show the source to anyone, are you writing open source software? No, the act of publishing the source with the rights to make changes to it is what makes software open source. In fact, all software is created as proprietary software as a result of copyright law.
ONLY if they want to distribute the code. If they only want to use it in-house they can lock it up in chains of gold for all the GPL cares. The GPL is a copyright license and thus only deals with limiting COPY rights, not with limiting USE rights. That is what EULA's are for...
It is important to make this distinction. By not making the distinction you only play into the hands of those who wish to denounce the GPL and other free software licenses. They could use your lines to show the dangers of using these licenses, even though what you say is wrong.
--frank[at]unternet.org
But then again, can you survive a law suit? Do you want to fight them if they just fire you? Probably not - and most of these corporate types know it.
Need an ISP in South Africa?
So, as I understand it, there are 3 pieces of software here. First are the GPL libraries; let's call them 'A'. Then, you have the software you did as a hobbyist, let's call that 'B'. Finally, you have the work for hire, called 'C'. C depends on B, and B depends on A.
It's clear that they own C, and there's nothing you can do about that. On the other hand, you own B. If you publicly distributed B under the GPL, you are probably screwed here. In that case, there's nothing to distinguish B from A, and your only recourse might be some technicality in the GPL. For example, if you used the GPL v3, you may be able to use the stuff about software patents to prevent your university from using it.
However, if by releasing B under the GPL you mean you just used GPL software and considered it free, you may be able to turn around and teach them a lesson here: assert ownership over B, and demand that they produce written proof otherwise. You could demand that C be open-sourced in return for being allowed to use B.
That being said, though, you were stupid to do closed-source work on your own open-source project. Not only will you have to fight for access to your own work, your knowledge of the closed-source work will probably 'taint' any contributions to the open-source one to such a degree that they could probably claim work you do on it, even if it's off their payroll.
In the future, don't be so trusting of your employer. When I do open-source work for hire, I create a private github account and make the repo publicly available and GPL-licensed from day one. All of my work on the clock is then contributing to an externally owned and operated repo.
Oh, and I get the corporate overlord's approval of open-sourcing the thing in writing.
Their contractee HAS a license: GPL
This means you can sell GPL binaries, and only provide direct copies of the source to those customers, and never the "public". This is a feature of the GPL, not a bug.
Yes. Because the customer has the right to redistribute the code, the GPL makes it difficult to enforce the sole-source model that proprietary software business models depend on. So, GPL distribution seems generally to get conceptually simplified to 'author releases for free to everyone.' There's nothing to prevent the author from charging $10k/copy (as long as he includes the source), and the purchaser turning around and distributing the exact same thing for $0. In the case of a spin-off, one imagines that whatever motivates the original company to retain the GPL-derived software internally will provide similar motivation to the spin-off.
Someone else answered it in a long fashion, but to put it short: You only have to provide the source code to those entities you provided the binaries to, NOT the general public. Otherwise would create an undue burden on the original programmers.
If you make Program A, give me a copy with source, and I sell the binaries for $10 each (or just hand them a disk free), you are NOT responsible for providing the source code to those customers, *I* am, and you would have the legal right to force me to give them the source code since *I* distributed the binaries. I don't have to provide a copy of the source to anyone else, only those I gave/sold the original binaries to.
Tequila: It's not just for breakfast anymore!
Is it not considered "distributing the binary" when I as an employee run some customized software on my company-provided machine?
Should I as a human have the right to the source code at that time that the binary is distributed to me?
Or does corporate personhood take precedence?
I feel fantastic, and I'm still alive.
Absolutely the answer this this guys question is YES.
Why is such a plainly simple question even on slashdot?
Better yet why are people arguing about things that are directly covered the the basic FAQ?
In a nutshell, no they cannot. If they do, first they are in violation of the GPL and if they continue, then they themselves are in violation of Copyright laws.
My karma is not a Chameleon.
A few years ago, 2 I think, I was working on some code for a prof to help a robot play soccer. At the time it was just assigned to us and he screwed off and didn't really talk to use for a month. He gave my partner and myself a lib to do Image Capture that was HIGHLY proprietary and actually sucked unbelievably bad. My partner and I said screw it and picked up a GPL licensed image capture lib and started to program, when I was done I released all the code I had done to a public code forum to share it. When my prof found out he went insane, he was so pissed it was kind of funny. He kept telling us that open source is a really bad idea and we should have known better then to use GPL code. I told him to F*** off and we passed. The year after I was working for another prof doing some more code but she wasn't in my field. Again I grabbed some GPL code spun up the solution, released it and gave it to her. She was so afraid people would now hack into her software because it was public code she refused to use it and told me I should have known better. Again I told her to F*** off and I passed. The main point is that Prof's seem to hate Open Source, not all of them but enough of them. They just can't admit it's a better way of thinking, kind of like the church and science, science the better way and the church well it did kill people for saying the earth wasn't the centre of the universe (very intelligent).
My employer FORBIDS me to use ANY GPL code for this reason. Doing so is cause for immediate termination and grounds for legal action. He doesn't even want me LOOKING at GPL code because of the risk of contamination - I am not to run Linux or work on any GPL projects even in my off-time because of the risk of contamination of GPL-covered code into our projects.
1. You own the code created prior to you beginning work for the university.
2. You and the university co-own the final code (as it was derived from your code) UNLESS some employment agreement you signed gave them sole ownership when you began work (unlikely).
3. And yes, absolutely the university can not release the source even if it uses GPL libraries. People constantly get this wrong. The university is only required to release the source to the project if it DISTRIBUTES the code outside of the university. And then it need only distribute the code (or least offer to distribute the code) to those whom it distributed binaries. It is not obligated to distribute the source to the general public, at least not because of the GPL.
If this is a university, publish it under GPL/BSD. You guys are public employees and all your work are belong to us.
[Disclaimer: This is not a troll or a flame. I’m just really shocked.]
I can not believe the utter absurdities mentioned on Slashdot.
Most comments seem to say something like “The code belongs to $someone”.
Now read that again: The code belongs to...?? Code belongs??
What the hell?
It feels like the FUD and propaganda of the **AA have completely succeeded in brainwashing people that you could actually own information. What an absurd concept!
How can you possess something that can not be stolen? How the hell do you own something, that you can not control? I mean, not ever! If you pass it one, your control is gone. If not, you can not prove its existence. It is not a physical object. You can’t possess it. You can own the container. Or offer the service that produces it. But that’s something different. All the premises required for something to be ownable, are not fulfilled for information.
It just makes so sense. How can grown up people with a healthy sense of reality believe such fantasies?
I know that all humans start believing something, when they just hear it often enough. That’s kind of a side-effect of us being social beings. But come on. This is like believing in Santa. Or God. Or saying that you own happiness. Or the color magenta. You know: Things that would have gotten you locked away 100 years ago, and certainly require therapy nowadays.
I’m sad. Because it feels like they have won, and we are to blame, because we the experts — of all people — bought into their lies. We were supposed to be the last defense. Am I now really standing alone??
Oh well. At least they have to walk over my dead body before I give up.
Any sufficiently advanced intelligence is indistinguishable from stupidity.
Depending on the circumstances, the employer may or may not be legally entitled to use the code how they like. But there's enough discussions here on what constitutes development. But...
The developer may not have been legally entitled to collect a paycheck to work on GPL software on company time.
You hear horror stories all the time going everywhere from rent-a-coder to some utility bundled on the Microsoft CD, where the employer had the expectation that they owned the code, only to find out a developer cheated and used some GPL code.
Since the developer even said that there was no written of verbal agreement with the company, the default assumption would be that they are paying you to write code that they will own.
I don't want to get into legal quibbles here, but the developer has basically defrauded the company if he got paid to deliver code that they can't use because of the license.
Can you construct some sort of rudimentary lathe?
Is it not considered "distributing the binary" when I as an employee run some customized software on my company-provided machine?
Should I as a human have the right to the source code at that time that the binary is distributed to me?
Or does corporate personhood take precedence?
No it is not considered "distributing the binary", as long as it is only installed on the company owned machine. If I write some code and install it on my computer, it is not distributing the code if I let you use it on my computer. It only becomes distributing when I allow you to install it on your computer. It is not about "corporate personhood" (except in so far as that applies to ownership issues), it is about who owns the computer the code runs on.
This gets more complicated when one organization rents computers from another, I do not have an understanding of the different permutations that come into play in that sort of circumstance.
The truth is that all men having power ought to be mistrusted. James Madison
First of all, I don't think judges and courts like tricks. They can just say they don't buy it. (Though I've never actually known a judge.)
I would also think that by working for an employer, you granted them the copyright and/or license to use that work, previous licenses notwithstanding. I don't know that the employee can distribute the work either, as the new and improved version isn't the same work as the original, and to my way of thinking, the employer owns the copyright to the new version and has a royalty-free license to use the old version. I don't think a court would buy the argument about simultaneous forks.
Because you did not sign a contract concerning the code or project then it would seem the following scenario best fits you.
Any code produced prior to employment can be applied under any license you wish it is owned by you and protected by lack of contractual agreement, this also forces code written afterwords to be GPL'd as part of the project.
Remember it is true that any work produced while getting paid is the product of the payer unless otherwise noted, they cannot simply assume the body of work as their own. They may attempt to argue legal custody so keep this in mind (and maintain your documentation). You own any code produced prior to employment (as long as you were accurate in your story): You can counter argue that they attempted to use employment as a means to acquire the project sans contract and thus have no legal right to it. You can also argue that they hired you for coding but not the specific code and because you have a prior body of work that goes into the project in deed like a book, you own the code (all of it) and they are licensed to use it for the duration of employment at the cost of employment. A more liberal interpretation may also take you to copy write. Code is writing for a computer to interpret and should fall under the copy write category. As an author is hired to produce a book you are hired to produce a program. Because the core code and in deed original versions of this application fall under a private enterprise you can argue ownership; now that said, this can effect your employment opportunities negatively.
A good idea might be to engage in contract talks for the employer to purchase ownership or license with a limit to duration the right to keep your original code from GPL. While I am a giant fan of GPL, I do recognize the needs of employment and if they are wishing to in truth own the code, make sure you get a solid of what it is worth now and with possible future earnings in mind. Having them agree to contract with term limits allows you to give them decision rights on licensing for the duration of your contract (do not make it indefinite) and gives them time to have the original base code or ideas replaced by their own closed source work. Your work is worth something, get a lawyer (of your own not the company/employers) to write out an equitable contract.
If you don't do it that way, then suddenly _anybody_ in the world has the right to request source code from you.
Or you could go with the third option of exec + written notice that allows on-demand access to source for 3 years. It seems everyone always forgets about this method.
You can try, then when you go to court, the judge will smack you in the face for trying to sneak around your legal obligations.
When you write something on your own with clear knowledge of the requirement for your employment, using knowledge you gained FROM your employment, you have a really HARD time trying to convince the court that it really was 'your' work.
The government and courts have been dealing with people far sneakier than you for several thousand years.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Perversely, it's not QUITE that simple.
Unless there is a work-for-hire clause in the contract or employment agreement, it can be said that they may have an interest in the rights on the code in question , but it can't be said that they actually OWN it unless you've got one of those clauses in place or an explicit assignment of rights in play. Moreover, there may be explicit restrictions on the work-for-hire aspects. Some will lay claim to anything you come up with, regardless of whether it had anything to do with your work or while not on the clock- others will only lay claim to the work you directly do for the employer and variations on a theme in-between.
Now...most employers have work-for-hire clauses in the mix, so that's where your assumption comes from. But it's not a foregone conclusion, nor is the one you stated a foregone one.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
It all rests in what his employment agreement/contract states. If it lays claim to any intellectual "property" work while under their employ, that explicit transfer will have been deemed to have transpired. Depending on that, is whether they actually have a claim on things here or not.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
You and most other commercial developers who actually need to eat.
I only release my work under a BSD license for this very reason.
It means my boss doesn't give a shit what I write at home as long as its not related to our core business. He rests safe in the knowledge that any thing I make at home and use at work is safe to be used at work.
It also means I get contributions back from professional developers at other businesses who use my code (and our companies code, some of which is BSD/Apache/MIT licensed).
If we used (L)GPL, no one would want anything to do with our code, and everyone would be poorer for it.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Check with your school's Technology Transfer group. While it is true that Universities generally want control over everything created while you are working for them, most of the time the value to the University is not worth their time or trouble. If your work will generate actual revenue for the University (revenue that will actually offset the work involved in licensing and all that), they'll be very interested. If not, they will most likely leave it up to you to do with it what you will. At least that is how it works at my school.
If the university is funded even partially by the state, in my view, anything they create is public property.
Some academics may disagree, but academics are a lot of self-righteous elitist jerks anyway.
Work for hire still would trump that. His motivation for developing the code is due to requests from his employer. Building two forks & then claiming 1 for me 1 for you still doesn't obviate the motivation for the code.
I am not a bookmark manager, but what the hell. Those folks actually spent a bit of time thinking about this shit, you know. If you're still confused after reading the FAQ, direct your question to GNU or FSF, not bloody slashdot.
May we live long and die out
loophole.
Thats from the summary ... the guy already knows the answer, he just doesn't want to accept it and is hoping slashdot can give him some way to get around the agreement he made with his employer.
Good job there buddy, you've just shown the world you have no intention of keeping your word or honoring your obligations.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
What if one department gets spun off as an independent business at some point in the future?
If that department needs to distribute copies of the software : Then yes. Big problems.
(Copies need to be made of the software, and therefore the copyright law kicks in : You can't make copy of things you don't own, unless you have a license. And the program's current copy license [GPL in this context] gives you authorisation to make copies, but only if you also hand over the code and anything else needed so the others can play with it).
So the new company must rewrite the GPL parts or find LGPL/BSD alternative or release the source of everything linked against the libraries.
If that department only continues using it internally : then not a lot a problem. They still can use it.
(Usage is not controlled by copyright licenses, these control only copies. EULA *could* address usage, but they are not considered valid in lots of juridictions).
The only problem that arises is that after the split, the parent university and the new private company won't be able to send each other copies of the software, so development will need to be forked.
(Although, sending *patches* and compiling on its own might be legal).
That's why it's preferable to use *L*GPL or BSD components for proprietary projects.
LGPL will work like the GPL be only at the level of the component. So if a library is linked against a whole project, only modifications to the library itself needs to be released - the rest can remain under any proprietary license.
BSD will let the company re-license the thing to something else, if they want.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Explain the GPL, that your work is based on pre-existing GPL source and what that means (that modifications to it are also GPL). Make it clear that they are not required to expose/distribute the source unless they distribute it. If they're still staunchly against GPL'ing the code. Proceed to explain that in order to break away from the GPL code, you'll have to start from scratch and find lgpl or bsd libraries to replace the gpl ones or write them yourself. Give an honest assessment of how long it would take you to start the project over like this. They're your employer, if they're willing to pay for closed source and absorb the overhead of not leveraging open source libraries then go for it! More money for you. :)
Can they still claim copyright and prevent me from publishing the source code even though it is derived from GPL software?
Anyone can CLAIM copyright to anything.
Preventing you from publishing the source would only be accomplished by a judge ruling in a court case. It's that simple.
Ownership of copyright can be determined by a judge, too.
That said, if the company knowingly employed you to work on a GPL'd product, their ownership of the copyright may be more difficult to present to a judge.
You could end up quite screwed here. Just because you GPL'd something doesn't mean it's always and forever GPL. This is not to say what's already been released as GPL can be taken back. That pee is already in the pool so to speak. However, as long as you are the copyright holder you're free to license the code as you see fit. The GPL doesn't lock you in unless you assign the rights to FSF or something. The problem you run into is you may have signed an employment agreement that compels you to transfer code ownership. As such you can lose the copyrights to code you have authored before your employment because of your employment agreement. It's also important to remember, even if state laws give you rights, those rights are not free. You need money to defend those rights.
The long and short of it is don't mix your open source project with work for hire projects without a specific rider on your employment agreement that spells out ownership in exacting terms.
Level 1) If I read the summary correctly, you wrote some code before you came to your employer. If you GPLed that code, then the code written prior to your employ is yours to do with as you want. Unless you somehow signed something to give rights over to your employer.
Level 2) Any changes you created to the project while under the employ of your employer. These belong to him/her/it. You cannot distribute them without permission. If your employer does distribute the code, because of the GPLed libraries and stuff, the employer must provide source code. But if your employer does not distribute the code, then he/she/it is free to keep it a secret and not release it. These are the rights under the GPL, it mostly protects the rights of an entity that the software is distributed to. But without distribution it doesn't apply.
I'm definitely not a lawyer. But it seems to me your best options are the following:
1) negotiate to buy a license to the software. If you get your employee to distribute it to you somehow, then you can demand the source and you are free to do what you want with it (via the terms of the GPL the employer cannot revoke your right to modify the code if you have the program distributed to you).
2) if your employer ever creates a commercial product from your code, buy it and then demand the source code and you are free to do what you want. If your employer ever makes a commercial product cheaply, buy a copy and then demand the source code, under the terms of the GPL
And, since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project. Also, the whole project relies on GPL libraries, and without those libraries it would be useless. Can they still claim copyright and prevent me from publishing the source code even though it is derived from GPL software?"
Any work for hire legally belongs to the employer, no verbal or written contract is necessary. (Unless you're freelancing, in which case you retain your copyrights). In this case, all of the changes you make belong to your employer, all new code you write belongs to your employer, you have no legal claim to the code, and as such, you cannot release it to the public without your employer's consent.
That the base libraries are GPL-licensed is inconsequential, as long as they keep the code internal, the GPL does not come into play. Even with straight up open source projects, the GPL is still governed by copyright law, and the actual copyrights to the code belong to the authors/contributers, this is why the FSF once upon a time, would encourage open source developers to re-assign their copyrights to the FSF, both for legal putposes, and because the copyright holder retains the right to relicense their code as they please, GPL or not. This is also why some companies working with open source (Sun comes to mind (OpenOffice and possibly OpenSolaris as well work this way), MySQL-AB may have done this as well) requires for external contributors to sign over their copyrights.
The GPL, again, is governed by copyright law, and contrary to popular misconception, it in no way circumvents copyright. You can't even technically fork the code in question (to release it to the public that way) because the code you wrote, that belongs to your employer, probably is not under the GPL, and despite what the GPL says about derivative works, and how such circumstances don't/can't legally occur "in the wild", the code isn't "in the wild", the GPL doesn't apply when the code isn't distributed - You can, of course try anyway, and argue that the GPL still applies, but you can expect your employer's lawyers to nail you to the wall for it.
All that matters is the IP agreement (if any) you signed when you went to work, and the related question of whether you can prove that you were working on this project before you started. The actual question is whether your Employer has a right to use your software which you started before you went to work and which therefore cannot be a work for hire. At the same time you MAY NOT own your subsequent work which may belong to your Employer (in some jurisdictions various types of work for hire do NOT create "works for hire", and extending something may qualify; talk to a lawyer). Lacking an IP agreement you will negotiate one. You will state that it was your intention (perhaps even clearly) to release your work as Open Source, and they will state their intention to keep it proprietary, and you will negotiate a solution or your work will disappear into a rights hole. A judge should think that obviously you meant to implicitly license your work to your employer, but will not assume you implicitly meant to transfer copyright. It really comes down to how much your positions matter to you and your employer. If you convince the judge that you accepted employment under the impression that your open source work would remain open source (and if your employer is a university this may seem like a reasonable assumption), you may prevail simply. good luck.
The company hired you to improve an already existing piece of work.
It is irrelevant whether or not you created that work in the first place, as you say that there is no agreement to transfer copyright, etc, to the university of the system you had written before. Therefore if the previous system was GPL, the university should make its changes GPL, or negotiate with the author of the original system (you) for its own license.
Using GPL libraries shouldn't be a problem however. Indeed as an internal project they can make their own changes and not release them anyway.
I think you'll have to suck it up for now, the university owns the work you've done. Of course if the university is publicly funded, then really it is the taxpayer that owns it, but know how that goes in general. Just take the money they're paying.
Once you've finished doing the changes, you can go back to the previous version that is yours, and add in the new features again, from scratch, building upon the knowledge and experience you got from doing it before!
Is it a public university? Was it a publicly funded project? Does your state have a FOIA statute?
You should actually read your local copyright law, because it can depend.
Out here, in Latvia the copyright always belongs to author (developer), unless specifically stated in employment contract.
So, the company can use the code you written for them, they are granted rights do distribute, etc, but you're still the copyright owner - and you can release it as GPL or whatever you wish.
Let's be clear. You have no rights to do whatever you want with the code you wrote for them.
Be careful now, that isn't always true. This work is GPL-necessary because of the external libraries, is it not? Normally a company developing software will be shuffling it around internally and making lots of copies, and this isn't a problem for copyright because the copyright is owned by the company. If the software is GPLed it isn't a problem either because redistribution is free. However, it does require compliance with its terms -- which means that if the company has provided you at any point with a copy of the software (i.e. it has gone through their hands and back), it is only allowed to do so under the terms of the GPL, and under those terms you have the right to redistribute. Of course, as always, talk to a lawyer first etc., but the point is "you have no rights" is rarely the truth.
1) If your libraries where GPL and properly published before starting to work with this guys:
They can either use the code only in-house, and never distribute it, or distribute it under the GPL.
2) If your libraries where LGPL, and properly published before starting to work with this guys:
They can distribute the code under any license they want, and link it to your LGPL libraries.
In any case, they do not own the code for your libraries. You can still do whatever you want with them.
WTF am I doing replying to an AC at 5 A.M on a Friday night?
A "work made for hire" is— (1) a work prepared by an employee within the scope of his or her employment; or (2) a work specially ordered or commissioned for use as a contribution to a collective work, as a part of a motion picture or other audiovisual work, as a translation, as a supplementary work, as a compilation, as an instructional text, as a test, as answer material for a test, or as an atlas, if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire. (17 U.S.C. 101)
As usual, incorrect information and faulty assumptions abound on Slashdot about what the law is and means. There is nothing in your post that should make you assume your employer owns anything. Two part analysis:
1) Does the work created prior to your employment fall w/in any category described in section 2 above? No. Your employer doesn't own it.
2) Does the work created while under employ fall within the scope of the work you are hired to do? It is unclear from you post if they hired you to do this, or if they asked you to take this on as an academic project separate and apart from your job responsibilities? If no, then you are the owner. If yes, your employer may be the statutory author of contributions you've made to the work as an employee acting within the scope of your employment.
That's the correct answer to your question.
Anyone following the SCO case would know that in the US, copyright transfer can ONLY be done with an explicit writing.
Saying that the Uni has an "interest" in code written before he was hired is just posturing. There is no such thing in law as an "implicit copyright transfer" - SCO tried to argue that, and failed.
I'm amazed at how quickly people forget ...
Then "internal use only" that supposedly lacks distribution effectively does not exist unless all members internal to the organization enter into (and never violate) an agreement to never convey/propagate/distribute the GPLed code, which is the entire executable and all of its source code now (not merely the GPLed libraries).
But then again entering into such an agreement is itself a violation of either GPLv2 or GPLv3 because neither you nor your university can impose more-restrictive legal terms than was contained in the GPLed libraries, even for users within your department or your university. So any person in the university who has access to the binaries can request the source and then convey/propagate/distribute both the binaries and the source code worldwide without any restriction whatsoever (until the GPLed libraries are replaced by nonGPLed libraries). Effectively, legally (FSF's nonbinding legal advice notwithstanding), there exists no such thing as "internal use" that assures a lack of conveyance/propagation/distribution in an attempt to not comply with the GPL's terms.
This sort of question is exactly what the Software Freedom Law Center is for.
Just keep swimming.
If this university department is the same department/school that you graduated from, they potentially own rights to what you created while you were a student as well.
Why can't that employee use the GPL to demand the source code to that supposedly "internal only" executable? Then, why can't that employee say "The GPL prohibits adding more-restrictive terms to the executable than the terms of the GPLed libraries." and then say "Prohibiting me from distributing this now-GPLed executabile and its source code worldwide is itself an additional restriction that neither the author nor the university can impose on me." And then convey/propagate/distribute the executable and its source code worldwide. The bits & information want to be free.
If you don't do it that way, then suddenly _anybody_ in the world has the right to request source code from you.
Sorry, that does not make any sense to me. How do you come to that idea?
angel'o'sphere
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
IANAL, but my guess is that if it's in your contract
From the original post:
And, since no written or verbal agreement was ever made to transfer copyright over to my employer, I question whether they can claim that they now own the extended version of the project.
The software in question began as a hobby project by a graduate student "on his own". It was based upon GPLed libraries of code by others (who have their own copyrights on that code) as well as code he developed prior to his employment (on which he holds the copyright).
Though any code this person developed under the employ of the university (ie. on their dime) is most likely under the copyright of said employer there was no agreement to transfer copyright of any PRE-EXISTING code and the employer cannot limit the original copyright holder's distribution rights.
HOWEVER, any derivative work done on the employer's dime WOULD have the employer's copyright attached. So, although the university has NO right to block the distribution of the ORIGINAL code or the unmodified libraries on which it is based it CAN prevent the derivative work from being distributed. The university should be aware that by employing this student and using his GPLed code as the basis for the derivative work they've agreed to the terms of the GPL. Those terms give the university full rights to restrict or permit distribution as they see fit. BUT because they are bounded by the terms of GPL if the university decided to sell or otherwise distribute this product to anyone else THEY MUST DO SO UNDER THE SAME GPL TERMS. This means full disclosure of source code to those that receive the software plus the rights to redistribute under GPL terms. If they make binary-only copies or place furher restriction that is copyright violation and software piracy no different than downloading a cracked Windows 7 torrent.
The path of least legal resistance would be to capitulate and let the university have what they have, but to release the code as it existed before the term of employment started as a project on sorceforge or google code or wherever as the basis of a "community development" fork. Because no transfer of copyright agreement was signed the employer would have no recourse, however if you want the added functionality of the later product it would have to be re-implemented in a meaningfully different way.
If you have the time and money or a generous lawyer friend (right there next to your hen's tooth lol) then it might help to remind the those employers who are resistant to the isea of the terms of the GPL, just in case their reasoning behind blocking distribution is because they want to commercialise the software itself. However, they might have legitimate reasons to keep the software to themselves. For example, the nature of the software's functionality might betray a proprietary business or technological process, or some other "trade secret". GPL is there to protect the freedom of software, not to thumb the nose of all IP law and ruin business plans.
Did he modify the libraries he's using? Is he sure it's actually GPL and not LGPL or even MIT or BSD? And in particular that there isn't a reasonable linking exception? My impression from the summary is that he's merely linking said FOSS libraries, and my (much less founded) impression from casual observation is that using FOSS libraries is usually ok so long as any modifications made to the libraries and redistributed are done so following any viral licenses that might apply.
But the question here is whether they can claim copyright on the code he wrote before he was working for them. I think the answer is no; I have a friend who successfully claimed personal ownership of patents that a university wanted dibs on for similar reasons. In that case, the code he wrote while employed by them is owned by them, but can't be distributed (probably even internally -- you are making copies, after all) without putting it under the GPL, unless they hire someone to re-write all the code they don't own.
But of course, the correct answer is always, "Consult a lawyer".
TCP: Why the Internet is full of SYN.
If you are an employee, then the software you wrote for them belongs to them. If you were a contractor, then the work you wrote for them belongs to you. Any GPL software that is published MUST REMAIN GPL. Attempts to claim proprietary rights to GPL software have failed before. Its a place even Microsoft will not touch. If they use it for their own use, they can do whatever they like. Attempts to publish GPL software as proprietary, will get a call from Harald Welte at GPL-violations.org. The next call will then be from one of two sets of lawyers. It could be the Free Software Foundation calling, the Electronic Frontier Foundation, or Eben Moglen (depending on exactly how nasty things are getting). Being a university, I suspect that they already know about this. If they don't they either are not much of a university, or they are in for a world of hurt.
If it's not screamingly obvious, Google run their own Linux kernel, which probably contains more secret sauce than anything else they've written.
Matthew @ Bytemark Hosting
If I read this right, you started the project on your own. When the university found it they brought you on to develop it.
If you had already released it via GPL then, to my understanding, it was a pre-existing work product and they can not claim ownership of it. Already being GPL'ed it should have been understood that the work being done would not violate the existing licensing.
IANAL but I do know that a company can not hire you then claim ownership of work you did before you were hired.
That may not be on purpose.
-mkb
If it's based on GPL code and they don't want to release the whole thing under the GPL, they'll need to rewrite the sections under the GPL before they can have their way with it.
I do want to point out the key to your entire statement there. The key word is, "release." If they want to use the effort for internal consumption, they are free to do so and are not required to every make the code publicly available. But, assuming the code is GPL'd, if they are publicly releasing binaries, they are legally obligated to provide the source.
If you work in a country which has signed the international copyright agreement - the copyright belongs to creator and can only transferred by an explicit contract, implicit doesn't work. Especially photographers have won many cases in court - why anyone even tries anymore is beyond me!
One common mistake here is mixing copyright, license, ownership, etc. Think about a painting made by order - it's almost impossible to move the copyright but, of course, whoever ordered it owns the painting. Totally different issue. But don't try to copy it - the artist will come after you very fast! Yes, we have built a complicated world.
Now - QuantumG is right, read the replies. GPL is a distribution license, period! Very nice, very easy to understand license - except if brainwashed by marketing or "free software" sides! As a copyright owner you can select whatever license, change it whenever you want but (in most cases) can't take back old except if there is a contract agreed by both sides (!!) which includes the clause of license revocation.
O.K. So the exception is for non-commercial redistribution under 2(c) if one received it under 2(b).
2(b) is a bugaboo for many commercial interests: they generally don't mind providing source on demand, but prefer to only have to do it to those to whom they have licensed binaries and not all comers as 2(b) allows.
GPL 3 is more liberal and business friendly in this regard.
In Liberty, Rene
No. You read GPL 2 2(b) incorrectly.
If you provide binaries and source, then you are correct.
But, if you provide binaries and an offer of source that offer is transferable. Then, anyone who gets binaries from anyone else can demand source from you.
In Liberty, Rene
In that case, the code he wrote while employed by them is owned by them, but can't be distributed (probably even internally -- you are making copies, after all) without putting it under the GPL, unless they hire someone to re-write all the code they don't own.
Under US Federal jurisdiction it is clear* that the GPL allows for unrestricted copying and use within an organization of GPL code without any obligation to any third party. If that organization distributes it to anyone outside of the organization then they would have obligations under the GPL. This was part of the intent of the GPL by the way.
*The number of words in the GPLv2 with no legal consensus on what they mean is staggering. "Distribution" for example has some defined meaning, however about half of the questions you might have about the meaning are completely undefined.
Up until the point where you got hired the work was entirely yours.
At the moment they picked you up, your contributions became work for hire and they became a secondary contributor with you as their agent.
The code is jointly owned by you and the university.
Them hiring you doesn't trump any of the work you did solo before getting the job.
Just the same though, getting your neck breathed down by a high powered legal department can change things in a hurry. Unless you have solid proof you worked on it before getting hired they will most likely be able to muscle you out of your rights anyway.
"uses GPL-licensed libraries. "
That phrase was brought to you by the department of redundancy department.
The code doesn't technically belong to anyone, but the rights to it do.
Just because it CAN be done, doesn't mean it should!
Is it possible to do two distinct forks simultaneously, if you're the one doing the coding on both forks? Couldn't your employer argue that your contributions to the personal fork are inevitably derived from the code you wrote for their fork? And if you write your fork first, and then soon thereafter write the employer's fork, isn't the employer's fork inevitably derived from your personal fork, since you wrote both?
I think a single person simultaneously (or even with weeks) writing both forks is a bad idea, at least from a legal "who owns this code" standpoint.
Following this suggestion is asking for legal troubles.
It's difficult to separate when you're validly allowed to develop for the open fork, and the employment fork.
However, if you want massive legal bills, this could work exactly the way you're describing it.
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
Um isn't that really a question for a lawyer? I know here at Slashdot we all consider ourselves lawyers,but the fact remains we are not lol.
Jack of all trades,master of none
It wasn't a suggestion... I was pointing out exactly what you're saying - it's a bad idea. Read my last sentence again.
Of course if you didn't sign it away, you retain copyright over what existed before you joined.
93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
While I understand the idea of copyrights not being bogus.
There is a legal framework, which we are dealing with.
That legal framework describes ownership of interests to distribute a work.
Actually, there are numerous incorporeal/non-physical interests that can be transfered and traded, and IP rights are not the only ones.
Real property oddly enough functionally amounts to a set of interests and rights rather than the actual property itself.
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
*facepalm*
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
The employer can only claim copyright over the portion of the work that was created under their employ. However, the sticky bit is that they licensed the original work under the GPL, so they must not distribute their additional code and, if they do, they must make it available under the GPL AND share copyright on the code with the original author.
Yes, and perhaps another way of putting it is like this. The contract between the employer and employee can obligate the employee to transfer his rights. But in such a transfer the employer can't receive wider rights than the employee had in the first place before he handed them over.
-wb-
Here is an easy workaround: request copies of the binary and / or source sent to a home email address, under some pretense. Quit the company before the email is sent. Congrats, you now have full distribution rights.
Fundamentally, the appearance of wrong doing is important not just wrong doing. You should take that into account along with the worth of the code. This is your reputation.
Now, the code you wrote before you joined the department you own. Unless there was a written conveyance of that copyright (which likely also included a special payment to you, a registration cost for you, etc). I am assuming they don't own it for another reason you haven't mentioned like you used their equiptment, or some student code you agreed to allowed them to claim ownership of your work while attending their school, etc ...)
Now, you may or may not have entered into a verbal agreement to license the code to them if that was a condition of hire. (likewise for copyright, but it sounds like you know you didn't enter an agreement to transfer that) ... You should formalize that if you did.
Technically you've likely never officially licensed some amount of code to them, and they own enhancements on your older code.
My opinion is given them a free non-revokable license to the original code (MIT, BSD, apache, etc) and take a loss on the rest. You can then redistribute the old code. Then they know what they own, you know what you own, and both of you know what needs to reimplemented to have a single copyright.
Your next project's code will be better. My advice: Protect your reputation and let people know you are serious about these things and 'straight' laced. Don't bully people, just do what is right and proper.
I'm not a lawyer, and hate acronyms, but this is my two cents of understanding here:
1) You worked on this project (henceforth "the Project") for personal reasons and on personal time.
2) You were later hired to develop the Project into a specific solution (henceforth "the Solution") required by a local university (henceforth "the University").
3) The Solution's size became daunting and you felt it would be wise to publish it to the open source community (henceforth "the Community").
4) You proposed to your project lead that the Solution be published to the Community.
5) Project lead made it clear that this is unacceptable, and that the Solution is sole copyrighted property of the University.
6) You still wish to release the Project to the community.
Assuming this is all accurate, then I believe that sole and exclusive copy-right relative to the Project as it existed prior to your employment by the University is yours and yours alone. You are free to release to the Community the Project as it existed prior to your employment by the University, and leave the University in possession of a fork or branch of the Project which meets the Solution they employed you to produce. This is my understanding.
As a university, they have little to gain by holding any sort of research they engage in back from the public. It is likely that releasing the Solution to the Community would result in termination, but as long as there is proof that the Project predates your work on the Solution, they would have no reason and (I believe) poor legal footing if they attempted to stop you from releasing your work on the Project before they employed you. Of course, you are obligated to inform them that under the terms of the GPL, which covers the Solution due to being incorporated in the Project and, by extension, the Solution which is derived from the Project, that if this Solution's binaries ever leave University hands in any way (whether it is sold or distributed for free), the University is required to provide full access to all of the source code. Their only recourse to this is to rewrite the entire Solution to use nothing under the GPL, and you are probably free to tell them that you will not be involved in such a project.
Likewise, you probably ought to make full disclosure if you do release the Project as it existed before the University hired you. It's only common sense and manners (though, admittedly, a "bad idea") to tell the University that though they are not allowing release of the Solution, you are going ahead and releasing all work you did on the Project before the University employed you to create the Solution. Provide a time frame in which the University may object and show you what they consider to be part of the University's copyright within the Project's source code, along with documentation that their claims are accurate, and make clear that when this time frame ends, all copyright of the remaining source code for the Project belongs to you. Make sure it's a reasonable time frame for them to review and verify that the Solution you produced for them is a derivative of your Project, and that anything within the solution that matches up with the Project originated first in the Project before you worked for them to create the Solution, and that they are only able to lay claim of copyright on portions of the Solution which you produced while explicitly in their employ.
Best advice: Visit a lawyer and see if he or she will represent your concerns in this when you tell the University. Preferably, of course, a copyright lawyer. If you lawyer up on this, the university may back down quietly and either allow release of the Project as it was before they employed you, or the Project stripped of the specifics of the Solution, or maybe even the Solution itself. Get other faculty and staff members on your side, if you can, and you may be able to avoid the need to lawyer up by getting the faculty and staff to put pressure on the University (or at least the department) to be fair with their use of open source or licensed coding work. After all - they paid you to build on an existing program, not to build a new one from scratch.
Why do employers pull this crap of "everything you create I own."
There's usually a little agreement they try to make you sign that gives them the right to do this. Now I don't do GPL, but my software is not exclusively owned by my customers either. So I just cross that thing right out on the page and tell them:
"I'm sorry, I cannot agree to this portion -- it would be impossible for me to abide by this agreement because I already have a large library of well-written and tested software functions and routines and algorithms that I use and share across projects outside of your business that my other previous customers have already paid for the right to use. And I am not going to sit in a chair and re-invent a SSN checking algorithm or a phone number validator simply because you want exclusive rights to it when the work has already been done, and been done better (I'm totally not interested in re-inventing wheels). But also in return you will someday get the benefit of something someone else previously paid for as well. So you see, I cannot possibly give you EXCLUSIVE rights to my work because they already don't exist. Now, I will be happy to provide you a license and/or right to use/sell the software I create, but this is simply the best I can offer."
They usually just initial the section I cross out and go with it. It's not worth a fight for them, and I won't take a job that would force me to do that. And I suggest you shouldn't either.
"They said I probly shouldn't fly with just one eye," "I am Bender. Please insert girder."
It can be vague and State-dependent, but code developed for an employer can be considered a trade secret. Discussing it in the wrong context can be considered "breach of a confidential relationship" and raise the possibility of getting sued. The main issues here are whether aspects of the code are "valuable" "secrets". The fact that this code is not published makes the actual code secret. If the secrecy adds value to the product (like the formula to Coke) then it is possible to breach that relationship. As long you are not revealing specific code or data, the discussion is most likely fine. This is discussed briefly in the excellent book, "Intellectual Property and Open Source". I would love to see a broader discussion, it wasn't enough to answer my questions on the topic...
A similar case where you might get into trouble discussing the code is if it is a national secret. I recall a case a couple years ago where an academic scientist discussed non-classified publicly available information with his Chinese student (regarding a flight system, I think) and ended up in jail for revealing national secrets because of a small related grant he had worked on.
Since this is way down at the end you'll never see this advice.
Sit down with your boss and talk it out. If your boss doesn't understand the GPL, explain it to him. Explain that if the University plans to distribute this as non-free software, you will need to reimplement a significant portion of the code. Give him an estimate of the time you would need to do it. If they are selling it, make sure you are on the author list registered with the University intellectual property office.
If he doesn't plan to distribute it, ask why not. Are their trade secrets in the code? How much time would it take to remove them? Who paid for this code? Do they require open distribution?
If you were hired because of your work on these libraries, your employer should have understood the licensing issues in using them in advance. Also let them know you were never told to avoid GPL libraries in your development efforts.
Final effort, if you can't reach an agreement, and your employment has ended, contact the University's legal department and tell them that you are worried that you boss will be illegally distributing this software. They aren't going to take your side, and they aren't going to give you GPL distribution. But they will make sure that your boss doesn't distribute this software.
Support SETI@home
Eh, this whole conversation really begins and ends with, "Not enough information".
What parts did you do before they hired you. Did you release that under GPL? Obviously the stuff you did for them belongs to them, but there may be limitations on their ability to distribute it. Is it worth creating another example of "poisoning" code with the GPL virus? It may well be spun that way.
Maybe your code just isn't worth a black eye or even the cost of a court battle? Too little info all around.
Because from the legal definition of "distribute", if the University owns the computer that the software is on, they haven't distributed it. So, the employee has no legal basis for demanding the source code.
The truth is that all men having power ought to be mistrusted. James Madison
They own the part you did after. However, they cannot distribute the combined work without your permission. If the program includes any GPL code written by anyone else they cannot distribute the program without either complying with the GPL or getting the author's permission. If the program links to any GPL libraries (not LGPL) they cannot distribute it without complying with the GPL.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
"Let's be clear. You have no rights to do whatever you want with the code you wrote for them."
What if they distribute the code to *HIM* -- then the GPL gives him rights. No?
Why can't that employee use the GPL to demand the source code to that supposedly "internal only" executable? Then, why can't that employee say "The GPL prohibits adding more-restrictive terms to the executable than the terms of the GPLed libraries." and then say "Prohibiting me from distributing this now-GPLed executabile and its source code worldwide is itself an additional restriction that neither the author nor the university can impose on me." And then convey/propagate/distribute the executable and its source code worldwide. The bits & information want to be free.
If your company provides you with a copy of Microsoft Word for you to use, you have no rights to that copy. Just try quitting your job and demanding that you can take that copy of Microsoft Word with you. If your company provides you with a copy of some GPL'd software for you to use, you have no rights to that copy either.
Should you take it on yourself to distribute the software then you are in deep shit. The GPL puts requirements on people making copies. The company didn't make copies, so there are no requirements on them. You made the copies, so you have to provide people with the source code, but you can't - the source code isn't yours, and your company will likely not be sympathetic with your cause.
IANAL, but the Affero GPL might offer interesting solutions to this issue. It could be interesting to build on software available under the Affero GPL and run the software you're developing as a service from the beginning. That way a third party might have the right to get a copy of the software and the source code, or not, IANAL.
Similar but subtly different.
I developed some software privately for several years, that I then brought to my current employer. I have continued to develop it there partly in work time, partly in my own time.
I now want to distribute it but am concerned what claims my employer may have. The main points about this:
My employer is a university so I am hoping they will be agreeable to open sourcing it, but I want to understand my rights (if any) before discussing it.
Did not Judge Kimball rule that as the law states "must have written and exact" text that copyright was transferred.
If you have proof of you prior code [all of it] they have no "global squatting rights" to it, the we own everything you have done non-sense.
Now what you did from the time forward, and this is still contested if you do something after hours, belongs [copyright] to them.
Or they can choose not to release it and just use it internally. Nothing in the GPL forces you to release your derived work - only if you do, it must be compatibly licensed.
I'm pretty sure that "having access" is not the same as "distributed to". If it is used internally in any organization, the IT dept. would "have access", for instance. The GPL only covers distribution, and if they are only using it within the organization (even if in different buildings or cities) then the GPL never comes into effect.
Best example is Google, who has many data centers, thousands of tech's who have access, running GPL code on tens of thousands of boxen. They never have to release kernel modifications at those locations because they aren't "distributing" the code, just using it within their own organization, in many different locations. They are NOT "distributing" it to those locations or anyone else, so the GPL never comes into play.
And the organization CAN make it a requirement that you never release any code that you are being paid to produce, even if it is for a program under the GPL. You don't own the code you produce for pay, the company does. Even if you own the original code, you don't own the changes (unless contract says otherwise) so you wouldn't have the authority or ownership to release any changes to the original base code, and technically, those changes are NOT forced to be licensed under the GPL until you distribute them. If you never distribute them, and then replace all previous GPL code with proprietary code, then it can be distributed under any license you wish, even though you developed it (but didn't distribute it) using GPL code.
The GPL doesn't restrict USAGE, only distribution. As to usage, it says you don't need a license to use it unrestricted, and this includes using it as a base for other programs under a different license as long as you remove the GPL portions before distributing.
Tequila: It's not just for breakfast anymore!
lulz
This varies from state to state.
In california it's a use of common sense.
If you do it on your own time and and on your own equipment, AND it is not something that could be considered your principle line of work for the company, then you are clear by law (though they can still take you to court and make your life miserable).
BUT if any of the above are not true, they may have some partial or complete interest in your work.
IF you work developing game code and develop a game engine, then they might have claim to that,
but if you develop database code or compilers, then more likely not.
Not all states have their head screwed on str8 in this regard.
In some states, contracts to prohibit re-employment in the same field (so you don't take company secrets to a competitor) after you leave for a year or more are legal, but not in California. California realizes that in our economy, you walk out one door and into another at the drop of a hat. That DOESN'T mean that taking of previous company secrets is ok -- just that it will be presumed that you will keep your prior employers secrets, secret.
In short...you'll have to check your state laws.
I think the point moreso stands that the GPL says that if you are unable to fulfill this license, you can't use the accompanies software in the first place. So it's not "What do I do in this pickel between my employer and the license now?" -- it is "I shouldn't have taken this contract" (or at least fulfilled it in a different way)
GPLv2sect3para0 You may copy ... the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: [3 ways of making source code available]
Let us reword that quotation: OP's university may copy the Program only if the OP's university enacts one of the GPLv2's 3 ways of accompanying that copy with source code or the offer to obtain the source code. Via the wording of this quotation, no distribution outside of the of the OP's university is needed to trigger this provision. Copying of any kind triggers the source-code obligation.
GPLv3sect6para0 You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: [5 ways of making source code available]
Let us reword that quotation: OP's university may convey the Program only if the OP's university enacts one of the GPLv2's 3 ways of accompanying that copy with source code or the offer to obtain the source code. Via the wording of this quotation, no distribution outside of the of the OP's university is needed to trigger this provision. Conveying of any kind triggers the source-code obligation.
He'll have to prove that his work was done before his employment
This is why my private projects always start with a visit to the "Create a new project page" on SourceForge. That way no one can take them away from me.
And this question is governed by the work made for hire doctrine (http://en.wikipedia.org/wiki/Work_for_hire). Ownership depends on whether you are an employee or an independent contractor. Which of these two you are depends on separate analysis. If you are an employee then the boss owns the lot. However, if you can prove that you are an independent contractor, then the code belongs to you because it is not in the 9 statutorily-defined categories in Section 101 of the Copyright Act. Interesting question. -- Noah Note: I am not an attorney and the preceding comment is NOT intended as legal advice.
IANAL, get your own lawyer, etc. etc ...
This seems to be a copyright case, and the GPL issue is just confusing here.
1 - The copyright of your original code was not transfered to anyone unless there is a specific contract signed by you stating that. I assume that your employment contract did not mention this code, and if so the original code's copyright is yours.
2 - The copyright of the work you did while employed at the university is (usually) copyright of the university. HOWEVER this is only the bits of code you did while working there. The remainder is still yours. AND...
3 - copyright of a derivative work is stil owned by the copyright owner of the original work. You are the copyright owner of the entire package. At most the university may be able to claim joint ownership due to the new bits added, but NOT sole ownership.
1+2+3 means that in litigation you would be able to stop them doing anything with that code. However (because of 2) they would also be able to stop you releasing the whole thing. They could not stop you from releasing the original code (because of 1).
So in litigation you can reach a deadlock and stop their interests. However this is a case of common sense, above all. Do you want to litigate against your employer? Almost surely you will lose your job in that case. The best way out of this, as some have also said, is to talk it out with the employer, making your point that it would be better for everyone that this is open source. If your direct supervisor (project manager, prof, etc) does not give in, try to talk with someone else, like people in the research office or maybe even a Dean. They may have solutions (and they don't want a fight), but when you do try not to be adversarial or it will just make people against you before they hear your points.
Note: I know this story too well: I am a Prof, and in the past have done the same thing as you (ie take code that I own copyright across several employers). Fortunately I got a letter from my first (uni) employer stating that the copyright of the code was mine, and from then on I have the proof of ownership established and any of the other employers just have to live with that. Now the code is joint owned by me and a few other employers... (and is open source)
Honestly, if you were working for me, I would fire you. I am a licensing and IP expert (I do that for a living). You had no right building a GPL based project for an employer without their permission. Most employers go way out of their way to avoid copyleft licenses that will result in their having to comply with terms that are not favorable to them. As for the many uninformed opinions here, such as "contractors are not employees," etc ... there is some truth to that, but then you are under contract.
Have to disagree - I've been exactly there - though I'm in Canada. I would expect the legality to be very similar where you are though, so this may be worth looking into. I think what others may be overlooking is the fact that this was done for a university. With respect to the creator of the work, educational institutions generally do not have, and should not try to enforce IP ownership in the same ways that private companies do. In this case the employer does own rights on the work since they paid you for it, but as the originator you also retain rights to it. Search your university's charters for the term 'sponsored research'. I would say that either you or the university could redistribute the work, but that it would have to be done under the terms of the GPL. Within that framework you could even profit from the work provided that you do it transparently and in good faith - which means informing the other party of your actions.
I think you meant GPL2 3(b), but I stand corrected. You have to make a written offer valid for 3 years from the date of your original distribution. I am not sure how this would be enforced if the first party is the original author, as the only person who can legally force the first party to comply is the copyright owner, (such as in this current discussion). I'm not even sure how you could prove the date of the original distribution (1st party to 2nd party), making this a difficult provision to enforce. It can't possibly mean 3 years from the distribution from 2nd party to 3rd party, as that could take place 5 years after the 1st party to 2nd party distribution.
This means that *technically*, the original author can be in violation of his own license, by simply refusing to provide source to a third party.
Tequila: It's not just for breakfast anymore!
Yes, GPL2 3(b).
Clearly if the distributer is the copyright holder, yes, no one other than him can enforce the license, and, as the copyright holder, he can relicense as he wishes. So, the paradox of being in violation of his own license does not apply.
However, where one combines code with GPL2 code, and distributes the combination, one MUST distribute under the terms of GPL2, and the copyright holders of the OTHER parts of the combination can enforce the license on the distributer.
This holds for ALL (re)distributors.
So, if C adds code to GPL2 code copywrighten by A and B, and distributes the result on Jan 1, 2010, he must include an offer good to Dec 31., 2012 to provide source to all comers who show they have binaries and a copy of C's offer. This is because GPL2 requires C's offer to be transferrable.
Now, if D further redistributes binaries received from C, he must either (a) provide source (which he got by holding C to his offer), or (b) provide his own offer good for three years from when D distributed (and this is true for every time D distributes), or (c) transfer C's offer (and only if D's distribution is non-commercial).
I agree that if the offer does not specify an expiration date, determining what it is requires determining when the distribution occurred. While a small burden, it is not impossible to demonstrate by a preponderance of the evidence.
This can actually be a pain in some cases where commercial interests want to distribute code licensed necessarily under the GPL, but have not yet developed the means to neatly package source and a convenient build mechanism. The classic example is a firm distributing GPL works in progress to contractors.
I asked RMS about that situation, and his position was that if the contractors were using their own computers and not computers provided by the firm that hired them, it was considered distribution. Neither of us is a lawyer, but I think that position is correct.
I've also been in positions where recipients of GPL code did not want source and we did not want to provide an offer (to comply with the GPL) because we did not like the transferability provisions. In the end we shipped them a CD and offered to pay return shipping for them to send it back to us at their discretion.
In Liberty, Rene
Ask them nicely if you can have a copy of the software for personal use, get it in writing. If they give it to you then they have distributed and assuming that the GPL would apply to that code if distributed then you can do what you like with it.
Thanks for the detail info, that is one of the nuances of the GPL that isn't obvious at first glance. I still have one problem that you are free to ignore if it doesn't interest you, but the issue seems real, even if unlikely. Here is the oversimplification to be perfectly clear in my meaning:
Bill writes a program and gives only Alice the binaries but no source. Bill has included a copy of the GPL license with the binaries and it is obviously GPL licensed. One year later, Alice needs to modify the source, and asks Bill to comply with GPL 2, 3(b) and provide a copy. Bill says he changed his mind about the license and it is now closed source and refuses to give Alice a copy of the source. He offers to sell her a restricted copy for $50,000 instead.
Bill can't relicense the copy he gave to Alice after he has already distributed it, that would be taking away Alice's right to redistribute under her current GPL licensed copy. He can change the license on FUTURE copies that HE distributes only, but he can never "unlicense" a copy that has knowingly and deliberately distributed under the GPL in a retroactive way. (This would be true regardless of the license, even Microsoft only changes the license with click through updates that you can refuse) Alice is metaphorically held hostage if she can't take legal action against Bill for refusing to comply with the GPL. Even though she is not the owner of the copyright, she can show she has been harmed by Bill's refusal to comply with the license of the software she received.
While not a common situation, the more the GPL gets used, particularly on smaller 'for hire' projects, the more likely this situation could occur. Perhaps the program made Alice $1M on her servers, and Bill just wants a cut, the reason doesn't matter. While it is easy to say "always get the source when you get the binaries", it is easy to overlook on a busy project when you hear "I will send it in the mail next week" and you aren't expecting to make changes any time soon.
Academic, perhaps, but troublesome. Thanks.
Tequila: It's not just for breakfast anymore!
That's easy. Bill gave Alice a license which gave her certain rights, including the right to demand source from Bill. She has a cause of action if he refuses under contract law (IF money or other "consideration" changed hands making it a binding contract).
Basically. Bill's rights stem from his copyright, and Alice's rights stem from the license Bill gave her.
Now, because Bill wrote the code all by himself, he is not obliged to license it to Alice under those terms. In fact, he can license it to Alice under restrictive terms, and to others under the GPL, and Alice could not demand he provide her source because her license did not give her that right. Further, she couldn't demand anyone who DID license the code under the GPL give her source either because they did not distribute to her!
Of course, if distribution is widespread, Alice might be able to get a copy of the source eventually, but she has no right to it.
Now, lets say Bill licensed the code to Alice under GPL2 3(b) because he had to in order to distribute to her as a "derived work" of someone else's GPL2 licensed code and no money changed hands. It would be questionable if Alice had a cause of action against Bill for violating the license. But, the copyright holders would have a cause of action against Bill for violating their copyright even if no money changed hands when their code was distributed to Bill, because his right to redistribute derived works was restricted by the license he got.
So, you can't violate a copyright without a license (which does not require consideration), but you can't enforce a license you receive without having paid consideration for it. One can freely give up rights without consideration, but one can not enforce rights gained unless they paid consideration. At least that's as far as my NAL understanding of contract law goes (there being an implied contract when the license is granted in exchange for money or other consideration).
In Liberty, Rene
Oh, Alice having "no right" to source above, means she has no cause of action to demand it. She does have a right to have it if she obtains it through someone other than Bill.
Basically, if I say you can do something, and you do it, you can do so with impunity: I can't change my mind after the fact unless I rescind my permission. But, if I promise you something (future delivery of source on demand under GPL2 3(b)), and you don't pay me consideration, you can't enforce that promise. Others, however, may.
In fact, GPL has specific sanctions for those that do not redistribute according to the terms of the license: their right to future redistribution can be explicitly rescinded. Further, statutory sanctions under copyright violation can also apply.
In Liberty, Rene
GNUv3sect6para0You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: [5 methods of providing the source code]
Why are you fixated on the word "distribute"? Instead, you should be fixated on the word "convey" as actually used in GPL as quoted above. Legally "conveyance" does not need an underlying "distribution", even though usually "distribution" needs an underlying "conveyance". Please read the GPL itself. But don't take my word. Let's use the GPL's own definition of "convey" and "propagate" to see whether there exists a method of conveyance in which no distribution occurs or whether there exists a method of propagation in which no distribution occurs.
GPLv3sect0para5 To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying , distribution (with or without modification), making available to the public, and in some countries other activities as well.
GPLv3sect0para6 To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
If the university has copied OP's Program from whereever OP stored the Program to the local hard disk of at least one user's computer and granted that user at least read permission to the Program that "enables" that user, "a third part", "to make ... copies", then by GPLv3sect0para6 the OP's university by an overt act of its own volition has triggered the source-code obligation to that user via mere copying/conveyance to that user's local hard disk without any distribution whatsoever outside the OP's university. That user shall now be in possession of all members of the set {OP's university-paid-for/university-copied binary, OP's university-paid-for source code, OP's pre-employment source code, underlying GPLed libraries' source code}. (Unless that user has consumated a signed side contract with the OP's university outside of the GPL as per GPLv3sect2para1sentenceFinal), under the freedom-rights granted transitively by the chain of copiers via the provisions of the GPL, that user then may now publicly distribute to humankind the OP's binary and OP's source code from which this binary is derived as a derivative work.
Source-code freedoms preserved transitively without distribution performed by OP's university itself or by OP herself. QED. The bits & information want their freedom. IANAL.
You actually quoted the relevant section
GPLv3sect0para6 To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
The user in your scenario who is using the software on a University computer has not received a copy of the software. The copy of the software is on the University computer.
The truth is that all men having power ought to be mistrusted. James Madison
But what happens if I release a GPL'd library, and your company uses it in their product? Once they have split and distributed the source + binary to the spinoff company, this means a program using my GPL'd library has been distributed. Does that mean I, as the library author, am also entitled to a copy of your source?
GPLv3sect6para0 any any any any kind of propagation that enables enables enables enables other other other parties to make make make make ... copies copies copies copies [obligates the propagator to make the source-code available in one or more of 5 listed ways]
What on earth do you think that "any", "enables", "other parties", and "make copies" mean in my scenario in a prior posting along this thread other than the following: A) If the OP's university were to have installed OP's binary Program on the local hard drive of the computer that the university authorized that user to utilize, and B) if the OP's university were to have granted read permission to OP's binary Program files on the local hard drive of the computer that the university authorized that user to fully utilize, and C) if there were to have not existed a side-agreement contract between the OP's university and that user that would have prohibited that user to make further copies of files on that local hard drive (especially copies that fall outside of the perimeter of the university), then under concomitant A & B & C the OP's university would have made a copy---where that act of copying is permitted only under the terms & provisions of the GPL---for which the university is legally responsible under the law (i.e., meeting the GPL's definition of "propagation"). In this scenario, did the OP's university lock down OP's binary Program out of sight of the user and throw away the key? No, in this scenario the university overtly granted read/copy permission to the files of OP's binary Program on the local hard drive that the university provided to the user.
The university rolled out the royal red carpet to the user to enact the very purpose of the GPL: to get the source code so that the user can maintain the user's own software freedom herself. Let us count the threads in this red carpet. The university funded the development of a GPLed Program. The university continued funding the development of that GPLed Program after being advised of the underlying GPLed libraries that cause the whole binary Program to be GPLed, rather than replace the GPLed libraries with non-GPL analogues. The university provided the user with a separate univerisity-owned computer, rather than merely an account on a time-share minicomputer, which could have permitted the university to avoid making the local-hard-drive copy by utilizing a single shared instance of the binary Program. The university provided that computer with local hard drive, rather than merely a diskless-booted remote filesystem, which likewise could have permitted the university to avoid making the local-hard-drive copy by utilizing a single shared instance of the binary Program. Did the OP's university make a policy prohibiting the use of OP's binary Program punishable by the death penalty? No, the university overtly authorized university personnel to copy the GPLed binary Program onto that hard drive, which can be performed legally only via compliance with
You are absolutely correct to conclude your post with "QED. IANAL", because your reasoning clearly demonstrates that to be the case.
The truth is that all men having power ought to be mistrusted. James Madison