GitMesh Community Governance

GitMesh Community Edition is governed by the LFDT and operates as an open-source project with transparent governance processes.

Project Overview

Project Name: GitMesh Community Edition
Governing Body: LFDT
License: Apache 2.0
Repository: https://github.com/LF-Decentralized-Trust-labs/gitmesh

Governance Structure

Technical Steering Committee (TSC)

The Technical Steering Committee provides technical leadership and oversight for the project.

Current TSC Members:

  • Ryan Madhuwala (Creator and Lead Maintainer)
  • Ronit Raj (Core Maintainer)
  • Parv Mittal (Core Maintainer)

Maintainers

Maintainers are responsible for the day-to-day management of the project, including:

  • Code review and merging
  • Release management
  • Issue triage and resolution
  • Community engagement

Contributors

All community members who contribute to the project through:

  • Code contributions
  • Documentation improvements
  • Bug reports and feature requests
  • Community support and engagement

Decision Making Process

Consensus Building

The project operates on a consensus-based decision-making model:

  1. Proposal - Ideas are proposed through GitHub issues or discussions
  2. Discussion - Community members provide feedback and suggestions
  3. Refinement - Proposals are refined based on community input
  4. Consensus - Agreement is reached through discussion and compromise
  5. Implementation - Approved changes are implemented and merged

Voting

For significant decisions that cannot reach consensus:

  • TSC members have voting rights
  • Simple majority required for most decisions
  • Supermajority (2/3) required for governance changes

Contribution Guidelines

Code of Conduct

All participants must adhere to the project's Code of Conduct, which promotes:

  • Respectful and inclusive communication
  • Constructive feedback and collaboration
  • Professional behavior in all interactions
  • Zero tolerance for harassment or discrimination

Contribution Process

  1. Fork and Clone - Fork the repository and create a local copy
  2. Create Branch - Create a feature branch for your changes
  3. Develop - Make your changes following coding standards
  4. Test - Ensure all tests pass and add new tests as needed
  5. Submit PR - Create a pull request with clear description
  6. Review - Participate in the code review process
  7. Merge - Changes are merged after approval

Becoming a Maintainer

Contributors can become maintainers by:

  • Demonstrating consistent, high-quality contributions
  • Showing deep understanding of the project
  • Exhibiting good judgment in technical decisions
  • Being nominated by existing maintainers
  • Receiving approval from the TSC

Relationship with LFDT

Governance Oversight

LFDT provides:

  • Legal and administrative support
  • Neutral governance framework
  • Intellectual property management
  • Community infrastructure

Independence

While governed by LFDT, the project maintains:

  • Technical independence and decision-making authority
  • Community-driven development process
  • Open and transparent operations

Enterprise Edition Relationship

Clear Separation

  • GitMesh CE - Open-source community edition governed by LFDT
  • GitMesh Enterprise - Commercial product built, hosted, and supported by Alveoli
  • This Website - Hosted by Alveoli for community welfare, not operated by LFDT

Collaboration

  • Alveoli contributes to the open-source project
  • Enterprise features may be contributed back to the community
  • Clear boundaries maintained between commercial and open-source offerings

Important Notice

LF Decentralized Trust governs the GitMesh CE GitHub repository. This website is hosted by Alveoli for community welfare and is not hosted or operated by LFDT.

Contact Information

Project Leadership

  • Technical Questions - Create GitHub issues or discussions
  • Governance Questions - Contact TSC members directly
  • Legal/Administrative - Contact LFDT through official channels

LFDT Contact

For LFDT-related matters:


This governance document is maintained by the GitMesh CE Technical Steering Committee and is subject to periodic review and updates.