Closed pcw24601 closed 1 year ago
@hshuaib90 – this is quite an important Issue. What licence would you prefer for hazen? Apache 2.0? Other?
@tomaroberts agreed, this is very important. We should license this core library as Apache 2.0 immediately. The web app would not be licensed for now.
Is your feature request related to a problem? Please describe. The current licence file states users cannot legally use the Hazen software. This could inhibit software uptake, lacks clarity for developers, and may make it difficult to manage the codebase as the number of contributors (=copyright holders) grows.
Describe the solution you'd like Hazen should be released under an open source license as per NHS Service Standards guidance. This enables users to run the software without being at risk of take-downs, shake-downs, or litigation, and contributors should be aware their work will be used in this way.
Legal advice may be needed when initially implementing a license give the number of contributors.
Describe alternatives you've considered There are a dizzying number of OSS licenses. I have no strong preferences but would prefer Hazen not to be used in close-source commercial software.
Additional context Current license file:
GitHub advice on 'No license':
NHS Service Standard