Technical Team/Use Cases/2.0/Upstream maintainer providing SPDX data - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T13:12:32Z

Convert to MediaWiki syntax

Eaw at 21:56, 2 April 2012

2012-04-02T21:56:04Z

Eaw at 17:54, 27 March 2012

2012-03-27T17:54:58Z

Eaw at 17:52, 27 March 2012

2012-03-27T17:52:13Z

New page

<ol><li>Title: Upstream maintainer providing SPDX data</li><li>Primary Actor: Member of upstream maintainer team</li><li>Goal in Context: To include with the copyrightable artifacts distributed by the project SPDX data describing it's licensing information.</li><li>Stakeholders and Interests: </li><ol><li>Upstream maintainers: </li><ol><li>To communicate the licensing information for their copyrightable artifacts.  </li><li>To have their licenses respected</li></ol><li>Consumers of upstreams copyrightable artifacts:</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>Preconditions: </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>Main Success Senario: Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format</li><li>Failed End Condition: Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.</li><li>Trigger:</li><ol><li>Project release</li><li>Commit time?</li></ol><li>Notes:  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>

← Older revision		Revision as of 13:12, 7 March 2013
Line 1:		Line 1:
−	~~<div><b>~~NOTE: This use case has been broken down into two ~~ ~~more specific use cases.~~ <~~/~~b><~~/~~div><div><b><br /></b></div><div><ol><li><a href="http://spdx~~.~~org~~/~~wiki/upstream-maintainer-providing-spdx-data-source-archive">~~Upstream maintainer providing SPDX data in source archive</~~a><~~/~~li><li><a href="http://spdx~~.~~org~~/~~wiki/upstream-maintainer-providing-spdx-data-scm">~~Upstream maintainer providing SPDX data in SCM~~</a></li></ol></div><div><b>~~If you are looking for an example of the use case template, please see one of them.~~</b></div>~~	+	'''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]]

← Older revision		Revision as of 21:56, 2 April 2012
Line 1:		Line 1:
−	<ol><li>~~<strong>Title~~:~~</strong>~~ 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.  ~~In particular this may look like an upstream maintainer including SPDX data in their tarball or jar file, incorporating SPDX data into their SCM, or publishing side car SPDX data.~~</li>~~<li><strong>Stakeholders and Interests:~~</~~strong~~>~~ ~~<~~/li~~><ol><~~li><strong>Upstream maintainers: <~~/~~strong~~></li>~~<ol><li>To communicate the licensing information for their copyrightable artifacts.  ~~</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> ~~</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>  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.  This can be seen because of the many different goals in the goals section~~.</li></~~ol><p> </p~~>	+	<div><b>NOTE: This use case has been broken down into two  more specific use cases. </b></div><div><b><br /></b></div><div><ol><li><a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-source-archive">Upstream maintainer providing SPDX data in source archive</a></li><li><a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-scm">Upstream maintainer providing SPDX data in SCM</a></li></ol></div><div><b>If you are looking for an example of the use case template, please see one of them.</b></div>

← Older revision		Revision as of 17:54, 27 March 2012
Line 1:		Line 1:
−	<ol><li><strong>Title:</strong> 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> </li><ol><li><strong>Upstream maintainers: </strong></li><ol><li>To communicate the licensing information for their copyrightable artifacts.  </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> </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>  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> </p>	+	<ol><li><strong>Title:</strong> 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.  In particular this may look like an upstream maintainer including SPDX data in their tarball or jar file, incorporating SPDX data into their SCM, or publishing side car SPDX data.</li><li><strong>Stakeholders and Interests:</strong> </li><ol><li><strong>Upstream maintainers: </strong></li><ol><li>To communicate the licensing information for their copyrightable artifacts.  </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> </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>  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.  This can be seen because of the many different goals in the goals section.</li></ol><p> </p>