-
Notifications
You must be signed in to change notification settings - Fork 74
Creating Conclusions
A Conclusion in AboutCode Manager refers to the documentation of your analysis and conclusions about the name, version, owner, copyright, license expression and other attributes for a single software package or file or -- if you conclude these attributes are shared by a group of packages and/or files -- for that group of packages/files.
You can record your Conclusions throughout the codebase you're analyzing, at any levels of the codebase (i.e., nodes in the directory tree representing the codebase) you think will best reflect the results of your analysis.
To create a Conclusion, begin by navigating to the Scan Data Table
view.
(insert image of Scan Data Table view)
In the directory tree on the left, choose the directory, package or file you want to annotate, right-click that node, and select Edit Conclusion
in the menu that appears. This will display a form with the path to that node displayed at the top of the form, and a series of attribute names (e.g., Status
, Name
, Version
, License Expression
, Owner
, Copyright
) and associated textboxes, dropdowns or radio buttons to record your input.
(insert image of Conclusion form)
The following fields are available when creating a Conclusion:
(The following is currently being revised)
Component Field | Description |
---|---|
Status | Used to document status of component creation (Analyzed - A component has been created, Needs Attention - A component is flagged for further review, Original Code - A component is from your organization, Not Reporting - A component that will not be reported and can be ignored) |
Component | Primary component (usually a file, directory or library name). A Component is any software-related object. Any component can contain one or more subcomponents. Component Name + Component Version must be unique. |
Version | Component Version Number |
License | This is the License for the Component. A License includes both the facts of a license, primarily the text, as provided by its owner, as well as an organization's interpretation and policy regarding that license. |
Owner | An Owner identifies the original creator (copyright holder) of a component. If this component is in its original, unmodified state, the component owner is associated with the original author/publisher. If this component has been copied and modified, the component owner should be the owner that has copied and modified it. |
Copyright | The Copyright notice that applies to the Component under the License. |
Programming Language | The primary language of the Component |
Homepage URL | The Homepage URL of the Component |
Notes | Comments that provide additional insight into the findings. |