Recently, management has announced their intention to switch the project I am working on to open source, "probably that new GNU license, because it's supposed to be the best."
Now, I like this job, a lot. Good people, easy atmosphere, and it's not profit-driven. However, if they finish this changeover, professional ethics will force me to leave... and I can't really afford to lose this job, knowing how long it took for me to find this one.
My question is this: What method can I use to prevent management from open-sourcing this project? Should I try to appeal to their ethics? Should I point out the flaws and unenforcability of the license? Or since this project will (by necessity) involve working with people's private data (including medical information, at times), can I somehow legally prevent them from copylefting the project?
Any help you could give me would be appreciated.
Post a Comment
You point of view is one not held by the majority of people on this site. If I may ask, what are your ethical objections of Open Licenses?
I understand that data obfuscation is easier to implement in a closed environment, (Security zealots non-withstanding) but are the any other professional issues that you have?
For info about challenging open source licenses, perhaps the FCC ruling regarding Software-defined radios (47 CFR Part 2??) may help as a legal precedent.
[The conversation comments are broken btw.]
Let's adress your points one by one.
1) There is a risk that making your code open source will reveal holes in the software, but seeing as it is the programmers job to make secure software, I guess that you can't use that as an argument to your bosses.
2) You are wrong. The GPL simply does not cover information/documents produced using GPL software. Making a document or storing information using GPL does not constitute making a derived work.
3) see 2.
4) I think that there are a great many companies who would employ people who worked on GPL code. Only idiots or anti-GPL zealots would take this stance. Hell I'm sure that Microsoft have employed programmers from GPL projects.
5) Well, I understand that you don't think the GPL ethical, but we are trying to dermine why you think it isn't Ethical in the first place.
6) Well, there are allegations that Microsoft, Canonical, Red Hat, IBM, Adobe, Amazon and most companies have broken the law, and copyright. However the GPL has no particular link to this. And I think that Google is a good example that using and creating Open source solutions does not unduly hamper profits.
7) see 2. e.g. Using Linux, or Open Office does not make all your personal documents open source.
'Derivative works' means using GPL source code to make a new program. NOT using a GPL program to create a document/store information.
8) If this were true, then this would have been your bargaining tool to use with your bosses. However, I just read the Code of Ethics, and the GPL does not violate it in any way:
1.5 Honor property rights including copyrights and patent.
It is for this reason that most Linux distributions do not bundle MP3 codecs or other patented. The GPL does not say that it is right to ignore patents or copyright. If anyone explicityly publicises a valid patent claim on any community-maintained GPL code, I am confident that it will be immediately removed, or a work-around written.
1.6 Give proper credit for intellectual property.
Look at the Linux kernel changelog. Each commit is attributed to the contributing author, bug-reports are attributed. Most GPL projects include a list of contributers which explicity gives proper credit for IP
1.7 Respect the privacy of others.
1.8 Honor confidentiality.
Privacy is not eroded by the GPL (see 2.)
As for confidentiality, that is up to each project's maintainer and is in no way linked to the GPL.
I'm not sure that you will win an argument with your bosses without having a clear, and precise knowledge of why the GPL is unethical. Once you have this, then you can present them to you superiors for an open debate.
Let's adress your points one by one.
1) There is a risk that making your code open source will reveal holes in the software, but seeing as it is the programmers job to make secure software, I guess that you can't use that as an argument to your bosses.
2) You are wrong. The GPL simply does not cover information/documents produced using GPL software. Making a document or storing information using GPL does not constitute making a derived work.
3) see 2.
4) I think that there are a great many companies who would employ people who worked on GPL code. Only idiots or anti-GPL zealots would take this stance. Hell I'm sure that Microsoft have employed programmers from GPL projects.
5) Well, I understand that you don't think the GPL ethical, but we are trying to dermine why you think it isn't Ethical in the first place.
6) Well, there are allegations that Microsoft, Canonical, Red Hat, IBM, Adobe, Amazon and most companies have broken the law, and copyright. However the GPL has no particular link to this. And I think that Google is a good example that using and creating Open source solutions does not unduly hamper profits.
7) see 2. e.g. Using Linux, or Open Office does not make all your personal documents open source.
'Derivative works' means using GPL source code to make a new program. NOT using a GPL program to create a document/store information.
8) If this were true, then this would have been your bargaining tool to use with your bosses. However, I just read the Code of Ethics, and the GPL does not violate it in any way:
1.5 Honor property rights including copyrights and patent.
It is for this reason that most Linux distributions do not bundle MP3 codecs or other patented. The GPL does not say that it is right to ignore patents or copyright. If anyone explicityly publicises a valid patent claim on any community-maintained GPL code, I am confident that it will be immediately removed, or a work-around written.
1.6 Give proper credit for intellectual property.
Look at the Linux kernel changelog. Each commit is attributed to the contributing author, bug-reports are attributed. Most GPL projects include a list of contributers which explicity gives proper credit for IP
1.7 Respect the privacy of others.
1.8 Honor confidentiality.
Privacy is not eroded by the GPL (see 2.)
As for confidentiality, that is up to each project's maintainer and is in no way linked to the GPL.
I'm not sure that you will win an argument with your bosses without having a clear, and precise knowledge of why the GPL is unethical. Once you have this, then you can present them to you superiors for an open debate.
Well, I understand that you don't think the GPL ethical, but we are trying to dermine why you think it isn't Ethical in the first place.
No; I need help trying to make sure the program (and thus, the data) stays secure.
This is not a joking matter. If this code gets open-sourced, it is going to ruin other people's lives, people who implicitly put their trust in me -- and no amount of FSF apologists knowingly misrepresenting the GPL on an Internet message board will fix that. Some way has to be found to keep this code closed-source, or the users will pay for it.
So, despite all those high-minded, misguided reasons for not trusting the GPL that you gave before,
you are really worried that your code will not stand up to public scrutiny? That someone will find your mistakes and exploit them.
Well, this is a difficult argument to push, because it is an implicit admission of bad programming. However, as I mentioned before, perhaps the FCC ruling: http://a257.g.akamaitech.net/7/257/2422/01jan20071800/edocket.acces.... may help you.
I doubt that you would have much success with any confidentiality laws.
There is nothing illegal in the GPL, or using it for confidential material, and it has been proven that GPL'd software can be made secure.
So the only time that this law could be used was if it could be proved that you were criminally negligent in implementing pertinent security measures in the software. And if that were the case, then the fact that you were writing open source software would have no benefit over closed-source software. As a court could order any source code to be disclosed anyway.






0 