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/Committers provides SPDX data for a code being committed"
From SPDX Wiki
Bschineller (Talk | contribs) |
|||
Line 1: | Line 1: | ||
− | <ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li><strong>Title:</strong> Committers provides SPDX data for a code being committed</li><li><strong>Primary Actor:</strong> Committer</li><li><strong>Goal in Context:</strong> To include SPDX data for code being committed to an upstream project.</li><li><strong>Stakeholders and Interests:</strong> <ol><li><strong>Committer:</strong> </li><ol><li>To communicate the licensing information for the code they are committing to the upstream project.</li></ol><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>Preconditions:</strong> <ol><li>Committer has decided on licensing information for their commit.</li></ol></li><li><strong>Main Success Senario:</strong> Committer communicates accurate complete licensing information for their commit in an SPDX data format as part of the commit process.</li><li><strong>Failed End | + | <ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li><strong>Title:</strong> Committers provides SPDX data for a code being committed</li><li><strong>Primary Actor:</strong> Committer</li><li><strong>Goal in Context:</strong> To include SPDX data for code being committed to an upstream project.</li><li><strong>Stakeholders and Interests:</strong> <ol><li><strong>Committer:</strong> </li><ol><li>To communicate the licensing information for the code they are committing to the upstream project.</li></ol><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>Preconditions:</strong> <ol><li>Committer has decided on licensing information for their commit.</li></ol></li><li><strong>Main Success Senario:</strong> Committer communicates accurate complete licensing information for their commit in an SPDX data format as part of the commit process.</li><li><strong>Failed End Conditions:</strong> </li><ol><li>Committer communicates inaccurate licensing information for their commit (license in the committed file disagrees with the asserted information)</li><li>Committer communicates incomplete licensing information for their commit.</li></ol></ol><ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><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 18:43, 29 May 2012
- Title: Committers provides SPDX data for a code being committed
- Primary Actor: Committer
- Goal in Context: To include SPDX data for code being committed to an upstream project.
- Stakeholders and Interests:
- Committer:
- To communicate the licensing information for the code they are committing to the upstream 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.
- Preconditions:
- Committer has decided on licensing information for their commit.
- Main Success Senario: Committer communicates accurate complete licensing information for their commit in an SPDX data format as part of the commit process.
- Failed End Conditions:
- Committer communicates inaccurate licensing information for their commit (license in the committed file disagrees with the asserted information)
- Committer communicates incomplete licensing information for their commit.
- Trigger:
- Commit of code to an upstream project.
- Notes: