-
Notifications
You must be signed in to change notification settings - Fork 22
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
docs: Add responsibles label to ocmcli component descriptor #1233
base: main
Are you sure you want to change the base?
Conversation
The responsibles label is used to automatically assign detected compliance issues to the responsible GitHub team. If no such responsibles are configured, GitHub repository statistics will be heuristically examined to determine the respective responsibles, however, these statistics are not properly created for this repository.
Mend Scan Summary: ❌Repository: open-component-model/ocm
|
|
||
|
||
labels: | ||
- name: cloud.gardener.cnudie/responsibles |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this label is opinionated, I am not sure if we should really accept this. if at all it should be ocm.software/responsibles. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems to be related to naming conventions discussions for "standard" labels that we expect to be used with OCM we had in the past, but never productively continued / finished :-)
The OCM spec differentiates between labels with a specific meaning inside of OCM and others, vendor specific ones (see here. cloud.gardener.cnudie/responsible would fall in "vendor-specific", but is very "standard" as many teams will have a need for them.
Therefore I support Jacob's proposal and start having a set of "standard" labels in the ocm.software namespace that we offer and use in our examples and OCM owned components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it will likely be a good idea to have a registry of "wellknown" labels (I started an internal one here). I also agree we should eventually drop cnudie
.
Considering, however, that we might see similar cases in the future, how about adding an aliases
-attr to labels? Also, I would very much appreciate it so see a registry of well-known labels at this github-organisation (those might be a good fit as additional language-bindings - ours (note that the package(-name) did not age well / is subject to being refactored).
What this PR does / why we need it
The responsibles label is used to automatically assign detected compliance issues to the responsible GitHub team. If no such responsibles are configured, GitHub repository statistics will be heuristically examined to determine the respective responsibles, however, these statistics are not properly created for this repository.
Which issue(s) this PR fixes