I was reading an article from ContractsCounsel about how to draft a software license, and I thought I would do a quick report of NoHarm's v1 progress.
Here is the Report
Based on my experience as a contributor, I can say that some of the steps are complete; however, some steps have not been addressed in the license, and these steps are very critical because many countries require strict standards for a terms and conditions to be legally binding in their jurisdiction. Here is what the license already has according to that article:
Steps 1-4 and 8 are in the license.
Step 6 (privacy policy) is not applicable to NoHarm.
End-User License Agreement (EULA) applies to the software developers and not Raisely.
Here is what needs to be completed or discussed:
Step 5: State that Raisely owns rights to Intellectual Property (not related to issue #83)
Step 7: State what happens when the Licensee does not comply with NoHarm.
Governing Law Clauses: If an international dispute were to occur, should the Licensee's or Licensor's country of residency apply?
SaaS agreements (not being discussed; not related to #17, which is a bit off topic anyways)
Clauses for termination of the license: Raisely and contributors need a way to terminate the license to non-complying licensees.
Proposed Resolution
We need to see what needs to be discussed, and either discuss them here or in separate issues/PRs.
Overview
I was reading an article from ContractsCounsel about how to draft a software license, and I thought I would do a quick report of NoHarm's v1 progress.
Here is the Report
Based on my experience as a contributor, I can say that some of the steps are complete; however, some steps have not been addressed in the license, and these steps are very critical because many countries require strict standards for a terms and conditions to be legally binding in their jurisdiction. Here is what the license already has according to that article:
Here is what needs to be completed or discussed:
Proposed Resolution
We need to see what needs to be discussed, and either discuss them here or in separate issues/PRs.