Technical Team/Use Cases/2.0/Consuming code snippets - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T13:21:34Z

Convert to MediaWiki syntax

Bschineller at 18:42, 25 September 2012

2012-09-25T18:42:05Z

Bschineller at 18:32, 25 September 2012

2012-09-25T18:32:21Z

Goneall at 20:58, 23 May 2012

2012-05-23T20:58:01Z

Goneall at 20:34, 23 May 2012

2012-05-23T20:34:40Z

New page

<p>To be filled in</p>

← Older revision		Revision as of 13:21, 7 March 2013
Line 1:		Line 1:
−	~~<ol><li><strong>~~Title:~~</strong>~~ Consuming Code Snippets~~</li><li><strong>~~Primary Actor:~~</strong>~~ Committer / submitter of code to either an open source project or a commercial product~~</li><li><strong>~~Goal in Context:~~</strong>~~ To include small amounts of code with implement specific functionality or algorithms developed by the open source community~~</li><li><strong>~~Stakeholders and Interests: ~~</strong></li><ol><li><p><strong>~~Committers to the open source project: ~~</strong></p><ol><li>~~Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license~~</li></ol></li><li><strong>~~Submitter to a commercial product:~~</strong><ol><li>~~Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license~~</li></ol></li><li><strong>~~Downstream consumers of the resultant software:~~</strong></li><ol><li>~~Adhere to the license obligations of the code snippet~~</li></ol><li><strong>~~Legal/compliance for the consuming organization:~~</strong></li><ol><li>~~Adhere to the license obligations of the code snippet~~</li></ol></ol><li><strong>~~Preconditions:~~</strong></li><ol><li>~~Open source project containing code snippet is available/accessible~~</li><li>~~Licensing for the project containing the code snippet is available or the author can be contacted for permission to use~~</li></ol><li><strong>~~Main Success Scenario:~~</strong> ~~Given that a snippet within a file (subset of file) is determined to have originated from somewhere else under some license, licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.~~  ~~Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations.~~ ~~(Regardless of whether the snippet includes comments indicating the origin of the code snippets.)~~</li></ol><ol><li><strong>~~Failed End Condition:~~</strong></li><ol><li>~~Committer / submitter does not indicate the inclusion of the code snippet~~</li><li>~~Originator of the code snippet does not provide adequate licensing information~~</li><li>~~If insufficient info to determine if a conflict exists between the license used for the code snippet and the license for the large component~~</li></ol><li><strong>~~Trigger:~~</strong></li><ol><li>~~Development of code~~</li></ol><li><strong>~~Example:~~</strong>~~ A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.~~ ~~ The code implementing the hash is copied into the source file which implements the verification algorithm.~~</li></ol>~~	+	# '''Title:''' Consuming Code Snippets
		+	# '''Primary Actor:''' Committer / submitter of code to either an open source project or a commercial product
		+	# '''Goal in Context:''' To include small amounts of code with implement specific functionality or algorithms developed by the open source community
		+	# '''Stakeholders and Interests: '''
		+	## '''Committers to the open source project: '''
		+	### Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license
		+	## '''Submitter to a commercial product:'''
		+	### Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license
		+	## '''Downstream consumers of the resultant software:'''
		+	### Adhere to the license obligations of the code snippet
		+	## '''Legal/compliance for the consuming organization:'''
		+	### Adhere to the license obligations of the code snippet
		+	# '''Preconditions:'''
		+	## Open source project containing code snippet is available/accessible
		+	## Licensing for the project containing the code snippet is available or the author can be contacted for permission to use
		+	# '''Main Success Scenario:''' Given that a snippet within a file (subset of file) is determined to have originated from somewhere else under some license, licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet. Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. (Regardless of whether the snippet includes comments indicating the origin of the code snippets.)
		+	# '''Failed End Condition:'''
		+	## Committer / submitter does not indicate the inclusion of the code snippet
		+	## Originator of the code snippet does not provide adequate licensing information
		+	## If insufficient info to determine if a conflict exists between the license used for the code snippet and the license for the large component
		+	# '''Trigger:'''
		+	## Development of code
		+	# '''Example:''' A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project. The code implementing the hash is copied into the source file which implements the verification algorithm.
		+
		+	[[Category:Technical]]

← Older revision		Revision as of 18:42, 25 September 2012
Line 1:		Line 1:
−	<ol><li><strong>Title:</strong> Consuming Code Snippets</li><li><strong>Primary Actor:</strong> Committer / submitter of code to either an open source project or a commercial product</li><li><strong>Goal in Context:</strong> To include small amounts of code with implement specific functionality or algorithms developed by the open source community</li><li><strong>Stakeholders and Interests: </strong></li><ol><li><p><strong>Committers to the open source project: </strong></p><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license</li></ol></li><li><strong>Submitter to a commercial product:</strong><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license</li></ol></li><li><strong>Downstream consumers of the resultant software:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol><li><strong>Legal/compliance for the consuming organization:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Open source project containing code snippet is available/accessible</li><li>Licensing for the project containing the code snippet is available or the author can be contacted for permission to use</li></ol><li><strong>Main Success Scenario:</strong> ~~Committer provides complete licensing information and an includes within the source file comments indicating the origin of the code snippets.~~  ~~Licensing~~ information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.  Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. </li><li><strong>Failed End Condition:</strong></li><ol><li>Committer / submitter does not indicate the inclusion of the code snippet</li><li>Originator of the code snippet does not provide adequate licensing information</li><li>If insufficient info to determine if a conflict exists between the license used for the code snippet and the license for the large component</li></ol><li><strong>Trigger:</strong></li><ol><li>Development of code</li></ol><li><strong>Example:</strong> A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.  The code implementing the hash is copied into the source file which implements the verification algorithm.</li></ol>	+	<ol><li><strong>Title:</strong> Consuming Code Snippets</li><li><strong>Primary Actor:</strong> Committer / submitter of code to either an open source project or a commercial product</li><li><strong>Goal in Context:</strong> To include small amounts of code with implement specific functionality or algorithms developed by the open source community</li><li><strong>Stakeholders and Interests: </strong></li><ol><li><p><strong>Committers to the open source project: </strong></p><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license</li></ol></li><li><strong>Submitter to a commercial product:</strong><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license</li></ol></li><li><strong>Downstream consumers of the resultant software:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol><li><strong>Legal/compliance for the consuming organization:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Open source project containing code snippet is available/accessible</li><li>Licensing for the project containing the code snippet is available or the author can be contacted for permission to use</li></ol><li><strong>Main Success Scenario:</strong> Given that a snippet within a file (subset of file) is determined to have originated from somewhere else under some license, licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.  Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. (Regardless of whether the snippet includes comments indicating the origin of the code snippets.)</li></ol><ol><li><strong>Failed End Condition:</strong></li><ol><li>Committer / submitter does not indicate the inclusion of the code snippet</li><li>Originator of the code snippet does not provide adequate licensing information</li><li>If insufficient info to determine if a conflict exists between the license used for the code snippet and the license for the large component</li></ol><li><strong>Trigger:</strong></li><ol><li>Development of code</li></ol><li><strong>Example:</strong> A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.  The code implementing the hash is copied into the source file which implements the verification algorithm.</li></ol>

← Older revision		Revision as of 18:32, 25 September 2012
Line 1:		Line 1:
−	<ol><li><strong>Title:</strong> Consuming Code Snippets</li><li><strong>Primary Actor:</strong> Committer / submitter of code to either an open source project or a commercial product</li><li><strong>Goal in Context:</strong> To include small amounts of code with implement specific functionality or algorithms developed by the open source community</li><li><strong>Stakeholders and Interests: </strong></li><ol><li><p><strong>Committers to the open source project: </strong></p><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license</li></ol></li><li><strong>Submitter to a commercial product:</strong><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license</li></ol></li><li><strong>Downstream consumers of the resultant software:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol><li><strong>Legal/compliance for the consuming organization:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Open source project containing code snippet is available/accessible</li><li>Licensing for the project containing the code snippet is available or the author can be contacted for permission to use</li></ol><li><strong>Main Success Scenario:</strong> Committer provides complete licensing information and an includes within the source file comments indicating the origin of the code snippets.  Licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.  Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. </li><li><strong>Failed End Condition:</strong></li><ol><li>Committer / submitter does not indicate the inclusion of the code snippet</li><li>Originator of the code snippet does not provide adequate licensing information</li><li>A conflict exists between the license used for the code snippet and the license for the large component</li></ol><li><strong>Trigger:</strong></li><ol><li>Development of code</li></ol><li><strong>Example:</strong> A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.  The code implementing the hash is copied into the source file which implements the verification algorithm.</li></ol>	+	<ol><li><strong>Title:</strong> Consuming Code Snippets</li><li><strong>Primary Actor:</strong> Committer / submitter of code to either an open source project or a commercial product</li><li><strong>Goal in Context:</strong> To include small amounts of code with implement specific functionality or algorithms developed by the open source community</li><li><strong>Stakeholders and Interests: </strong></li><ol><li><p><strong>Committers to the open source project: </strong></p><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license</li></ol></li><li><strong>Submitter to a commercial product:</strong><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license</li></ol></li><li><strong>Downstream consumers of the resultant software:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol><li><strong>Legal/compliance for the consuming organization:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Open source project containing code snippet is available/accessible</li><li>Licensing for the project containing the code snippet is available or the author can be contacted for permission to use</li></ol><li><strong>Main Success Scenario:</strong> Committer provides complete licensing information and an includes within the source file comments indicating the origin of the code snippets.  Licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.  Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. </li><li><strong>Failed End Condition:</strong></li><ol><li>Committer / submitter does not indicate the inclusion of the code snippet</li><li>Originator of the code snippet does not provide adequate licensing information</li><li>If insufficient info to determine if a conflict exists between the license used for the code snippet and the license for the large component</li></ol><li><strong>Trigger:</strong></li><ol><li>Development of code</li></ol><li><strong>Example:</strong> A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.  The code implementing the hash is copied into the source file which implements the verification algorithm.</li></ol>

← Older revision		Revision as of 20:58, 23 May 2012
Line 1:		Line 1:
−	<p>To be ~~filled~~ in</p>	+	<ol><li><strong>Title:</strong> Consuming Code Snippets</li><li><strong>Primary Actor:</strong> Committer / submitter of code to either an open source project or a commercial product</li><li><strong>Goal in Context:</strong> To include small amounts of code with implement specific functionality or algorithms developed by the open source community</li><li><strong>Stakeholders and Interests: </strong></li><ol><li><p><strong>Committers to the open source project: </strong></p><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the open source license</li></ol></li><li><strong>Submitter to a commercial product:</strong><ol><li>Leverage pre-existing algorithms or functionality (e.g. MD5 Hash Algorithm) within a license compatible with the commercial license</li></ol></li><li><strong>Downstream consumers of the resultant software:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol><li><strong>Legal/compliance for the consuming organization:</strong></li><ol><li>Adhere to the license obligations of the code snippet</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Open source project containing code snippet is available/accessible</li><li>Licensing for the project containing the code snippet is available or the author can be contacted for permission to use</li></ol><li><strong>Main Success Scenario:</strong> Committer provides complete licensing information and an includes within the source file comments indicating the origin of the code snippets.  Licensing information is included in the SPDX file provided with the source code product along with information on the location of the code snippet.  Downstream consumer aggregate the license information from the Snippet with the license information from the rest of the package(s) to determine the full obligations. </li><li><strong>Failed End Condition:</strong></li><ol><li>Committer / submitter does not indicate the inclusion of the code snippet</li><li>Originator of the code snippet does not provide adequate licensing information</li><li>A conflict exists between the license used for the code snippet and the license for the large component</li></ol><li><strong>Trigger:</strong></li><ol><li>Development of code</li></ol><li><strong>Example:</strong> A file implementing a verification algorithm specific to a package needs to implement an hash algorithm in a compatible manner to another open source project.  The code implementing the hash is copied into the source file which implements the verification algorithm.</li></ol>