Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License changes #1241

Merged
merged 3 commits into from
Mar 7, 2024
Merged

License changes #1241

merged 3 commits into from
Mar 7, 2024

Conversation

buger
Copy link
Owner

@buger buger commented Mar 6, 2024

No description provided.

Copy link
Contributor

@eamora-ab eamora-ab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change on line 55 (Section 9 limitation of liability) looks right.

There's another change request on section 13.5 which is reference by section 9. The change is as follows (copied from communication with legal counsel):

13.5 (Indemnification). Licensor agrees to defend, indemnify, and hold harmless You from and against any lawsuits, claims, losses, damages, fines and expenses (including attorneys' fees and costs) arising out of a claim brought by a third-party alleging that the Software directly infringes such third-party’s intellectual property rights; provided that Licensor shall have no indemnity obligation for claims arising out of your modification to the Software. You agree to defend, indemnify, and hold harmless Licensor from and against any lawsuits, claims, losses, damages, fines and expenses (including attorneys' fees and costs) brought by a third-party arising out of your modifications to the Software or breach of this Agreement.

The summary and rationale for the change is keep this protection both ways. Right now it is a protection for the licensor. The request is add a similar statement to protect the license. Basically my employer is seeking protection in the rare event of a third party making some sort of claim that neither of can hold each other accountable.

IANAL(I am not a lawyer) but my thought is that this is implicit. For example, if hypothetically we were to copy copyrighted code and a 3rd party seeks damages, we cannot blame you nor can you blame us. The idea is to make both of these cases explicit to minimize risk for the business (licensee in this case).

In no event will either party be liable for any direct, indirect, consequential, incidental, special, exemplary, or punitive damages or liabilities whatsoever arising from or relating to the Software, the Software content or this Agreement, whether based on contract, tort (including negligence), strict liability or other theory, even if such party has been advised of the possibility of such damages.

In no event will Licensor liability exceed the Software license price as indicated in the invoice. The existence of more than one claim will not enlarge or extend this limit.
Except for indemnification obligations in Section 13.5, in no event will Licensor liability exceed the Software license price as indicated in the invoice. The existence of more than one claim will not enlarge or extend this limit.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good.

Copy link

sonarcloud bot commented Mar 7, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@buger
Copy link
Owner Author

buger commented Mar 7, 2024

@eamora-ab make sense! Applied changes to other section as well.

Copy link
Contributor

@eamora-ab eamora-ab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

@buger buger marked this pull request as ready for review March 7, 2024 14:48
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Mar 7, 2024
@buger buger merged commit 5c7cb59 into master Mar 7, 2024
13 checks passed
@eamora-ab
Copy link
Contributor

Following up here:

Legal realized that the previous statement in section 9 could stay and should stay:

In no event will either party be liable for any direct, indirect, consequential, incidental, special, exemplary, or punitive damages or liabilities whatsoever arising from or relating to the Software, the Software content or this Agreement, whether based on contract, tort (including negligence), strict liability or other theory, even if such party has been advised of the possibility of such damages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants