THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Technical Team/Use Cases/2.0/Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it
From SPDX Wiki
- Title: Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.
- Primary Actor: Downstream Consumer
- Goal in Context: The downstream consumer would like to correct SPDX data in the upstream because they believe it contains an error.
- Preconditions:
- Downstream consumer has analyzed upstream and assembled a correction to SPDX data found in the project due to what they discovered about it.
- Downstreams correction is acceptable to upstream.
- Stakeholders and Interests:
- Downstream Consumer providing patch:
- To get upstream to incorporate their correction into upstreams SPDX data in their source base.
- To gain legitimacy for their correction by its acceptance by upstream.
- Upstream maintainers:
- To be able to document the license information for their project accurately.
- 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.
- Downstream Consumer providing patch:
- Main Success Senario: Upstream accepts SPDX data correction from downstream as being an accurate reflection of their licensing information and incorporates it into their source base.
- Failed End Condition: Upstream does not accept SPDX data correction from downstream and incorporate them into their source base.
- Trigger:
- Submission of SPDX data correction to upstream for incorporation.