Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A asdf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • asdf
  • asdf
  • Issues
  • #91
Closed
Open
Issue created Sep 12, 2021 by Symbolics@Symbolics

Symbol & warning for license field in system definition

Although the recommendation for the :license field states this should be a string, I have found that a keyword symbol works as well.

How do people feel about changing the recommendation to use a symbol identifier from the SPDX license list and issuing a warning if it's not found? E.g. :BSD-1-Clause

One use case is preparing manifests for software deliveries. Typically all included software, including all the transient dependencies, must be listed and have an approved license. At the moment it seems folks use the string in the license field randomly and it's a manual process to work out exactly what license the library is under. Using an SPDX identifier would eliminate any ambiguity.

Assignee
Assign to
Time tracking