Skip to content

Latest commit

 

History

History
21 lines (12 loc) · 1.39 KB

0007-P-proposal-sdk-approval.md

File metadata and controls

21 lines (12 loc) · 1.39 KB

Cross SDK changes approval

  • Author(s): Artur Souza (@artursouza)
  • State: Ready
  • Updated: 06/27/2023

Overview

This defines the criteria to how SDK proposal are approved.

Background

The SDK Spec SIG will define the spec for how SDKs operate today but there are still multiple areas where SDKs design are inconsistent due to decisions made within each SDK repository's maintainer. There needs to be a process to improve consistency across SDKs, independent of the SDK Spec SIG, since there are ongoing discussions for new features that keep SDKs drifting away from each other.

Proposal

Proposals that impact multiple SDKs should be presented in this repository and will be approved if at least a simple majority (50% + 1) of the maintainers of SDK repositories approve the change. The vote counted is per person and not per repository. Voting ends when the simple majority is reached; cannot be mathematically reached; or is idle (no changes, comments or votes) for more than 30 calendar days. The list of maintainers are based on the maintainers listed on GitHub as of the time of the proposal submission. Voting should be done via a comment in the proposal's pull request in this repository.

Approval of this proposal

As a way to kickstart this process, STC should approve this proposal following the existing voting criteria by STC, commenting on this proposal's pull request for future reference.