Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align package information with doc composition #669

Merged
merged 1 commit into from
May 17, 2022

Conversation

nishakm
Copy link
Contributor

@nishakm nishakm commented May 3, 2022

No description provided.

@nishakm nishakm changed the title 668 sync package info Align package information with doc composition May 3, 2022
@nishakm nishakm force-pushed the 668-sync-package-info branch from 1b7ea50 to 2a211bb Compare May 3, 2022 14:40
@kestewart kestewart self-requested a review May 10, 2022 14:46
@kestewart kestewart added this to the 2.3 milestone May 10, 2022
Copy link
Contributor

@kestewart kestewart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update description and add in the DCO, other than that, looks good to merge.

Copy link
Member

@swinslow swinslow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nishakm! One comment on formatting, otherwise +1 from me.


This field provides information about the purpose of the identified package. Package Purpose is intrinsic to how the package is being used rather than the content of the package. The options to populated this field are limited to:

`APPLICATION` if the package is a software application;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this list need asterisks as prefixes, so that the lines don't soft-wrap into a single paragraph (since this is MarkDown)?

Package information is optional, but if it is added the following
fields shall be present.

Fixes spdx#668

Signed-off-by: nisha <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants