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/Upstream maintainer providing SPDX data"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
<ol><li><strong>Title:</strong>&nbsp;Upstream maintainer providing SPDX data</li><li><strong>Primary Actor:</strong> Member of upstream maintainer team</li><li><strong>Goal in Context:</strong> To include with the copyrightable artifacts distributed by the project SPDX data describing it's licensing information.</li><li><strong>Stakeholders and Interests:</strong>&nbsp;</li><ol><li><strong>Upstream maintainers:&nbsp;</strong></li><ol><li>To communicate the licensing information for their copyrightable artifacts. &nbsp;</li><li>To have their licenses respected</li></ol><li><strong>Consumers of upstreams copyrightable artifacts:</strong></li><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></ol><li><strong>Preconditions:</strong>&nbsp;</li><ol><li>Upstream has selected licenses for the copyrightable artifacts originating with the project (package, files, etc)</li><li>Upstream has indentified license data for other copyrightable artifacts they consume</li></ol><li><strong>Main Success Senario:</strong> Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format</li><li><strong>Failed End Condition:</strong> Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.</li><li><strong>Trigger:</strong></li><ol><li>Project release</li><li>Commit time?</li></ol><li><strong>Notes:</strong> &nbsp;This use case probably needs to be broken down into multiple use cases, as there are significant variations around it involving storage of accurate SPDX data in SCMs, inline vs side car SPDX data, and at least thinking about the different ways different kinds of upstreams distribute different kinds of artifacts.</li></ol><p>&nbsp;</p>
+
'''NOTE: This use case has been broken down into two more specific use cases.'''
 +
 
 +
# [[Technical_Team/Use_Cases/2.0/Upstream_maintainer_providing_SPDX_data_in_source_archive|Upstream maintainer providing SPDX data in source archive]]
 +
# [[Technical_Team/Use_Cases/2.0/Upstream_maintainer_providing_SPDX_data_in_SCM|Upstream maintainer providing SPDX data in SCM]]
 +
 
 +
If you are looking for an example of the use case template, please see one of them.
 +
 
 +
[[Category:Technical]]

Latest revision as of 13:12, 7 March 2013

NOTE: This use case has been broken down into two more specific use cases.

  1. Upstream maintainer providing SPDX data in source archive
  2. Upstream maintainer providing SPDX data in SCM

If you are looking for an example of the use case template, please see one of them.