FLUIDFLUID
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Anatomy
  • Cheatsheet
  • Full Specification
  • Versions
  • JSON Schema 0.7.5 ↗
  • Reference (HTML) ↗
Examples
How-to
What's New
Deck
GitHub
GitHub
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Anatomy
  • Cheatsheet
  • Full Specification
  • Versions
  • JSON Schema 0.7.5 ↗
  • Reference (HTML) ↗
Examples
How-to
What's New
Deck
GitHub
GitHub
  • Project

    • Contributing to FLUID: Shape the Standard

Contributing to FLUID: Shape the Standard

Welcome! FLUID is more than a specification — it's a community-driven standard for the future of data. We thrive on collaboration, innovation, and practical solutions. If you want to help define a great standard and solve real problems, you're in the right place.


🚀 Our philosophy: build with us

We believe in a simple, meritocratic process: good ideas, backed by clear use cases, get in. Your expertise and creativity can help shape the future of data engineering.


🛠️ How to contribute

We keep things lean and effective — no unnecessary bureaucracy.

1. Have an idea? Start the conversation

  • Big ideas, new features, or breaking changes: Open a GitHub Issue to start a discussion. Tip: A great proposal explains the "why" as much as the "what."

  • Bug fixes, typos, or small improvements: Skip the issue — just open a Pull Request!


2. Fork, code, and submit a Pull Request

  1. Fork the repository.
  2. Make your changes directly to the specification files.
  3. Add a real-world example.Features without clear, practical examples will not be accepted.
  4. Submit your PR. Link to your issue if you created one.

3. Community review: fast, fair, focused

Your PR will be reviewed by core contributors and the community. We look for:

  • Alignment with FLUID principles: Federated, Layered, Unified, Interchange Definition.
  • Clarity and simplicity: Is it easy to understand and elegant?
  • Real-world impact: Does it solve an actual problem?

If it's good, it's in. We value thoughtful debate and feedback, but we have a strong bias for action.


🌟 Becoming a core contributor

Consistently submit high-quality PRs, provide thoughtful reviews, and help shape discussions. That's the path to becoming a core contributor and a recognized member of the FLUID project.

Your name, ideas, and expertise will be embedded in a standard powering the next generation of data engineering.


🤝 Code of Conduct

We expect everyone to follow our Code of Conduct:

  • Be respectful.
  • Challenge ideas, not people.

Let's build something great — together.


Where to go next

  • Core Principles — the five principles every contribution should align with.
  • Schema Reference — the specification files you'll be editing.
  • Examples — where your real-world example will live.
Edit this page on GitHub
Last Updated: 5/29/26, 5:26 PM
Contributors: fas89, Claude Opus 4.8