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
< Technical Team‎ | Use Cases/2.0
Revision as of 19:31, 4 April 2012 by Eaw (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  1. Title: Committer annotates source files with SPDX data
  2. Primary Actor: Committer
  3. Goal in Context: To indicate in the file their SPDX data for that file
  4. Stakeholders and Interests: 
    1. Committer: 
      1. To communicate in the source file the SPDX data that applies to the file
    2. Upstream maintainers: 
      1. To be able to document the license information for the commits they receive
      2. To communicate the licensing information for their copyrightable artifacts.  
      3. To have their licenses respected
    3. Consumers of upstream source:
      1. To receive accurate and clear information of licensing of upstream source
      2. To be able to comply easily with licenses for upstream source
      3. To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.
  5. Preconditions: 
    1. Committer has decided to accept the licensing for the upstream project
    2. The Upstream Maintainer is providing SPDX data for the upstream project.
  6. Main Success Senario: Committer communicates  in the file the SPDX data for the file.
  7. Failed End Condition: Committer communicates inaccurate incomplete licensing information for their package.
  8. Trigger:
    1. Commit of code to an upstream project.
  9. Notes: This use case needs work, it's probably *not* about the committer here, but the inline marking of source code files is interesting.