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

add clarity around distros' use of aliases #250

Merged
merged 3 commits into from
Jul 22, 2024

Conversation

luhring
Copy link
Contributor

@luhring luhring commented Jul 10, 2024

Coming out of google/osv.dev#2374 (comment), wanted to suggest some potential wording improvements to help the next Linux distro that comes along better understand how the aliases field should and should not be used.

I welcome any feedback, and I'm not sure I've captured the sentiment perfectly.

One particular callout: this PR removes an existing sentence (below) that we struggled to wrap our heads around. If there's something that this was trying to convey that's lost in my PR, I'd love to better understand it.

Aliases may be used for vulnerabilities affecting different packages or ecosystems as long as they follow this definition.

cc: @michaelkedar @andrewpollock @cpanato

Copy link
Contributor

@cpanato cpanato left a comment

Choose a reason for hiding this comment

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

lgtm

docs/schema.md Outdated
follow this definition.
Two vulnerabilities can be described as aliases if they affect any given
software component the same way: either both vulnerabilities affect the software
component or neither do. And, consequently, a potential patch that addresses one
Copy link
Collaborator

Choose a reason for hiding this comment

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

Grammar nit: don't start sentences with a conjunction.

Suggested change
component or neither do. And, consequently, a potential patch that addresses one
component or neither do. Consequently, a potential patch that addresses one

Copy link
Collaborator

Choose a reason for hiding this comment

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

Or more invasively,

"A subsequent patch addresses both of the vulnerabilities (and no others), and vice versa."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I like that!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Adjusted in f84a635

@oliverchang
Copy link
Contributor

CC @chrisbloom7 and @rsc in case you have thoughts!

@oliverchang oliverchang merged commit 15b8711 into ossf:main Jul 22, 2024
1 check 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.

5 participants