QUIP 7 | qt_attribution.json File Format
|Title:||qt_attribution.json File Format|
From Qt 5.8, Qt modules document their 3rd party code in qt_attribution.json files. The format is JSON-based and can be processed with the qtattributionscanner tool.
This QUIP is about the file format of the qt_attribution.json files. See QUIP 4 for the process on how to add and update 3rd party code to Qt.
A qt_attribution.json file needs to contain one JSON object or an array of such objects. Each object's properties have the following meanings:
- Unique name for component, without spaces. All lower case. Mandatory.
- Descriptive name of the component, without version number. Camel case. Mandatory.
- The qch file the documentation of the component should be part of. Mandatory.
- Array with possible entries "examples", "tests", "tools", or "libs". Components that will be included in Qt libraries or plugins should set "libs", components that will be included in executables like Qt Designer or are part of the build infrastructure "tools". Optional, default is [ "libs" ].
- Free text on where the Third-Party Component in Qt is used, when it is included (e.g. if it's limited to a specific platform), how to avoid it (e.g. by using configure options), and what functionality is missing in this case. Mandatory.
- (Relative) path to the sources. Default is same directory as the file. Optional.
- A short description of what the component is and is used for. Optional.
- Homepage of the upstream project. Optional.
- Version used from the upstream project. This can also be a revision number or commit hash from a version control system. Optional.
- Link to exact upstream version. Optional.
- The license under which the component is distributed, preferably with the names from SPDX  'Full Name'. Mandatory.
- SPDX License Identifier , or an SPDX Expression . Optional.
- Relative path to file containing the license text. Optional for code in the Public Domain, otherwise needed.
Aggregated list of copyright lines. Mandatory.
The list can be edited for brevity by, for example, combining different copyright years for the same author. Terms like "All rights reserved" can be removed, too.
If there are too many copyright lines in the sources, aggregating them into:
Copyright YYYY The x project contributors
Copyright YYYY <main author> and contributors
is also acceptable.
|||(1, 2, 3) https://spdx.org/licenses/|