Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
Software Quality Assurance
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • id2
    • S
      Software
    • S
      services
  • FAIR
  • Software Quality Assurance
  • Issues
  • #60

Closed
Open
Opened Oct 17, 2020 by Maximilian Dolling@mdollingOwner

clarify handling of non SPDX licenses

The situation is as following:

GFZ+ released a software license named HEESIL-1.0-or-later. The license text is released via GFZ gitlab.

Currently only licenses in the spdx license list are valid, because of the use of the reuse tool by the fsfe.

The question is: Do we handle 'non standard' licenses?

problems that occur:

  • fixed list vs. user defined
    • fixed list makes things a lot easier
    • user self defined gives way more flexibility
  • how to get the license text to the repo?

I'd like to get your opinion.

/cc @btesfaye @hfuchs @nils @hammi @mruester

Edited Oct 17, 2020 by Maximilian Dolling
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: id2/software/services/fair/software-quality-assurance#60