Adjust the ASC quarterly agenda finalization

[jjhursey]

No description provided.

[jjhursey]

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

• You do not need to vote on every proposal
• If you have no opinion, don't vote - that is also useful data
• If you've already commented on this issue, please still vote so
  we know your current thoughts
• Not all proposals solve exactly the same problem, so we may end
  up accepting proposals that appear to have some overlap
  This is not a binding majority-rule vote, but it will be a very
  significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

• Hooray or Rocket: I support this so strongly that I
  want to be an advocate for it
• Heart: I think this is an ideal solution
• Thumbs up: I'd be happy with this solution
• Confused: I'd rather we not do this, but I can tolerate it
• Thumbs down: I'd be actively unhappy, and may even consider
  other technologies instead

If you want to explain in more detail, feel free to add another
comment, but please also vote on this comment.

[jjhursey]

Per ASC Meeting on Jan. 23, 2020

• @kathrynmohror suggested that we should add text regarding the state of the PRs/Docs to be presented in the meeting. Something of the sense that all PRs and Documents to be presented at the meeting must not change in content after the two-week freeze window to provide folks with a stable view of the material to review before the meeting. Folks can comment on the PR/Issue, but the content of that PR/Issue must not change.

[kathrynmohror]

@jjhursey What about:
A PR posted for vote or reading in the ASC quarterly meeting must not have any modification of the content of the branch after the agenda finalization deadline. Comments on the PR are welcome at any time, but the content of the PR must be frozen to allow for community review of the stable text. For a formal reading, it is required that a PDF rendering of the changed document be sent to the chairs for distribution in the final agenda.

[jjhursey]

@kathrynmohror I like that addition. I'll update the PR in a moment. Thanks.

[jjhursey]

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

• You do not need to vote on every proposal
• If you have no opinion, don't vote - that is also useful data
• If you've already commented on this issue, please still vote so
  we know your current thoughts
• Not all proposals solve exactly the same problem, so we may end
  up accepting proposals that appear to have some overlap
  This is not a binding majority-rule vote, but it will be a very
  significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

• Hooray or Rocket: I support this so strongly that I
  want to be an advocate for it
• Heart: I think this is an ideal solution
• Thumbs up: I'd be happy with this solution
• Confused: I'd rather we not do this, but I can tolerate it
• Thumbs down: I'd be actively unhappy, and may even consider
  other technologies instead

If you want to explain in more detail, feel free to add another
comment, but please also vote on this comment.

[jjhursey]

PMIx ASC 2Q 2020 Meeting:

• Passed first vote: 10 Yes / 0 No / 0 Abstain / 4 not present for vote
• Passed with the edit seen here

[jjhursey]

• Rebased after merging PR Adding guidance for minor changes to the standard #10
• Added commit changing "one month" to "four weeks"

[jjhursey]

PMIx ASC 3Q 2020 Meeting:

• Passed Second Vote 7 Yes / 0 No / 2 Abstain / 5 not present for vote

[jjhursey]

(Rebased onto current master in preparation for the merge)