Stephan Lo
82d424aeca
- Remove Backstage component page (not in product structure) - Add editorial status alert to all draft pages with: * Jira ticket reference placeholder * Assignee field * Draft status indicator * Last updated date * TODO checklist for completion - Update component template with editorial header - Use Docsy alert shortcode (warning style) for professional appearance
2.2 KiB
| title | linkTitle | weight | description |
|---|---|---|---|
| Governance | Governance | 5 | Project history, architecture decisions, compliance, and audit information. |
{{% alert title="Draft" color="warning" %}} Editorial Status: This page is currently being developed.
- Jira Ticket: TBD
- Assignee: Team
- Status: Draft - Structure only
- Last Updated: 2025-11-16
- TODO:
- Migrate relevant ADRs from docs-old
- Document project history and phases
- Add deliverables mapping
- Include compliance documentation {{% /alert %}}
Governance Overview
This section provides information for auditors, governance teams, and stakeholders who need to understand the project's decision-making process, history, and compliance.
Architecture Decision Records (ADRs)
Documentation of significant architectural decisions made during the project, including context, options considered, and rationale.
Project History
Development Process
The EDP was developed using collaborative approaches including mob programming and iterative development with regular user feedback.
Project Phases
- Research & Design
- Proof of Concept
- Friendly User Phase
- Production Rollout
Deliverables Mapping
Mapping to IPCEI-CIS deliverables and project milestones.
Compliance & Audit
Technology Choices
Documentation of technology evaluation and selection process for key components (e.g., VictoriaMetrics, GARM, Terraform, ArgoCD).
Security Controls
Overview of implemented security controls and compliance measures.
Ticket References
Cross-references to Jira tickets, epics, and project tracking for audit trails.
Community & External Relations
Open Source Contributions
Contributions to the Forgejo community and other open-source projects.
External Stakeholders
User experience research and feedback integration.
Documentation Template
When creating governance documentation:
- Context: Background and situation
- Decision/Event: What was decided or what happened
- Rationale: Why this decision was made
- Alternatives: Other options considered
- Consequences: Impact and outcomes
- References: Links to tickets, discussions, external resources