Difference between revisions of "Technical Team/Use Cases/2.0/Patch provider provides SPDX data for the patch"

<ol><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Title:</strong>&nbsp;Patch provider provides SPDX data for the patch</li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Primary Actor:</strong>&nbsp;Patch Provider</li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Goal in Context:</strong>&nbsp;To indicate the licensing information asSPDX data for the patch.</li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Preconditions:</strong>&nbsp;<ol><li>Committer has decided on the licensing for the patch</li></ol></li><li><strong style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;">Stakeholders and Interests:</strong><span style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: small;">&nbsp;</span><ol><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Patch Provider:</strong>&nbsp;<ol><li>To communicate that the license information for their patch.</li><li>To have their licenses respected</li></ol></li><li><strong style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;">Upstream maintainers:&nbsp;</strong><ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><li>To be able to document the license information for the patches they receive</li><li>To have a paper trail of the licensing information for their project.&nbsp;</li><li>To have their licenses respected</li></ol></li><li><span style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: small;"><strong>Third party patch appliers (think Yocto):</strong><br /></span></li><li><ol><li><span style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: small;">To be able to know whether or not they have licensing issues when they apply a patch ot upstream.<strong><br /></strong></span></li></ol></li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><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 style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Main Success Senario:</strong>&nbsp;Patch supplier communicates the licensing information for their patch.</li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Failed End Condition:</strong>&nbsp;Patch supplier doesn't communicates inaccurate incomplete licensing information for their patch.</li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Trigger:</strong><ol><li>Creation of a patch</li></ol></li><li style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;"><strong>Notes:</strong>&nbsp;&nbsp;</li></ol>