Template – professional legal review recommended. This page summarizes the licensing and release principles of the GitCover Commons gUG. The license file of the respective repository or material is always binding. Status: [DD.MM.YYYY].

The GitCover Commons gUG (limited liability) — "GCC" — promotes Open Source and open knowledge. To make clear what may be used how, the principle applies throughout: the respectively attached license is decisive. This page only explains where to find these notices and which licenses we typically use.

1. Principle: The license at the work is decisive

For each work (software repository, dataset, training material, graphic), the license deposited there is binding. We label licenses machine-readably according to the REUSE standard with SPDX identifiers. Authoritative sources per work:

flowchart TD A["Work of the GCC
(Code · Docs · Material · Graphic)"] B{"License
notice?"} L1["LICENSE / LICENSES/"] L2["SPDX-License-Identifier
in the file"] L3[".reuse/dep5"] L4["Notice in the material"] R["This specific license is
BINDING for use"] F["If in doubt: inquiry to
gemeinnuetzig@gitcover.org"] A --> B B -->|Repository| L1 B -->|File| L2 B -->|Collection| L3 B -->|Website/Doc| L4 L1 --> R L2 --> R L3 --> R L4 --> R B -->|no notice| F classDef n fill:#e3f2fd,stroke:#1565c0,stroke-width:2px; classDef ok fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px; classDef q fill:#fff3e0,stroke:#ef6c00,stroke-dasharray:4 3; class A,L1,L2,L3,L4 n; class R ok; class F q;

2. Typical Licenses

Unless indicated otherwise, we use:

Type of work Typical license (SPDX) Meaning in brief
Software / Source code Apache-2.0 or MIT Use, modification, distribution — even commercially — permitted under the conditions of the license
Documentation / Training material CC-BY-4.0 or CC-BY-SA-4.0 Redistribution/modification with source and license attribution (for SA: same license)
Website content CC-BY-SA-4.0 as above
Standards / Specifications indicated per document see respective license notice

The table serves as orientation. In individual cases, exclusively the license deposited at the work applies (item 1).

3. Usage and Publishing Releases

Beyond the licenses, granted releases (e.g., for redistribution of materials, for source attribution, for use of templates) apply exclusively vis-à-vis commercial users (entrepreneurs within the meaning of Section 14 BGB; see GTC, item 2) and only within the granted scope.

4. Trademarks, Names and Logos (excluded)

The open licenses do not cover trademark, name, and mark rights. In particular, "GitCover" and "Coverflex" as well as the associated logos are protected and may not be used to designate own products/services without separate written permission. Third-party trademarks (e.g., "GitLab", "GitHub", "Codeberg", "Open WebUI") are the property of their respective holders.

5. Third-Party Licenses (Third-Party Components)

Our software and this website may contain third-party components under their own open-source licenses. These are listed in the respective LICENSES/ collection or in a THIRD-PARTY/NOTICE file of the repository and take precedence for the respective component.

Third-party components used on this website:

Component Purpose License (SPDX) Reference
Mermaid.js Rendering of diagrams MIT via jsDelivr CDN
Google Fonts Fonts OFL-1.1 / Apache-2.0 (per font) via Google CDN

Note: The integration of Mermaid.js and Google Fonts via external CDNs is also relevant to data protection — see Privacy Policy, sections 2a and 5.

6. Contributions

Contributions to our projects are made under the conditions deposited in the respective project — typically via a Developer Certificate of Origin (DCO) or a Contributor License Agreement (CLA) (CONTRIBUTING file in the repository).

7. Sources

Questions on licensing: gemeinnuetzig@gitcover.org.