Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
49 lines (38 loc) · 2.94 KB

CONTRIBUTING.md

File metadata and controls

49 lines (38 loc) · 2.94 KB

Contributing to Data Commons

Thank you for your interest in Data Commons. This document outlines our contribution process and expectations. These guidelines apply to all repositories within the datacommonsorg GitHub organization.

Governance and Review Authority

  • Maintenance: This project is maintained by the Data Commons team.
  • Merge Authority: Only designated Maintainers have the authority to approve and merge Pull Requests (PRs). All merges to the main branch must be reviewed.
  • Service Levels: We operate on a weekly rotation to ensure consistent engagement. We aim to:
    • Acknowledge new issues/PRs within 1 business day.
    • Provide technical feedback or triage within 3 business days.

Contribution Workflow

  1. Search First: Before opening a new issue or PR, search existing items to ensure the topic hasn't already been addressed.
  2. Open an Issue: For any significant change, please open an issue to discuss your proposal before submitting code. This ensures alignment with the project roadmap.
  3. Use Templates: Use the provided Issue and PR templates to ensure we have the necessary context (repro steps, environment, etc.) to review your work.
  4. Code Style: Follow the Google Style Guides relevant to the language you are using.

Large Feature Requests (RFC Process)

For complex additions—such as new ingestion pipelines, large-scale tooling, or architectural changes—we require a Design Proposal (RFC).

Maintainers will evaluate proposals based on:

  • Architectural Alignment: Does the feature fit the core product vision?
  • Maintenance: Can the contribution be supported long-term without excessive overhead?
  • Generality: Is the feature broadly useful to the Data Commons ecosystem?

Policy on "The No"

To maintain project focus and code quality, we may decline contributions that:

  • Fall outside the project's current scope or architectural vision.
  • Introduce significant technical debt or maintenance burden.
  • Duplicate existing functionality.

Communication

Please use GitHub Issues for all technical discussions, bug reports, and feature requests.

Contributor License Agreement

Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to https://cla.developers.google.com/ to see your current agreements on file or to sign a new one.

You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again.

Community Guidelines

This project follows Google's Open Source Community Guidelines.

By contributing, you agree that your contributions will be licensed under the project's existing Open Source license.