Summary

  • OpenTelemetry’s current public roster lists 162 project maintainers and 19 Service Desk handles. Its two listed Community Managers appear in the wider project-maintainer group but not in the smaller access group.
  • The February charter promises Community Managers Service Desk access. An October roster-sync rule defines the automated group as the Governance Committee plus Technical Committee; CNCF says a populated scoped group grants access only to listed handles. Public records do not show whether manual account creation resolves the mismatch.

Analysis

A right in the charter, a different rule in the account list

A governance promise has to survive the account system that lets its holder use it. OpenTelemetry’s documents leave one such promise between two desks.

The Governance Committee Charter says the committee may appoint Community Managers to organize cross-functional programs, work with the CNCF and member organizations, and support the end-user and contributor community. The charter says they will have Service Desk access. It also allows the committee to appoint people from outside the OpenTelemetry project.

The current Community Members page lists two people under Community Management. Both accounts appear in the broad project-maintainer roster in OpenTelemetry’s current .project file. Neither is in its 19-person servicedesk group. The wider roster has 162 handles in the current file snapshot.

The current group composition follows an explicit generation rule. On 30 October, OpenTelemetry merged a roster-sync pull request generated from the project’s public membership data. The pull request states that project maintainers are the union of the Governance Committee, Technical Committee and maintainers; the servicedesk team is the union of the Governance Committee and Technical Committee. The distinction is not hidden in a hand-edited spreadsheet. It is a formula in the approved update that determines who enters the automated service group.

CNCF’s own September implementation note explains the consequence. A project with no servicedesk team keeps access for all maintainers. Once a project publishes a non-empty team, only handles in that team receive the scoped Service Desk access; each handle must also appear in the maintainer group. The note says OpenTelemetry was the first project to use the new scope. Mailing-list membership remains tied to the full maintainer roster, so this is a support-channel rule, not a rewrite of the project’s standing or technical authority.

The result is precise. The charter assigns a Service Desk entitlement to Community Managers. The automated rule assigns seats to two committee rosters. The two currently listed managers belong to the broad maintainer set but are outside the subset used for the service-desk grant. The public documents have not joined those statements into one rule.

The safety valve handles broken data, not a missing role

CNCF’s dot-project automation guide gives a fail-open rule for an empty or unresolvable servicedesk team: the automation warns and leaves existing access unchanged. That protects a project from losing every seat because a team was mistyped or failed to resolve.

OpenTelemetry’s group is populated and resolves to a defined set. The empty-team safeguard does not say what to do when a valid group follows a formula that leaves out a role promised access by the charter. Syntax can be correct while two governance documents still disagree about entitlement.

That distinction matters because the charter does not describe Community Managers as ceremonial names. It gives them cross-project work: events, communications, programs with the CNCF, and community-health reporting to the Governance Committee. If a support seat is needed to perform a task, a right that depends on an unpublished exception is harder to exercise and harder for the committee to oversee.

Put the entitlement where the grant is made

A project can keep a small Service Desk team and still honor a wider charter. It needs one public mapping that tells maintainers which roles receive seats, which upstream roster supplies each role, how a manual exception works, and which document wins when they differ.

OpenTelemetry has already made the boundary unusually visible. The 30 October change records a formula; the current file exposes the selected handles; the charter describes a separate role. The gap is the joining rule. The Governance Committee can choose to include Community Managers in the automated group, publish a manual grant path that works alongside the scope, or revise the charter after deciding that the entitlement should change. Silence leaves the actual credential system to answer a question the governance text has already answered differently.

CNCF should publish the answer beside the group rule so the next appointee can see whether the chartered entitlement comes through the generated team or a manual exception.

OpenTelemetry’s 19-person group may be doing exactly what its source rule asks. That is why the charter needs an explicit companion rule. A sound access record shows both who receives a credential and which institutional promise that credential is supposed to serve.

Sources