3 ms·
I believe the person you're replying to was referring to section 2870 from the California Labor Code: https://leginfo.legislature.ca.gov/faces/codes_displaySect
by mgomez 6y ago
I believe the person you're replying to was referring to section 2870 from the California Labor Code: https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=LAB§ionNum=2870 https://leginfo.legislature.ca.gov/faces/codes_displaySectio...
"(a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer’s equipment, supplies, facilities, or trade secret information except for those inventions that either:
(1) Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer; or
(2) Result from any work performed by the employee for the employer.
(b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable."
- wahern 6y ago> Relate... to the employer’s business This is the catch-all and I've always been curious what the seminal cases are which apply this language. For example, the charter for most corporations these days usually establishes the business for "any lawful activity", so if the scope of an employer's business is defined by the charter, then pretty much any commercially viable FOSS project could potentially be ensnared by an employer. Any IP lawyers here have some pointers to how "employer's business" is supposed to be interpreted and applied?
- User23 6y agoYeah, if Judge Alsup got the case it might get a very different ruling than another judge.