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

Include author for components when available in Cargo metadata #770

Merged
merged 1 commit into from
Nov 30, 2024

Conversation

davids-work
Copy link
Contributor

No description provided.

@davids-work davids-work requested a review from a team as a code owner November 22, 2024 13:05
@Shnatsel
Copy link
Contributor

I see v1.6 has deprecated the author field and added authors which allows multiple entries. However it is not available in v1.5 or earlier.

@davids-work what is the motivation for listing the authors like this? Do you need to meet some regulations that require the authors to be listed?

@davids-work
Copy link
Contributor Author

davids-work commented Nov 29, 2024

Indeed, or at least the internal interpretation of the regulation(s) that we need to fulfill is that we must include the author field for every dependency.

I don't think that there are any rules for the exact formatting (comma-separated or otherwise) in case of multiple authors. I note that the v1.4 spec says "The person(s) or organization(s) that authored the component", so the spec writers seems to at least have had the notion that there might be multiple authors involved.

@lfrancke
Copy link
Contributor

That seems reasonable to me. Do the best we can in 1.4/1.5 and switch to the better format in 1.6.

We could ask in the CycloneDX Slack if there are any preferences....I did a quick search and didn't find anything but I might have missed something.

@Shnatsel Shnatsel merged commit a1653d7 into CycloneDX:main Nov 30, 2024
13 checks passed
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