GLACIATION provides a coherent edge-core-cloud platform via modular microservices on Kubernetes. We welcome contributions that reduce data movement, enable energy-aware orchestration, and maintain privacy sovereignty.
- Governance and Sustainability
- Technical Standards
- Contribution Process
- Security and Privacy
- Open Science and Licensing
- KPI Validation
Core assets are managed through a formal stewardship plan to ensure maintenance beyond the project end date.
We follow a standardized workflow for contributions, including versioning and a set release cadence. All bugs and feature requests are managed through a structured triage process.
The platform backbone is built on Kubernetes. All contributions must respect modularity and interoperability.
Deployment: We use GitOps-based practices with Argo CD. Account for different deployment profiles, specifically edge versus data-centre configurations.
Metadata: Contributions must align with the distributed knowledge graph and the reference metadata model mapped to SAREF. Use SPARQL query templates for interaction.
Observability: Use standard tooling, including Prometheus and Grafana.
Read the documentation before asking questions. Check existing issues to see if your point has already been covered.
Investigate carefully before submitting a report. Ensure you are using the latest version.
When filing an issue, include:
- Stack traces and OS/Platform versions.
- Reliable reproduction steps.
- Expected vs. actual behavior.
Note: Do not report security vulnerabilities in public issues. Send sensitive bugs directly to glaciationconsortium@groups.outlook.com .
Explain why an enhancement is useful for the majority of users. If the feature targets a small subset, consider an add-on or plugin. Provide a descriptive title and a step-by-step description of the suggested change.
By contributing, you agree that you authored 100% of the content and have the necessary rights to provide it under the project license.
All contributions must adhere to the project security package.
Maintain policy-driven workload segregation integrated with Kubernetes scheduling. Implement encryption, data sanitization, and privacy-preserving computation standards. Ensure any AI-enabled data movement mechanisms respect ethical and trustworthy autonomy.
Official releases are delivered via GitHub. Consult the licensing matrix to determine if components are open-source, source-available, or commercial.
EU Funding: All dissemination and publications resulting from contributions must include the correct reference to EU funding.
New features must be validated against SMART KPIs, specifically regarding energy efficiency and privacy.
Ensure final reporting is comparable across use cases. Include baselines, measurement methods, and pointers to supporting logs or configuration scripts.