Skip to content

Governance.md

Latest commit

 

History

History
56 lines (32 loc) · 3.59 KB

Governance.md

File metadata and controls

56 lines (32 loc) · 3.59 KB
Raw

GLACIATION Platform Governance

This document describes the governance structure and post-project sustainability plan for the GLACIATION platform and its core assets, specifically the Metadata Reference Model (GLC-MRM).

To guarantee the longevity of the project’s technical results beyond the initial grant period, the consortium has formalized a concrete maintenance plan and decision-making process for the glaciation-heu organization.

Technical Steering Committee (TSC)

A Technical Steering Committee (TSC) acts as the permanent custodian of the central GitHub organization. As outlined in the final exploitation strategy (Deliverable D8.5), the TSC comprises technical leads from:

  • Dell Technologies: Technical Coordinator
  • Lakeside Labs: Kernel & Swarm Intelligence Lead
  • HIRO: System Integrator

To ensure operational sustainability, TSC members have pledged in-kind contributions (engineering hours and infrastructure) to maintain their duties for a minimum of two years post-project, as part of their internal R&D roadmaps.

TSC Responsibilities

The TSC is responsible for the following core duties:

  • Repository Management: Overseeing the 40+ public repositories hosted on glaciation-heu to ensure code quality, security, and availability.
  • Release Management: Managing semantic versioning and release cycles for core components such as the Kernel and the DKG Engine. The committee maintains a continuous release cadence for minor updates and an annual review cycle for major architectural versions.
  • Conflict Resolution: Acting as the final decision-making body for conflicting pull requests or architectural changes proposed by the community.

Maintenance of the Metadata Reference Model (GLC-MRM)

The GLACIATION Metadata Reference Model (GLC-MRM) is a critical shared asset requiring active stewardship to maintain interoperability (detailed in Deliverable D6.5, Section 4.7). Its maintenance operates on a community-driven, open-source workflow following W3C/ERCIM best practices for ontology maintenance.

Contribution Workflow

The evolution of the ontology and core components adheres to the following process:

  1. Issue Tracking: Internal and external users must report semantic gaps, bugs, or feature requests via GitHub Issues.
  2. Community Discussion: Proposed changes are discussed transparently within the issue threads to reach a technical consensus.
  3. Pull Requests (PRs): Resolutions are submitted as Pull Requests. The TSC reviews these PRs against the core ontology and platform requirements.
  4. Implementation: Accepted changes are merged into the main branch, triggering a semantic version bump (e.g., v1.1.0 to v1.2.0).

This workflow ensures that the GLC-MRM remains extensible while preserving backward compatibility for existing adopters.

Licensing and Open Access

A standardized LICENSE_MATRIX.md is available to clarify the open-source licenses (e.g., Apache 2.0 / MIT) applied across all repositories. This ensures that the GLC-MRM and Kernel components remain available under permissive terms to encourage unhindered adoption.

All shared assets are supported by the post-project coordination mechanism defined in D8.5, ensuring that the knowledge, documentation, and operational runbooks remain discoverable and usable by the European research and industrial community.

Contact & Communication

For general inquiries, governance questions, or to reach the Technical Steering Committee directly, please contact the consortium at: