DevFW-CICD/website-and-documentation
23
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
website-and-documentation/content/en/docs/governance/references/_index.md

6.8 KiB
Raw Blame History

title linkTitle weight description
References References 40 Index of primary sources and evidence links used across the Governance chapter.

This list is an index of links referenced across the Governance chapter, plus the intended meaning (“semantics”) of each link.

  • (internal only) Confluence: Sub Project Developer Framework — mandate, quick links, and high-level framing.
  • (internal only) Confluence: System Design — architecture framing (planes model, baseline preferences, early decision drivers).
  • (internal only) Confluence: Proof of Concept 2024 — PoC scope, goals, and evaluation/acceptance framing.
  • (internal only) Confluence: Forgejo as a service — service decomposition and operational concerns used as evidence for Phase 4.
  • (internal only) Confluence: How we SCRUM — delivery process reference.
  • (internal only) Confluence: eDF Stakeholder Workshops — plan for internal/external stakeholder workshops, target groups, and intended outcomes.
  • (internal only) Confluence: internal stakeholder workshop 7.11. — internal stakeholder session agenda and captured feedback (contains AI-generated summary blocks).
  • (internal only) Confluence: external stakeholder workshop — external stakeholder session notes (contains agenda attachment and AI-generated summary blocks).
  • (internal only) Confluence: Workpackage e.3 - Sustainable-edge-management-optimized user interface for edge developers — UX-focused workpackage with objectives, KPIs, and “validation with users” framing.
  • (internal only) Confluence: Deliverable D66 - Sustainable-edge-management-optimized user interface for edge developers — deliverable page including PoC results summary for autonomous UI/UX testing.
  • (internal only) Confluence: Customer Engagement — research planning cadence (who/why/when), plus synthesized insights/assumptions used to justify PII-free “what we learned” summaries.
  • (internal only) Confluence: UX Insights and Learnings — running log of UX observations and recommended improvements (useful for evidence-backed, non-PII synthesis of recurring friction patterns).
  • (internal only) Confluence: [IPCEICIS-3703] Use Case identification for automated UX testing — structured prioritization of automated UX testing scenarios (happy-path smoke flows, functional correctness, visual/accessibility checks). Note: treat as internal working material; do not replicate embedded credentials/content.
  • (internal only) Jira: IPCEICIS-368 — PoC part 1 traceability anchor.
  • (internal only) Jira: IPCEICIS-765 — PoC part 2.1 traceability anchor.
  • (internal only) Jira: IPCEICIS-766 — PoC part 2.2 traceability anchor.
  • (internal only) Jira: IPCEICIS-514 — PoC golden path template traceability anchor.
  • (internal only) Jira: IPCEICIS-759 — PoC example app traceability anchor.
  • (internal only) Jira: IPCEICIS-760 — PoC CI/CD traceability anchor.
  • (internal only) Jira: IPCEICIS-761 — PoC telemetry traceability anchor.
  • (internal only) Jira: IPCEICIS-762 — PoC infrastructure traceability anchor.
  • (internal only) Jira: IPCEICIS-763 — PoC additional items traceability anchor.
  • (internal only) Jira: IPCEICIS-767 — PoC orchestration extension traceability anchor.
  • (internal only) Jira: IPCEICIS-768 — PoC part 3 (user documentation) traceability anchor.
  • Documentation site: PoC Structure — published docs-old summary of the PoC structure.
  • Documentation site: Team and Work Structure — published docs-old description of process and traceability intent.
  • Documentation site: Forgejo docs entry — documentation entry point for the Forgejo/EDP component.
  • Service entry point: edp.buildth.ing — EDP Forgejo instance.
  • Service org: edp.buildth.ing/DevFW-CICD — public organization referenced for transparency.
  • Service org: edp.buildth.ing/DevFW — private organization reference.
  • (internal only) Repository (edp-doc): edp.buildth.ing/DevFW/edp-doc — EDP technical documentation repository (ADRs, postmortems, PoC process), used as evidence sources in this chapter.
  • Upstream project: forgejo.org — Forgejo project homepage.
  • Upstream governance: Codeberg e.V. — referenced as steward/governance body.
  • Upstream contribution: PR #9409 — GARM endpoints contribution.
  • Upstream contribution: PR #9803 — webhook workflow events contribution.
  • Upstream contribution: PR #9962 — ephemeral runners contribution.
  • Upstream hosting: Codeberg.org — hosting platform used for upstream Forgejo contributions.