PMC Vote on GMNS v0.94 PR

[joecastiglione]

PMC Members,

Per the proposed rules in our draft GMNS Governance document, PMC members are asked to indicate their support or opposition to a proposed action, in this case, acceptance of the PR for GMNS v0.94, which is described here:

#60

As this is a code change, lazy approval by the PMC is required.

Lazy approval means that the change is implicitly allowed unless a “-1” PMC vote is received, at which time, depending on the type of action, either lazy majority or consensus approval must be obtained. No quorum is required.

As PMC members you may indicate your position in the following ways

+1 = "Yes," "Agree," or "the action should be performed."

-1 = “No,” “Disagree,” or “the action should not be performed.” On issues where consensus is required, this vote counts as a veto. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a -1 vote to include an alternative course of action.

Abstain = PMC members can abstain from voting. They can either remain silent or express their reason.

PMC members will have one week to vote (by end of day Monday 6/12/2023, Anywhere on Earth), if you so choose. If additional time is needed, please indicate.

Thanks,

Joe

[joecastiglione]

+1

[ssmith55]

+1

[e-lo]

Request: can you please tag official releases with each voted-on version so that it is obvious which version is associated with which commit? This will enable us to validate to specific versions of the spec. 🙏

https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository

[mike-mahut]

+1

[ianberg-volpe]

The voting period has closed without a -1 vote, so I will now merge the PR.