Liste des Groupes | Revenir à s logic |
One problem I generally see is, that most people
are not aware, that an employee has no rights
on the stuff he writes for his employer.
Standard Rules:
- Work for Hire Doctrine: In most jurisdictions, code
written by an employee within the scope of their employment is considered a "work for hire," meaning the employer owns
the intellectual property (IP) unless otherwise agreed in writing.
- Employment Contracts: Most employment agreements
explicitly state that any code, inventions, or intellectual
property created as part of your job belongs to the employer.
- Use of Employer Resources: If an employee uses the
employer’s time, tools, or resources to create code, the employer generally owns the resulting work.
Exceptions:
- Independent Work: If an employee writes code outside
working hours, without using company resources, and it’s
unrelated to their job, they may retain rights. Some
jurisdictions, like California, have laws (e.g., California Labor Code §2870) protecting employees in such cases.
- Negotiated Agreements: If the employee has a specific
agreement (e.g., consulting or freelance arrangements),
ownership terms might differ.
So like 90% of the stackoverflow users cannot
go into an agreement individually, since they are
employed, with stackoverflow in that they would be
able to give a license to what they write.
Mild Shock schrieb:Mild Shock schrieb:such mechanisms should be a playground>
for infantile developers with a mindset of a 5 year old.
Corr.:
>
such mechanisms should not be a playground
for infantile developers with a mindset of a 5 year old.
Les messages affichés proviennent d'usenet.