THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Technical Team/Use Cases/2.0/Committer annotates source files with SPDX data
From SPDX Wiki
- Title: Committer annotates source files with SPDX data
- Primary Actor: Committer
- Goal in Context: To indicate in the file their SPDX data for that file
- Stakeholders and Interests:
- Committer:
- To communicate in the source file the SPDX data that applies to the file
- Upstream maintainers:
- To be able to document the license information for the commits they receive
- To communicate the licensing information for their copyrightable artifacts.
- To have their licenses respected
- Consumers of upstream source:
- To receive accurate and clear information of licensing of upstream source
- To be able to comply easily with licenses for upstream source
- To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.
- Committer:
- Preconditions:
- Committer has decided to accept the licensing for the upstream project
- The Upstream Maintainer is providing SPDX data for the upstream project.
- Main Success Senario: Committer communicates in the file the SPDX data for the file.
- Failed End Condition: Committer communicates inaccurate incomplete licensing information for their package.
- Trigger:
- Commit of code to an upstream project.
- Notes: This use case needs work, it's probably *not* about the committer here, but the inline marking of source code files is interesting.