Licensing and brand
Open-Source Acknowledgement
The open-source software WeGrowNepal is built on, and the terms we use it under.
- Version
- v1.0
- Effective
- Contents
- 3 sections · 8 clauses
- Document ref.
- WGN-LEGAL-OSS-V1.0
The PDF is a watermarked controlled copy. If it differs from this page, this page governs.
At a glance
A plain-language summary. The numbered clauses below are what legally applies.
- WeGrowNepal is built on open-source software, principally under the MIT and Apache 2.0 licences.
- We comply with the terms that software is offered under.
- We do not publish the package-and-version list, for security reasons.
- The full attribution list is available on request.
1. What we build on
- 1.1
The WeGrowNepal applications and services incorporate open-source software released under permissive licences, principally the MIT Licence and the Apache Licence, Version 2.0.
- 1.2
We are grateful to the people who wrote that software and released it freely, and we comply with the terms under which it is offered — including the requirement that copyright and permission notices accompany it.
2. Why the list is not published here
- 2.1
We do not publish the manifest of packages and version numbers shipped in our applications.
Why this is here
Such a manifest states exactly which libraries at exactly which versions are running on every installation. That is directly useful to somebody matching them against published vulnerabilities, and of very little use to anybody else.
- 2.2
This is a decision about where the list lives rather than whether it exists. The complete attribution list, including licence texts, is provided on request to any person with a legal, academic or compliance reason to have it.
- 2.3
Requests may be sent to hello@lacspace.com and are answered.
3. The licences themselves
- 3.1
The MIT Licence permits use, copying, modification and distribution, provided the copyright notice and permission notice are included with the software.
- 3.2
The Apache Licence 2.0 permits the same, adds an express grant of patent rights from contributors, and requires that significant modifications be stated.
- 3.3
The platform may include third-party or open-source components licensed under their own terms, which prevail for those components only. Such inclusion does not make Lacspace proprietary software open-source, and neither the MIT nor the Apache licence requires that it should.
Why this is here
This is the question people most often assume the other way round: using open-source software does not oblige a product to be open-source.
Version history
Every change to this document is recorded here, so amendments can be inspected rather than taken on trust.
v1.0 ·
- First published.