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