Hacker News Reader

Comment by enz | Hacker News Reader

If your project is OSS, what prevents them from taking it and "force you" (as an employee) to work on it anyway?

Maybe a restrictive license may help: if your company takes the code and modify it, make them under the obligation of releasing the source code too.

What is the current license of your project?

Ultimately, nothing prevents you from deleting your public Git repo. You can decide that your project is not available anymore, it is your right.

View on HN

Deleting the code or putting a restrictive license in place doesn't change the terms of the employment contract if it has terms stating that they have IP to work done while working there.

The current license is Apache 2.0 so that's not helping.

> Ultimately, nothing prevents you from deleting your public Git repo. You can decide that your project is not available anymore, it is your right.

I don't think this is an option. They can still claim that they want the code because I created something that directly relates to what the company does.

If they have even a debatable claim on the code (probably not but are you 100% sure?), then deleting it is destroying their property.

That's a quick way to have a miserable life (getting fired, sued, blacklisted among peers, etc).

If it is a sude project that is related to your work I would say that is a good case for tge company (ianal though)

At least you are using the know how you gained during your work

Reply on news.ycombinator.com