Technical Team/Use Cases/2.0/Downstream consumers contributing patches to provide SPDX data to an upstream that doesnt have it

 

1. Title: Downstream consumers contributing patches to provide SPDX data to an upstream that doesn't have it.
2. Primary Actor: Downstream consumer
3. Goal in Context: The downstream consumer would like to provide SPDX data to an upstream that doesn't have it such that upstream will accept it as representing their licensing and incorporate it into their source base.
4. Preconditions: 
   1. Downstream consumer has analyzed upstream and assembled SPDX data matching what can be discovered about it.
   2. Downstreams analysis is acceptable to upstream.
5. Stakeholders and Interests: 
   1. Downstream Consumer providing patch: 
      1. To move their analysis of the licensing information of the software into the upstream so that it can be shared from the root of the software
      2. To gain legitimacy for their analysis by its acceptance by upstream.
   2. Upstream maintainers: 
      1. To be able to document the license information for their project.
      2. To have their licenses respected
   3. Third party patch appliers (think Yocto):
      1. To be able to know whether or not they have licensing issues when they apply a patch to upstream.
   4. 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.
6. Main Success Senario: Patch supplier communicates that their patch is licensed matching the SPDX data specified for the project.
7. Failed End Condition: Patch supplier doesn't communicates inaccurate incomplete licensing information for their patch.
8. Trigger:
   1. Creation of a patch