-
Notifications
You must be signed in to change notification settings - Fork 315
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
Rename "Violations" and "Issues" tab in the web app report #4395
Comments
My knowledge might be outdated, but I recall only using the term @sschuberth Have you considered the term "Rule Violations" actually? |
Yes, I'm only talking about the web app reporter UI.
No, but that term would be fine with me, too. |
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
Align naming with ORT's API naming see for example ORT documentation in [1] and [2] where 'policy rule violation' and `rule_violations` is used. [1]: https://github.com/oss-review-toolkit/ort/blob/master/docs/config-file-ort-yml.md#resolving-policy-rule-violations [2]: https://github.com/oss-review-toolkit/ort/blob/master/docs/file-rules-kts.md Relates-to: #4395 Signed-off-by: Thomas Steenbergen <thomas.steenbergen@here.com>
@tsteenbe any plans to continue here? |
For more clarity, the proposal is to rename "Violations" to "Policy Violations" and "Issues" to "Technical Issues", which should make more clear who in a workflow is responsible for addressing what.
Opinions @oss-review-toolkit/core-devs?
The text was updated successfully, but these errors were encountered: