Page History

...

Geode contributors don't always know who the right people are to tag on a review. Geode committers also tend to review and approve pull requests based on different criteria - for example to see if the documentation is well written, or if the code meets minimum standards for including tests, etc. We want to ensure that all PRs are routed to subject matter experts that can review the substantive changes of the PR, and ensure that contributors and committers can identify that a PR has been reviewed by someone with expertise in the correct area.

Anti-Goals

What is outside the scope of what the proposal is trying to solve?

Solution

We would like to use a github CODEOWNERS file to indicate owners for different areas of the code. Below is the a breakdown of different areas of the code that need owners. None of these areas should have a single owner, and we foresee that owners can rotate over time. By being marked an owner, a user will automatically be added as a reviewer for a PR that changes these areas.

geode repository CODEOWNERS

Please see this sample draft codeowners file.

...

Other repositories

These repositories are smaller and only need a single set of code owners for each repository.

• geode-native
• geode-examples
• geode-benchmarks
• geode-site
• geode-kafka-connector
• geode-dotnet-core-client

...