Roadmap: evolve Backstage into a Forgejo developer platform #31

Open
opened 2026-11-07 21:51:43 +00:00 by martin · 0 comments
Owner

Goal

Provide a reliable place to discover repositories, understand services and APIs, read documentation, create projects, and inspect delivery status. Make the catalog trustworthy, add useful developer workflows, then make the platform safe to host.

Phase 1 — Trustworthy foundation

  • #21 — Establish a reproducible dependency and test baseline
  • #22 — Add application quality gates to Woodpecker
  • #23 — Verify the imported catalog end to end
  • #20 — Replace Yarn with Bun before hosted deployment

Phase 2 — Useful developer workflows

  • #24 — Make Forgejo discovery resilient and continuously refreshed
  • #28 — Support repository-owned catalog metadata
  • #27 — Tailor the portal to the actual developer workflow
  • #25 — Deliver TechDocs for one real Forgejo repository
  • #26 — Create a project in Forgejo through a software template
  • #29 — Show Woodpecker delivery status for catalog components

Phase 3 — Hosting readiness

  • #30 — Establish a secure, persistent hosted deployment

Sequencing and decisions

  1. Start with #21 and #23; add repository-owned validation through #22.
  2. Migrate the package manager to Bun in #20 against the validated baseline and CI. Bun migration must be completed before hosted deployment; retaining supported Node as the Backstage runtime is a separate compatibility decision.
  3. Use #24 and #28 to establish refresh behavior and metadata precedence; preserve stable entity references.
  4. Deliver small documentation, scaffolding, and CI-status pilots, with useful portal navigation alongside them.
  5. Host only after the mandatory gates in #30 pass. Not every workflow pilot is required for the first secure deployment. Split identity/permissions and operations into delivery issues once the hosting target is chosen.

Backlog conventions

Each delivery issue contains its own acceptance criteria. Use this issue for overview and sequencing decisions, not duplicate task details. Native Forgejo issue dependencies capture mandatory gates. The three phases are documented here; no milestones were created because milestone creation is not exposed by the available Forgejo tools.

Existing work

Keep Renovate's Dependency Dashboard #8 as the source of dependency PRs, rather than duplicating individual upgrades. Current automated-review failures are distinct from application validation failures.

Initially out of scope

  • Kubernetes integration without a concrete workload.
  • A large custom-plugin suite before pilot workflows demonstrate value.
  • Unrestricted dependency-major upgrades or an unvalidated switch of the Backstage runtime/test runner to Bun.
  • Changes to shared global CI configuration as part of application work.
## Goal Provide a reliable place to discover repositories, understand services and APIs, read documentation, create projects, and inspect delivery status. Make the catalog trustworthy, add useful developer workflows, then make the platform safe to host. ## Phase 1 — Trustworthy foundation - [x] #21 — Establish a reproducible dependency and test baseline - [ ] #22 — Add application quality gates to Woodpecker - [x] #23 — Verify the imported catalog end to end - [ ] #20 — Replace Yarn with Bun before hosted deployment ## Phase 2 — Useful developer workflows - [ ] #24 — Make Forgejo discovery resilient and continuously refreshed - [ ] #28 — Support repository-owned catalog metadata - [ ] #27 — Tailor the portal to the actual developer workflow - [ ] #25 — Deliver TechDocs for one real Forgejo repository - [ ] #26 — Create a project in Forgejo through a software template - [ ] #29 — Show Woodpecker delivery status for catalog components ## Phase 3 — Hosting readiness - [ ] #30 — Establish a secure, persistent hosted deployment ## Sequencing and decisions 1. Start with #21 and #23; add repository-owned validation through #22. 2. Migrate the package manager to Bun in #20 against the validated baseline and CI. Bun migration must be completed before hosted deployment; retaining supported Node as the Backstage runtime is a separate compatibility decision. 3. Use #24 and #28 to establish refresh behavior and metadata precedence; preserve stable entity references. 4. Deliver small documentation, scaffolding, and CI-status pilots, with useful portal navigation alongside them. 5. Host only after the mandatory gates in #30 pass. Not every workflow pilot is required for the first secure deployment. Split identity/permissions and operations into delivery issues once the hosting target is chosen. ## Backlog conventions Each delivery issue contains its own acceptance criteria. Use this issue for overview and sequencing decisions, not duplicate task details. Native Forgejo issue dependencies capture mandatory gates. The three phases are documented here; no milestones were created because milestone creation is not exposed by the available Forgejo tools. ## Existing work Keep Renovate's Dependency Dashboard #8 as the source of dependency PRs, rather than duplicating individual upgrades. Current automated-review failures are distinct from application validation failures. ## Initially out of scope - Kubernetes integration without a concrete workload. - A large custom-plugin suite before pilot workflows demonstrate value. - Unrestricted dependency-major upgrades or an unvalidated switch of the Backstage runtime/test runner to Bun. - Changes to shared global CI configuration as part of application work.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/backstage#31
No description provided.