Skip to content

Remove blanket allowlist for EPL 2.0; allowlist `elkjs` instead

Thong Kuah requested to merge reduce_acceptability_to_just_elkjs into master

What does this MR do?

https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/1505 is only for EPL 2.0 for elkjs.

Other usages of EPL 2.0 needs to be separately approved

Reverse allowlist of EPL 2.0 from !6853 (merged), and allowlist elkjs instead

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • [-] If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • [-] If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • [-] If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  1. Remove EPL 2.0 from list of allowlisted licenses. Expect Trigger:package to fail
  2. Add elkjs to list of allowlisted software. Expect Trigger:package to pass

See !6870 (comment 1382568706) for passing result

  • [-] Documentation created/updated.
  • [-] Tests added.
  • [-] Integration tests added to GitLab QA.
  • [-] Equivalent MR/issue for the GitLab Chart opened.
  • [-] Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Thong Kuah

Merge request reports