FOSSology - Revision history

Ckresse: /* Customization */ : Add note on patch offset

2024-01-19T10:21:43Z

Customization: : Add note on patch offset

← Older revision		Revision as of 12:21, 19 January 2024
Line 5:		Line 5:

	== Customization ==		== Customization ==
	In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">		In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation (version 4.1.0.95), the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">
	Index: fossology/spdx2/agent/template/spdx2-document.xml.twig		Index: fossology/spdx2/agent/template/spdx2-document.xml.twig
	===================================================================		===================================================================
Line 47:		Line 47:
	+{% endfor %}		+{% endfor %}
	</syntaxhighlight>		</syntaxhighlight>

			For newer Fossology versions, there might be a slight offset when applying the patch.

	==Community server==		==Community server==

Ckresse: /* Customization */: Remove anchor

2024-01-09T10:12:11Z

Customization: : Remove anchor

← Older revision		Revision as of 12:12, 9 January 2024
Line 4:		Line 4:
	In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.		In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.

	== ~~<div id="fossypatch">~~Customization~~</div>~~ ==		== Customization ==
	In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">		In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">
	Index: fossology/spdx2/agent/template/spdx2-document.xml.twig		Index: fossology/spdx2/agent/template/spdx2-document.xml.twig

Ckresse: Add anchor to /* Customization */

2024-01-09T10:08:22Z

Add anchor to Customization

← Older revision		Revision as of 12:08, 9 January 2024
Line 4:		Line 4:
	In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.		In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.

	== Customization ==		== <div id="fossypatch">Customization</div> ==
	In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">		In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">
	Index: fossology/spdx2/agent/template/spdx2-document.xml.twig		Index: fossology/spdx2/agent/template/spdx2-document.xml.twig

CarstenEmde: Updated OSSelot logo to new font feature

2023-11-01T14:41:06Z

Updated OSSelot logo to new font feature

← Older revision		Revision as of 16:41, 1 November 2023
Line 5:		Line 5:

	== Customization ==		== Customization ==
	In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">		In the SPDX standard, licenses are denoted by a short identifier (e.g. GPL-2.0-only or LicenseRef-MIT-customized). Licenses that are not listed in the [https://spdx.org/licenses SPDX License List] are prefixed by "LicenseRef-", and in the section "License information" of the SPDX tag:value file, the full license text is given. Licenses with standard texts according to the [https://spdx.org/licenses SPDX License List] do not carry the "LicenseRef-" prefix, and their license text is not given in the tag:value file. For the <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> project however, the SPDX tag:value file is intended to be self-consistent, i.e. for every short license identifier the corresponding full license text must be given. In order to achieve this while ensuring the SPDX file can be valid, we have patched our Fossology installation to add the "LicenseRef-" prefix to all license identifiers. In our Fossology installation, the patch directory is /usr/local/share/fossology/patches and the patch list-all-license-texts-in-spdxtv-export.patch looks as follows:<syntaxhighlight lang="diff">
	Index: fossology/spdx2/agent/template/spdx2-document.xml.twig		Index: fossology/spdx2/agent/template/spdx2-document.xml.twig
	===================================================================		===================================================================
Line 49:		Line 49:

	==Community server==		==Community server==
	The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.		The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">OSSelot</span> curators' training.

	==Basic workflow==		==Basic workflow==
	The basic workflow for clearing a package with Fossology is given on the [https://www.fossology.org/get-started/basic-workflow/ Fossology project page].		The basic workflow for clearing a package with Fossology is given on the [https://www.fossology.org/get-started/basic-workflow/ Fossology project page].

Ckresse: Add link to basic workflow

2023-09-19T07:32:08Z

Add link to basic workflow

← Older revision		Revision as of 09:32, 19 September 2023
Line 50:		Line 50:
	==Community server==		==Community server==
	The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.		The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.

			==Basic workflow==
			The basic workflow for clearing a package with Fossology is given on the [https://www.fossology.org/get-started/basic-workflow/ Fossology project page].

Ckresse: Add License-Ref patch

2023-08-03T08:02:56Z

Add License-Ref patch

@@ Line 3: / Line 3: @@
 ==Manual addition of [[Scancode]]==
 In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.
 ==Community server==
 The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.

Wiki at 13:36, 15 July 2023

2023-07-15T13:36:59Z

← Older revision		Revision as of 15:36, 15 July 2023
Line 1:		Line 1:
	==Installation==		==Installation==
			The Fossology software can be downloaded from the [https://www.fossology.org/ project's home page].
			==Manual addition of [[Scancode]]==
	In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.		In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.
	==Community server==		==Community server==
	The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.		The reference community FOSSology server <i>[https://fossy.osadl.org Fossy]</i> is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the <i>Fossy</i> server after they successfully underwent <span style="font-family: OSSelot-Bold; font-weight: 500; color: #1565af;">O</span> curators' training.

Wiki: Created initial content

2023-07-15T13:32:14Z

Created initial content

New page

==Installation==
In addition to the default installation, the [[Scancode]] Open Source scan tool should be installed, and an interface from the FOSSology instance to it should be configured. The rationale behind the recommendation to use a certain variety of scanners is that each scanner has its own strengths and weaknesses and by combining the individual scan findings, the overall result can be optimized.
==Community server==
The reference community FOSSology server [https://fossy.osadl.org Fossy] is available on the Internet and internally used for primary curation and review; however, it is not publicly available. Future contributors may be granted login to the Fossy server after they successfully underwent O curators' training.