THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "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
Jump to: navigation, search
 
Line 1: Line 1:
−
<ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li><strong>Title:</strong>&nbsp;Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.</li><li><strong>Primary Actor:</strong>&nbsp;Downstream Consumer</li><li><strong>Goal in Context:</strong>&nbsp;The downstream consumer would like to correct SPDX data in the upstream because they believe it contains an error.</li><li><strong>Preconditions:</strong>&nbsp;<ol><li>Downstream consumer has analyzed upstream and assembled a correction to SPDX data found in the project due to what they discovered about it.</li><li>Downstreams correction is acceptable to upstream.</li></ol></li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Downstream Consumer providing patch:</strong>&nbsp;<ol><li>To get upstream to incorporate their correction into upstreams SPDX data in their source base.</li><li>To gain legitimacy for their correction by its acceptance by upstream.</li></ol></li><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To be able to document the license information for their project accurately.</li><li>To have their licenses respected</li></ol></li><li><strong>Consumers of upstream source:</strong><ol><li>To receive accurate and clear information of licensing of upstream source</li><li>To be able to comply easily with licenses for upstream source</li><li>To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.</li></ol></li></ol></li><li><strong>Main Success Senario:</strong>&nbsp;Upstream accepts SPDX data correction from downstream as being an accurate reflection of their licensing information and incorporates it into their source base.</li><li><strong>Failed End Condition:</strong>&nbsp;Upstream does not accept SPDX data correction from downstream and incorporate them into their source base.&nbsp;</li><li><strong>Trigger:</strong><ol><li>Submission of SPDX data correction to upstream for incorporation.</li></ol></li></ol>
+
<ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li><strong>Title:</strong>&nbsp;Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.</li><li><strong>Primary Actor:</strong>&nbsp;Downstream Consumer</li><li><strong>Goal in Context:</strong>&nbsp;The downstream consumer would like to correct SPDX data in the upstream because they believe it contains an error.</li><li><strong>Preconditions:</strong>&nbsp;<ol><li>Downstream consumer has analyzed upstream and assembled a correction to SPDX data found in the project due to what they discovered about it.</li><li>Downstreams correction is acceptable to upstream.</li></ol></li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Downstream Consumer providing patch:</strong>&nbsp;<ol><li>To get upstream to incorporate their correction into upstreams SPDX data in their source base.</li><li>To gain legitimacy for their correction by its acceptance by upstream.</li></ol></li><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To be able to document the license information for their project accurately.</li><li>To have their licenses respected</li></ol></li><li><strong>Consumers of upstream source:</strong><ol><li>To receive accurate and clear information of licensing of upstream source</li><li>To be able to comply easily with licenses for upstream source</li><li>To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.</li></ol></li></ol></li><li><strong>Main Success Scenario:</strong>&nbsp;Upstream accepts SPDX data correction from downstream as being an accurate reflection of their licensing information and incorporates it into their source base (and the conscious decision to make correction is reflected)</li><li><strong>Failed End Condition:</strong>&nbsp;Upstream does not accept SPDX data correction from downstream and incorporate them into their source base.&nbsp;</li><li><strong>Trigger:</strong><ol><li>Submission of SPDX data correction to upstream for incorporation.</li></ol></li></ol>

Revision as of 18:45, 26 June 2012

  1. Title: Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.
  2. Primary Actor: Downstream Consumer
  3. Goal in Context: The downstream consumer would like to correct SPDX data in the upstream because they believe it contains an error.
  4. Preconditions: 
    1. Downstream consumer has analyzed upstream and assembled a correction to SPDX data found in the project due to what they discovered about it.
    2. Downstreams correction is acceptable to upstream.
  5. Stakeholders and Interests: 
    1. Downstream Consumer providing patch: 
      1. To get upstream to incorporate their correction into upstreams SPDX data in their source base.
      2. To gain legitimacy for their correction by its acceptance by upstream.
    2. Upstream maintainers: 
      1. To be able to document the license information for their project accurately.
      2. 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.
  6. Main Success Scenario: Upstream accepts SPDX data correction from downstream as being an accurate reflection of their licensing information and incorporates it into their source base (and the conscious decision to make correction is reflected)
  7. Failed End Condition: Upstream does not accept SPDX data correction from downstream and incorporate them into their source base. 
  8. Trigger:
    1. Submission of SPDX data correction to upstream for incorporation.
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Downstream_consumers_contributing_patches_to_provide_corrections_to_SPDX_data_for_an_upstream_that_does_have_it&oldid=1888"