Details
-
PI Risk
-
Resolution: Resolved
-
Solution
-
Intolerable
-
Data Processing, Obs Mgt & Controls, Services, SRCnet, Product Delivery Teams
-
Mitigate
-
AT4-903 Check PSS gitlab licenses
AT-224
Compliance for all Atlas-managed repos: LICENSE
ORC-1423
Review and update licenses
AT3-311
Check all licenses for PST Gitlab repositories
NZAPP-587
Add license to ska-telescope/csp-rdma-spectrogram
CT-770
Taranta: Manage system team deprecations
CT-766
Integrate license reporting in CI machinery for all repositories
CT-765
Remove archived projects from Gitlab
BTN-1579
all projects: ROAM-345 Software Licences check
5 more...
Description
In GitLab, our public projects must have an open licence.
Without this, we will suffer reputation loss, as we will not be living up to our principle of openness.
We will also suffer a financial penalty, as we will need to pay for services we currently get for free, but this is less important the reputation loss.
This will be resolved when:
- All repositories under the ska-telescope organisation have a LICENSE
- All public repositories have an open source LICENSE
- ideally, this is a licence as defined in the SKA Software Standards (i.e. default of BSD 3-clause, unless GPL or lGPL must be used).
- A solution is identified to manage non compliances out of the ska-telescope gitlab groupÂ
- license reporting is integrated into the CI pipeline machinery - https://docs.gitlab.com/ee/user/compliance/license_compliance/index.htmlÂ
Teams can see which repos we've identified as an issue in:
 Licenses can be checked by:
$ sudo pip3 install spdx-lookup
$ cd <project dir>
$ spdx-lookup -f LICENSE info
Confidence: 96.67%
Id: BSD-3-Clause
Name: BSD 3-clause "New" or "Revised" License
OSI approved: yes
 It appears that a minimum of 96.67% is required so that GitLab can automatically recognise the license.
Attachments
Issue Links
- is duplicated by
-
SS-104 All SKA GitLab repository licences updated to comply with SKA software standards
-
- Discarded
-
- mentioned on
