Merge branch 'main' into development

content/en/docs/components/forgejo/forgejo.md

@@ -64,3 +64,30 @@ Here is the management summary of the work package results:
 * **💖 Community Contribution:** We didn't just keep this for ourselves! We contributed all these features **directly back to the upstream Forgejo community**. This wasn't just a code-dump; we actively collaborated via **issues**, **feature requests**, and **pull requests (PRs) on [codeberg.org](https://codeberg.org/)**.
 
 * **🚀 Bonus Functionality:** We also implemented **artifact caching**. This configures Forgejo to act as a **pull-through proxy** for remote container registries (like Docker Hub), which seriously speeds up our build times and saves bandwidth.
+
+---
+
+## 📊 Key Performance Indicators (KPIs)
+
+These metrics assess the success of the work package across technical quality, development efficiency, and open-source engagement.
+
+### 🚀 CI/CD & Delivery Efficiency
+
+These KPIs measure the effectiveness of the Forgejo + GARM setup.
+
+| KPI | Description | Target / Benchmark |
+| :--- | :--- | :--- |
+| **Deployment Frequency** | How often changes are successfully pushed to production/staging (e.g., deploys per day/week). | High frequency (daily or better) indicates high agility. |
+| **Change Failure Rate (CFR)** | Percentage of deployments that require immediate remediation (e.g., a rollback or hotfix). | Below 5% (Industry standard for high performance). |
+| **Cycle Time** | Time from the first commit to deployment/release. | Measured in days, trending downward, indicating pipeline efficiency. |
+| **Artifact Cache Hit Rate** | Percentage of build requests successfully served by the local Forgejo proxy cache. | **90%+** demonstrates effective use of the proxy and reduced external dependencies. |
+
+### 💖 Open Source & Community Engagement
+
+These KPIs quantify our strategic commitment to the Forgejo community.
+
+| KPI | Description | Target / Benchmark |
+| :--- | :--- | :--- |
+| **Upstream Contribution Ratio** | Percentage of project code (GARM-related features) committed to Forgejo's upstream repositories versus being maintained in a private fork. | **100%** demonstrates full commitment to collaboration. |
+| **Pull Request (PR) Resolution Time** | Average time taken for a PR submitted to Codeberg to be merged or closed by the Forgejo community. | Trending downward (e.g., < 7 days) indicates healthy, responsive collaboration. |
+| **Number of Accepted External PRs** | Count of community-submitted features/fixes related to our GARM extension that we review/merge into our implementation. | Increase over time indicates growing external adoption/interest in our work. |