Skip to content

GOVERNANCE.md

Latest commit

 

History

History
59 lines (38 loc) · 3.77 KB

GOVERNANCE.md

File metadata and controls

59 lines (38 loc) · 3.77 KB

🏛️ Governance of Trevas

Trevas is an open-source project with a clear governance structure. This document outlines the roles and responsibilities of project contributors and maintainers, and explains how decisions are made within the project.

📋 Governance Overview

Trevas is hosted and governed by Insee, which ensures the long-term vision and sustainability of the project. However, Making Sense, as the main contributor, is entrusted with the management of the project’s roadmap, issue prioritization, and day-to-day operational decisions.

This model ensures a balance between institutional support and active community-led development.

📋 Key Roles

Insee - Project Governance & Repository Host

  • Responsibilities:
    • Ensures the project aligns with long-term public goals.
    • Hosts the official GitHub repository.
    • Holds final decision-making authority when needed on governance matters.

Making Sense - Lead Contributor & Project Management

  • Responsibilities:
    • Drives the roadmap and feature prioritization.
    • Oversees day-to-day project management.
    • Reviews and merges Pull Requests (PRs).
    • Updates the GitHub Project board to reflect current priorities.
    • Ensures contributions meet quality and coding standards.

Maintainers

  • Maintainers assist with:
    • Reviewing and merging PRs.
    • Guiding the direction of the project based on the roadmap.
    • Managing community contributions and coordinating with Making Sense.

If you're interested in becoming a maintainer, you can request the role by emailing contact@making-sense.info.

🤝 Decision Making

  • Collaborative Decisions: Most decisions are made collaboratively with input from the community and maintainers.
  • Governance by Delegation and Consensus: Insee retains final governance authority, but delegates operational decisions to Making Sense. Decisions are generally made by consensus.
  • Major Changes: Major changes to project structure or direction are discussed openly with the community via GitHub Issues or Discussions.

🚀 Contributing

If you want to contribute to the project, please refer to our CONTRIBUTING.md for guidelines on submitting code, issues, and pull requests.

💼 Sponsors & Active Organizations

We would like to thank the following sponsors and organizations for their support and active involvement in Trevas:

  • Insee: Insee initiated the creation of Trevas and led its initial development. In addition to its governance role, Insee laid the foundation for the project and played a key role in shaping its early direction.

  • Making Sense: Main contributor to Trevas, Making Sense has made numerous code contributions, actively shaped the roadmap, and plays a key role in day-to-day project management. They also promote Trevas within the VTL (Validation and Transformation Language) community, helping to grow its adoption and ecosystem.

  • CASD: The CASD has supported the project by funding specific developments tailored to its operational needs. These enhancements have been contributed back to the main repository as open-source code, benefiting the entire community.

Their support is instrumental in helping us maintain and grow this project. If you or your organization would like to sponsor or contribute to Trevas, please reach out to us at contact@making-sense.info.

🗣️ Communication

We encourage open, transparent discussions. For any questions, suggestions, or conversations, please use GitHub Issues to engage with the community.