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/Contributor makes commit subject to existing SPDX data of project"

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;Contributor makes commit &nbsp;subject to existing SPDX data of project</li><li><strong>Primary Actor:</strong>&nbsp;Committer</li><li><strong>Goal in Context:</strong>&nbsp;To indicate the commit is subject to existing SPDX data for the project.</li><li><strong>Preconditions:</strong>&nbsp;<ol><li>Committer has decided to accept the licensing for the project</li><li>The Upstream Maintainer is providing SPDX data for the project.</li></ol></li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Committer:</strong>&nbsp;<ol><li>To communicate that their commit is licensed in alignment with the SPDX data for the project.</li></ol></li><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To be able to document the license information for the commits they receive</li><li>To communicate the licensing information for their copyrightable artifacts. &nbsp;</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;Committer communicates that they are agreeing to the SPDX data for the project applying to their commit.</li><li><strong>Failed End Condition:</strong>&nbsp;Committer communicates inaccurate incomplete licensing information for their package.</li><li><strong>Trigger:</strong><ol><li>Commit of code to an upstream project.</li></ol></li><li><strong>Notes:</strong>&nbsp;&nbsp;</li></ol>
+
<ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li><strong>Title:</strong>&nbsp;Contributor makes commit &nbsp;subject to existing SPDX data of project</li><li><strong>Primary Actor:</strong>&nbsp;Committer</li><li><strong>Goal in Context:</strong>&nbsp;To indicate the commit is subject to existing SPDX data for the project.</li><li><strong>Preconditions:</strong>&nbsp;<ol><li>Committer has decided to accept the licensing for the project</li><li>The Upstream Maintainer is providing SPDX data for the project.</li></ol></li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Committer:</strong>&nbsp;<ol><li>To communicate that their commit is licensed in alignment with the SPDX data for the project.</li></ol></li><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To be able to document the license information for the commits they receive</li><li>To communicate the licensing information for their copyrightable artifacts. &nbsp;</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;Committer communicates that they are agreeing to the SPDX data for the project applying to their commit.</li><li><strong>Failed End Condition:</strong>&nbsp;</li><ol><li>Committer communicates inaccurate licensing information for their package.</li><li>Committer communicates incomplete licensing information for their package.</li></ol><li><strong>Trigger:</strong><ol><li>Commit of code to an upstream project.</li></ol></li><li><strong>Notes:</strong>&nbsp;&nbsp;</li></ol>

Revision as of 18:45, 29 May 2012

  1. Title: Contributor makes commit  subject to existing SPDX data of project
  2. Primary Actor: Committer
  3. Goal in Context: To indicate the commit is subject to existing SPDX data for the project.
  4. Preconditions: 
    1. Committer has decided to accept the licensing for the project
    2. The Upstream Maintainer is providing SPDX data for the project.
  5. Stakeholders and Interests: 
    1. Committer: 
      1. To communicate that their commit is licensed in alignment with the SPDX data for the project.
    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.
  6. Main Success Scenario: Committer communicates that they are agreeing to the SPDX data for the project applying to their commit.
  7. Failed End Condition: 
    1. Committer communicates inaccurate licensing information for their package.
    2. Committer communicates incomplete licensing information for their package.
  8. Trigger:
    1. Commit of code to an upstream project.
  9. Notes: