-
Notifications
You must be signed in to change notification settings - Fork 117
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
[ALL] - We need to be more consistent on "compliant" vs "conformant" #988
Comments
@tomkivlin (Tom), thanks for opening this issue. The RI/RC WSs will avoid duplication and use this issue to document the conversation & disposition, then apply the outcome across our documents, and presumably updates to our WS titles, and general decks/messaging. Per the Gov call today Brian B. will be reaching across to Heather to collect their (LFN) feedback, then we can ensure we have consensus on definition, and application of that definition. |
Has there been any conclusion in the meantime regarding official terminology we should follow? |
@rabi-abdel did you say on a call last week that "conformance" / "conformant" was the chosen term? If we can point to a meeting decision, or even better some published content then we could start raising PRs across all RM/RA/RI/RC workstreams. |
@tomkivlin yes, the decision is to use Conformance/Conformant. |
Fixes the RM part of anuket-project#988 Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
Fixes the RM part of #988 Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
There is a similar RC-1 issue, #1056 . Therefore, I did some research, and generated a PR #1283 to clarify Conformance for the use of RC-1. It's a short, abbreviated definition. The more detailed notes and background are in my RC-1 issue #1056. Please review the PR #1283 and feel free to edit/comment after looking at the notes/research I put in the issue. |
1. Change Compliant to Conformant (Issue #988) 2. Changed language of 1.1 and 1.3
1. replace "compliance" and "compliant" with "conformance" and "conformant" (Issue #988) 2. Edit some language to make it clearer and concise.
Changed title of 4.2.3.3 to say "conformant" (Issue #988)
Edit 5.1 to change "conformance" to "compliance" (Issue #988). Some minor language edits.
Changed title of 4.2.3.3 to say "conformant" (Issue #988)
* [RA-1 C03] Language edits 1. replace "compliance" and "compliant" with "conformance" and "conformant" (Issue #988) 2. Edit some language to make it clearer and concise. * [RA-1 Ch03] "Compliant" Delete "The following diagram shows the core OpenStack services that must be provided to be compliant." as part of it is repeat of previous paragraph; introduce conformance in the previous paragraph.
Edit 5.1 to change "conformance" to "compliance" (Issue #988). Some minor language edits.
RI/RC were done via issue 1056 & PR 1283 (Both closed) |
From deep dive in Prague:
We need to be more consistent on "compliant" vs "conformant"
The text was updated successfully, but these errors were encountered: