Even worse: Depending on (local or national) law, it may be the company’s property, even if written in personal time. Especially if the code is in competition with your work.
Yes, it’s ass-backwards, but that’s how it is in some places.
Comment on I wrote a program for my boss. How legal is to to write the program again and make it FOSS?
scorpionix@feddit.de 1 year ago
Not a lawyer but from my understanding of intellectual property: You wrote it on company time, so it is the companies code. Publishing it without explicit approval would be copyright infringement.
NostraDavid@programming.dev 1 year ago
DroneRights@lemm.ee 1 year ago
The code on the computer isn’t what I would be publishing. I would be publishing the memories in my head, which I had written down again
remotelove@lemmy.ca 1 year ago
Don’t copy the code directly from any company assets. There are plenty of ways to track code and data theft these days, so don’t even attempt it.
Honestly, there is not much that a company can do unless they specially own the business logic of what you are doing. Are there aspects to the code that apply to internal proprietary software? That probably isn’t wise to share.
While I am not a lawyer, a general rule of thumb is that if you think you might be stealing something, you probably are. Anything you do on company time, is technically owned by that company.
If your previous work gets discarded by that company, never talk about it again. Never code it again for that company and just let the idea die, as far as that company is concerned. Independently resurrect the idea at a later date.
Nobody here can really tell you what to do, btw. Quite honestly, if you think that you can claim ownership of what you have, pay a few hundred bucks for a consultation with a lawyer.
GentlemanLoser@ttrpg.network 1 year ago
Good sensible advice right here ^
scorpionix@feddit.de 1 year ago
Doesn’t matter if you write it in code or chisel it on a stone tablet. It is still the companies intellectual property.
Think of it this way: You film a movie which for whatever reason doesn’t get published. This doesn’t give you the permission to write a book containing the same story, just in writing. The story is still owned by the film studio. The same reason applies to published material: You are not allowed to write a Star Wars story without approval from Disney, the copyright holder. Fan fiction exists in a gray zone for exact this reason.
Bipta@kbin.social 1 year ago
You're sort of missing the point. Two programming implementations are never the same if you rewrite them from scratch for anything but the most trivial program. It wouldn't be a copy of the original and it would have a unique, if similar, implementation. It's not as clear cut as you suggest (at least not for the reasons you suggest, but IANAL.)
boblin@infosec.pub 1 year ago
Legally it is quite clear. Taking a description of a closed source program and writing a new one is ok in most cases (unless that description is API docs - see Cisco vs Arista). Taking a look at closed source software and then implementing your own version is poison as far as OSS goes. OP implemented the first version, so that’s already a problem. They may get away is they describe what the program does to someone else and let them implement it, but OP would not be able to touch the source code
scorpionix@feddit.de 1 year ago
It is not about the code line by line, but the functionality that OP created for their employer. And yes it is not clear-cut in the sense that in Oracle vs. Google it was AFAIK decided that the idea of the
toStringMethod does not fall under copyright. However, a software that fills a specific need for a company and is then re-implemented/released by an employee? You can bet your ass you are in for at least a lengthy battle in court.beejjorgensen@lemmy.sdf.org 1 year ago
You can absolutely write a Star Wars knockoff, though. You just can’t call it that. There’s some gray line in there somewhere.
lemmyvore@feddit.nl 1 year ago
If you rewrite it in a clean-room approach and another language it will most likely not be in breach of copyright.
But there are many other aspects where you may be at fault: breaking confidentiality, using trade secrets, non-disclosure, non-compete etc.
My advice would be to have an honest discussion with the company owner and ask for the permission to open the code under a permissive license. Be prepared to explain what the advantages would be for the company, beyond “the code is just sitting there”. Be prepared to drop it if they say no.
If you go ahead it is quite possible you will be sued. Make sure you’re willing to risk it and spend time and money defending your project.
alonely0@programming.dev 1 year ago
–Not legal advice-- Except he can’t do clean-room development because copyright is viral. If he had access to the copyrighted source, any code he writes on the matter, if it coincides with the copyrighted one to some extent, can be pursued for copyright claims (IBM v. Microsoft). For example, when there’s a leak of Windows source, ReactOS devs get super scared, because it really puts them on the line. Another example is Nouveau, which can’t accept anyone who has worked at NVIDIA. That being said, the company was not intending to do anything with it, so they can’t claim damages; ergo, he’s completely safe.
DroneRights@lemm.ee 1 year ago
I’m not a he