Whenever this comes up, the question I have to ask is this: Has there even been a case in California where a jury decided that an employer owned the open source

Whenever this comes up, the question I have to ask is this: Has there even been a case in California where a jury decided that an employer owned the open source (or other software) an employee developed in their own free time? Has a company in California successfully litigated to take ownership and taken down an open source project because it was an employee’s side project? To protect myself, I have done the following: • I make sure, before signing an “inventions” clause, to put all of my open source on GitHub a date stamp before the date when I signed the inventions clause. This way, any and all of my own open source I use on the job (usually, a password generator, but I was once at a company with DNS so broken I had to run MaraDNS locally to have a usable Internet) is stuff I did not develop while working for the company. • I list all of my GitHub projects, state that none of them are related to what the company develops, and that any and all development is done on my own time, using my own computer.