docs(rfc): add RFC 0014 SDK acceptance scorecard - #2293
Closed
rhuss wants to merge 1 commit into
Closed
Conversation
Propose a tiered conformance framework for OpenShell language SDKs with three API tiers (Core, Extended, Full), three auth levels (L1 static, L2 token lifecycle, L3 OIDC), operational requirements (linting, testing, proto sync, CI), and a standard scorecard format. The RFC number is tentative pending maintainer assignment. Signed-off-by: Roland Huß <rhuss@redhat.com>
rhuss
requested review from
a team,
derekwaynecarr,
maxamillion and
mrunalp
as code owners
July 15, 2026 08:18
Collaborator
|
Relates to #2267 |
Contributor
Author
|
Let's park that RFC and learn from onboarding the Typescript and Golang SDK, before we prematurely introduce some guardrails here. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Propose a tiered conformance framework for OpenShell language SDKs. The RFC defines three API conformance tiers (Core, Extended, Full), three auth levels (L1 static, L2 token lifecycle, L3 OIDC), operational requirements (linting, testing, proto sync, CI), and a standard scorecard format.
The primary deliverable is a scorecard document that serves as the living acceptance contract for current and future language SDKs.
Motivation
The Go SDK contribution (#2044, tracked in #2270) is the first new language SDK and surfaced the lack of formal acceptance criteria. This was discussed in the contributor meeting on 2026-07-14. The RFC establishes a shared framework so contributors know what to target and reviewers have a concrete checklist.
What's in this RFC
Note: the RFC number 0014 is tentative pending maintainer assignment from issue #2292.
Related