Repository navigation
Conversation
zzylol
force-pushed
the
docs/governance-and-rfc
branch
from
October 12, 2026 21:18
01d6f14 to
0965b48
Compare
RFC 0001 is the accepted design doc, with its two diagrams and three marked updates for facts that changed after approval (scenario generator receiver, fanout-based exact ground truth, one asap-collector container per stage).
zzylol
force-pushed
the
docs/governance-and-rfc
branch
2 times, most recently
from
October 13, 2026 00:20
17186b1 to
f263a6c
Compare
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
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.
Part 10 of the RFC 0001 stack: governance and the design record, following OpenTelemetry practice.
docs/rfcs/0001-sketch-telemetry-functions.md: the approved design doc, wording unchanged, with its two diagrams. Facts that changed after approval are marked "Update after approval:" and the superseded sentences are struck through:docs/rfcs/README.md: when to write an RFC versus a GitHub issue, numbering, statuses and review.CONTRIBUTING.md: roles (contributor, approver, maintainer) and the bar for each; at most two open PRs per contributor; PR expectations; design principles; local checks; the CI benchmark tiers (now implemented); a weekly sync (placeholder). It is written for people and AI agents.MAINTAINERS.md(a placeholder row for the owner), issue forms (bug, feature, capability) and a PR template.README.md: a short Contributing section.Please fill in or adjust: the MAINTAINERS row, the weekly sync time and link, and the approver/maintainer bar (my proposal: approver after a month with several merged PRs and reviews plus a maintainer sponsor; maintainer after two months as approver plus a majority of maintainers).