Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1 Sharing insights into product goals and roadmap will enable us to be successful in establishing technical direction.
2 Each CC uses their own experience and judgment to determine how best to train new folks. For example, investing time in scaffolded constructive reviews on both code PRs and design/decision PRs can have a multiplicative effect.3 In the event of any disagreement between CCs, it is expected that the CCs will demonstrate appropriate judgment and work it out amongst themselves. If moderation is required, they can reach out to Nimisha, as head of architecture.
4 The process for “acknowledgment” from the owning team is left to the discretion of the Champion and CC so they may find a working model for the relevant changes. For certain types of contributions, a one-time acknowledgment at the beginning of a project is sufficient to avoid blockers on every PR.