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/Project maintainer pulling individual files out of another project (subsetting)"

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;Project maintainer pulling individual files out of another project (subsetting)</li><li><strong>Primary Actor:</strong>&nbsp;Member of upstream maintainer team</li><li><strong>Goal in Context:</strong>&nbsp;To include individual files from another project (subsetting), and reference the SPDX data from the incorporated project for those files.</li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To communicate the licensing information for their copyrightable artifacts including the included project. &nbsp;</li><li>To have their licenses respected</li></ol></li><li><strong>Incorporated Project maintainers:</strong><ol><li>To have their licenses respected</li></ol></li><li><strong>Consumers of upstreams copyrightable artifacts:</strong><ol><li>To receive accurate and clear information of licensing of artifacts</li><li>To be able to comply easily with licenses for artifacts</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>Preconditions:</strong>&nbsp;<ol><li>Incorporated project maintainers have selected licenses for the copyrightable artifacts originating with the project (package, files, etc) and incorporated SPDX data into their source code.</li><li>Upstream has indentified license data for other copyrightable artifacts they consume</li></ol></li><li><strong>Main Success Senario:</strong>&nbsp;Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format including the information for the incorporated project.</li><li><strong>Failed End Condition:</strong>&nbsp;Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.</li><li><strong>Trigger:</strong><ol><li>Incorporate of another projects source code.</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;Project maintainer pulling individual files out of another project (subsetting)</li><li><strong>Primary Actor:</strong>&nbsp;Member of upstream maintainer team</li><li><strong>Goal in Context:</strong>&nbsp;To include individual files from another project (subsetting), and reference the SPDX data from the incorporated project for those files.</li><li><strong>Stakeholders and Interests:</strong>&nbsp;<ol><li><strong>Upstream maintainers:&nbsp;</strong><ol><li>To communicate the licensing information for their copyrightable artifacts including the included project. &nbsp;</li><li>To have their licenses respected</li></ol></li><li><strong>Incorporated Project maintainers:</strong><ol><li>To have their licenses respected</li></ol></li><li><strong>Consumers of upstreams copyrightable artifacts:</strong><ol><li>To receive accurate and clear information of licensing of artifacts</li><li>To be able to comply easily with licenses for artifacts</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>Preconditions:</strong>&nbsp;<ol><li>Incorporated project maintainers have selected licenses for the copyrightable artifacts originating with the project (package, files, etc) and provided SPDX data for those copyrightable artifacts.</li><li>Upstream has identified license data for other copyrightable artifacts they consume</li></ol></li><li><strong>Main Success Scenario:</strong>&nbsp;Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format including the information for the incorporated project.</li><li><strong>Failed End Condition:</strong>&nbsp;Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.</li><li><strong>Trigger:</strong><ol><li>Incorporate of another projects copyrightable artifacts.</li></ol></li><li><strong>Notes:</strong>&nbsp;&nbsp;</li></ol>

Revision as of 18:30, 10 July 2012

  1. Title: Project maintainer pulling individual files out of another project (subsetting)
  2. Primary Actor: Member of upstream maintainer team
  3. Goal in Context: To include individual files from another project (subsetting), and reference the SPDX data from the incorporated project for those files.
  4. Stakeholders and Interests: 
    1. Upstream maintainers: 
      1. To communicate the licensing information for their copyrightable artifacts including the included project.  
      2. To have their licenses respected
    2. Incorporated Project maintainers:
      1. To have their licenses respected
    3. Consumers of upstreams copyrightable artifacts:
      1. To receive accurate and clear information of licensing of artifacts
      2. To be able to comply easily with licenses for artifacts
      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. Incorporated project maintainers have selected licenses for the copyrightable artifacts originating with the project (package, files, etc) and provided SPDX data for those copyrightable artifacts.
    2. Upstream has identified license data for other copyrightable artifacts they consume
  6. Main Success Scenario: Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format including the information for the incorporated project.
  7. Failed End Condition: Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.
  8. Trigger:
    1. Incorporate of another projects copyrightable artifacts.
  9. Notes:  
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Project_maintainer_pulling_individual_files_out_of_another_project_(subsetting)&oldid=1902"