Technical Team/Use Cases/2.0/Application which ships with development tools - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T13:12:51Z

Convert to MediaWiki syntax

Eaw at 21:18, 4 April 2012

2012-04-04T21:18:10Z

Goneall at 18:48, 29 March 2012

2012-03-29T18:48:59Z

New page

<ol><li>Title: Application which ships with development tools</li><li>Primary Actor: Committer of the open source project containing the contrib library</li><li>Goal in Context: To include within the distribution of an open source project development tools used to build a deployable executable (or executables) from the open source code.  These development tools would not be included in any resultant executable and may be under a different license than the stated license for the project.</li><li>Stakeholders and Interests:</li><ol><li>Committers to the open source project: </li><ol><li>Makes clear which copyrightable artifacts are intended to be used only at development time and is not intended to be distributed with any executables.</li></ol><li>Consumers of upstream copyrightable artifacts:</li><ol><li>To receive accurate and clear information of licensing of artifacts</li><li>To be able to distinguish copyrighted artifacts intended to be build and distributed as part of the project from build tools intended to be used at development time</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>Project has been organized with clear distinctions between the build tools and other project artifacts</li><li>Licensing information has been collected for the build tools and main project artifacts</li></ol><li>Main Success Scenario: Committer provides complete licensing information and an indication of which artifacts is part of the main project and which artifacts are part of the build tools. Each build tool will contain information on licensing.</li><li>Failed End Condition: Committer does not specify an artifact is part of the build tools causing confusion on the applicable license for the overall project.</li><li>Trigger:</li><ol><li>Project release</li></ol><li>Notes: This use case is from the perspective of a committer who is assembling/aggregating additional build tools for further distribution.  Although the intent of the committer for the build tools has been made, the downstream recipient may choose to use the build tools in a different manner (e.g. include some of the source in the main project itself).  The downstream recipient may also replace or remove the build tools.</li></ol>

← Older revision		Revision as of 13:12, 7 March 2013
Line 1:		Line 1:
−	~~<ol><li><strong>~~Title:~~</strong>~~ Application which ships with development tools~~</li><li><strong>~~Primary Actor:~~</strong>~~ Committer of the open source project containing the contrib library~~</li><li><strong>~~Goal in Context:~~</strong>~~ To include within the distribution of an open source project development tools used to build a deployable executable (or executables) from the open source code.~~ ~~ These development tools would not be included in any resultant executable and may be under a different license than the stated license for the project.~~</li><li><strong>~~Stakeholders and Interests:~~</strong></li><ol><li><strong>~~Committers to the open source project: ~~</strong></li><ol><li>~~Makes clear which copyrightable artifacts are intended to be used only at development time and is not intended to be distributed with any executables.~~</li></ol><li><strong>~~Consumers of upstream copyrightable artifacts:~~</strong></li><ol><li>~~To receive accurate and clear information of licensing of artifacts~~</li><li>~~To be able to distinguish copyrighted artifacts intended to be build and distributed as part of the project from build tools intended to be used at development time~~</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>~~Project has been organized with clear distinctions between the~~ ~~build tools~~ ~~and other project artifacts~~</li><li>~~Licensing information has been collected for the~~ ~~build tools~~ ~~and main project artifacts~~</li></ol><li><strong>~~Main Success Scenario:~~</strong>~~ Committer provides complete licensing information and an indication of which artifacts is part of the main project and which artifacts are part of the build tools. Each build tool will contain information on licensing.~~</li><li><strong>~~Failed End Condition:~~</strong>~~ Committer does not specify an artifact is part of the build tools causing confusion on the applicable license for the overall project.~~</li><li><strong>~~Trigger:~~</strong></li><ol><li>~~Project release~~</li></ol><li><strong>~~Notes:~~</strong>~~ This use case is from the perspective of a committer who is assembling/aggregating additional build tools for further distribution.~~ ~~ Although the intent of the committer for the build tools has been made, the downstream recipient may choose to use the build tools in a different manner (e.g. include some of the source in the main project itself).~~ ~~ The downstream recipient may also replace or remove the build tools.~~</li><li><strong>~~Example:~~</strong>~~ Wireshark, a network analyzer licensed under GPLv2, contains in it's source base piddle, which is GPLv3, but is solely used as a tool for building wireshark, and no part of which goes into any of the binary artifacts built out of Wireshark.~~</li></ol>~~	+	# '''Title:''' Application which ships with development tools
		+	# '''Primary Actor:''' Committer of the open source project containing the contrib library
		+	# '''Goal in Context:''' To include within the distribution of an open source project development tools used to build a deployable executable (or executables) from the open source code. These development tools would not be included in any resultant executable and may be under a different license than the stated license for the project.
		+	# '''Stakeholders and Interests:'''
		+	## '''Committers to the open source project: '''
		+	### Makes clear which copyrightable artifacts are intended to be used only at development time and is not intended to be distributed with any executables.
		+	## '''Consumers of upstream copyrightable artifacts:'''
		+	### To receive accurate and clear information of licensing of artifacts
		+	### To be able to distinguish copyrighted artifacts intended to be build and distributed as part of the project from build tools intended to be used at development time
		+	### To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts
		+	# '''Preconditions:'''
		+	## Project has been organized with clear distinctions between the build tools and other project artifacts
		+	## Licensing information has been collected for the build tools and main project artifacts
		+	# '''Main Success Scenario:''' Committer provides complete licensing information and an indication of which artifacts is part of the main project and which artifacts are part of the build tools. Each build tool will contain information on licensing.
		+	# '''Failed End Condition:''' Committer does not specify an artifact is part of the build tools causing confusion on the applicable license for the overall project.
		+	# '''Trigger:'''
		+	## Project release
		+	# '''Notes:''' This use case is from the perspective of a committer who is assembling/aggregating additional build tools for further distribution. Although the intent of the committer for the build tools has been made, the downstream recipient may choose to use the build tools in a different manner (e.g. include some of the source in the main project itself). The downstream recipient may also replace or remove the build tools.
		+	# '''Example:''' Wireshark, a network analyzer licensed under GPLv2, contains in it's source base piddle, which is GPLv3, but is solely used as a tool for building wireshark, and no part of which goes into any of the binary artifacts built out of Wireshark.
		+
		+	[[Category:Technical]]

← Older revision		Revision as of 21:18, 4 April 2012
Line 1:		Line 1:
−	<ol><li><strong>Title:</strong> Application which ships with development tools</li><li><strong>Primary Actor:</strong> Committer of the open source project containing the contrib library</li><li><strong>Goal in Context:</strong> To include within the distribution of an open source project development tools used to build a deployable executable (or executables) from the open source code.  These development tools would not be included in any resultant executable and may be under a different license than the stated license for the project.</li><li><strong>Stakeholders and Interests:</strong></li><ol><li><strong>Committers to the open source project: </strong></li><ol><li>Makes clear which copyrightable artifacts are intended to be used only at development time and is not intended to be distributed with any executables.</li></ol><li><strong>Consumers of upstream copyrightable artifacts:</strong></li><ol><li>To receive accurate and clear information of licensing of artifacts</li><li>To be able to distinguish copyrighted artifacts intended to be build and distributed as part of the project from build tools intended to be used at development time</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>Project has been organized with clear distinctions between the build tools and other project artifacts</li><li>Licensing information has been collected for the build tools and main project artifacts</li></ol><li><strong>Main Success Scenario:</strong> Committer provides complete licensing information and an indication of which artifacts is part of the main project and which artifacts are part of the build tools. Each build tool will contain information on licensing.</li><li><strong>Failed End Condition:</strong> Committer does not specify an artifact is part of the build tools causing confusion on the applicable license for the overall project.</li><li><strong>Trigger:</strong></li><ol><li>Project release</li></ol><li><strong>Notes:</strong> This use case is from the perspective of a committer who is assembling/aggregating additional build tools for further distribution.  Although the intent of the committer for the build tools has been made, the downstream recipient may choose to use the build tools in a different manner (e.g. include some of the source in the main project itself).  The downstream recipient may also replace or remove the build tools.</li></ol>	+	<ol><li><strong>Title:</strong> Application which ships with development tools</li><li><strong>Primary Actor:</strong> Committer of the open source project containing the contrib library</li><li><strong>Goal in Context:</strong> To include within the distribution of an open source project development tools used to build a deployable executable (or executables) from the open source code.  These development tools would not be included in any resultant executable and may be under a different license than the stated license for the project.</li><li><strong>Stakeholders and Interests:</strong></li><ol><li><strong>Committers to the open source project: </strong></li><ol><li>Makes clear which copyrightable artifacts are intended to be used only at development time and is not intended to be distributed with any executables.</li></ol><li><strong>Consumers of upstream copyrightable artifacts:</strong></li><ol><li>To receive accurate and clear information of licensing of artifacts</li><li>To be able to distinguish copyrighted artifacts intended to be build and distributed as part of the project from build tools intended to be used at development time</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>Project has been organized with clear distinctions between the build tools and other project artifacts</li><li>Licensing information has been collected for the build tools and main project artifacts</li></ol><li><strong>Main Success Scenario:</strong> Committer provides complete licensing information and an indication of which artifacts is part of the main project and which artifacts are part of the build tools. Each build tool will contain information on licensing.</li><li><strong>Failed End Condition:</strong> Committer does not specify an artifact is part of the build tools causing confusion on the applicable license for the overall project.</li><li><strong>Trigger:</strong></li><ol><li>Project release</li></ol><li><strong>Notes:</strong> This use case is from the perspective of a committer who is assembling/aggregating additional build tools for further distribution.  Although the intent of the committer for the build tools has been made, the downstream recipient may choose to use the build tools in a different manner (e.g. include some of the source in the main project itself).  The downstream recipient may also replace or remove the build tools.</li><li><strong>Example:</strong> Wireshark, a network analyzer licensed under GPLv2, contains in it's source base piddle, which is GPLv3, but is solely used as a tool for building wireshark, and no part of which goes into any of the binary artifacts built out of Wireshark.</li></ol>