This repository was archived by the owner on Jan 2, 2024. It is now read-only.
charter: Add a section on OCI Projects #2
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We don't want that to be part of the header.
wking
force-pushed
the
oci-project-consolidation
branch
from
5706a50 to
ac72ae7
Compare
Author
|
I'm also not sure what the established terminology would be for “being a certificate authority” (where I've used “certification application”). Is there a better term for using existing tools to accept, judge, and publish the results of certification applications? |
Because "everything the OCI is working on" is usually more important
than distinguishing between specifications and implementations. And
"OCI Specifications and/or OCI Projects" (which was used several
times) didn't list the certification tooling or application described
in the Trademark Board's old f.i ("creating the OCI trademarks
associated with OCI Specifications, OCI Projects, the Open Container
Format (OCF) or OCI Certified Solution"). It's better to just lump
all these efforts together under "OCI Projects" and then reference
them as a group later in the charter.
Author
|
OCI members can figure this out amongst themselves, and don't have a channel for input from external parties like me. |
Author
|
There is an OCI Projects §2 in the adopted charter :). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because "everything the OCI is working on" is usually more important than
distinguishing between specifications and implementations. And
"OCI Specifications and/or OCI Projects" (which was used several times)
didn't list the certification tooling or application described in the
Trademark Board's old f.i ("creating the OCI trademarks associated with OCI
Specifications, OCI Projects, the Open Container Format (OCF) or OCI
Certified Solution"). It's better to just lump all these efforts together
under "OCI Projects" and then reference them as a group later in the
charter.
This builds on #1, so that should be merged first. I'm happy to
rebase this off of #1 if #1 ends up being more controversial than I
expect ;).