OSS
/oss/en/openforge/overview

Documentation Overview

OSS Project Blueprint, reusable engineering standards, templates, and reference practices.

Documentation Overview

OpenForge is a shared Project Blueprint + Engineering Standards + Reusable Templates foundation for creating, evolving, deploying, operating, and maintaining high-quality open-source software.

It turns recurring OSS engineering foundations—repository structure, documentation guidelines, GitHub operations, CI/CD pipelines, supply chain security, release governance, and operational runbooks—into reusable standards and production-ready templates.

Engineering Lifecycle Loop

Project Definition (Purpose, scope, license definition)
      ↓
Repository Bootstrap (Directory layout, GitHub templates)
      ↓
Documentation / Architecture (README pairs, ADR structure, inventory)
      ↓
Standards + Templates (CI/CD, Docker, K8s, security baseline)
      ↓
Implementation / CI / Security (Language toolchain, build, security scan)
      ↓
Release / Operations (SemVer, SBOM, signing, observability, backup)
      ↓
Evidence / Lessons / Metrics (Maturity Scorecard evaluation)
      ↓
OpenForge Improvement (Feedback into shared standards and templates)
      ↺

OpenForge does not prescribe a specific programming language or application framework. Projects adapt the baseline to their own operational context and record intentional architectural deviations through ADRs (Architecture Decision Records).

What This Portal Adds

While the OpenForge GitHub repository serves as the authoritative source of truth for implementation assets, the /oss/en/openforge/ web portal focuses on technical context:

  • Why a standard is necessary: The fundamental engineering motivation behind each requirement
  • Adoption context: When and in which architectural phases the standard should be applied
  • Engineering trade-offs: Costs, operational overhead, and benefits introduced by the standard
  • Real-world adoption: How standards are deployed and maintained across active OSS projects
  • Continuous learning: Lessons codified from changes, incident reviews, and maturity scorecard metrics

Core Documents

  • Concepts — Three-tier model, trust boundaries, change model, and governance principles
  • Getting Started — Step-by-step adoption guide for existing and new OSS projects
  • Standards Portfolio — Complete index and directory of all 29 engineering standards
  • Templates Catalog — Reusable starting points for GitHub, CI/CD, Container, and Kubernetes assets
  • Architecture Blueprints — Combined architectural patterns across platform and service scenarios
  • Operations Guide — Post-deployment observability, health checks, backup/recovery, and incident runbooks
  • Reference Map — Authoritative source mapping across standards, templates, and evidence
  • Maturity Metrics — Maturity scorecard metrics and assessment checkpoints
  • Troubleshooting — Evidence-first symptom-cause-action debugging methodology
  • Architecture Decision Records — Key architectural decisions and design trade-offs

Source of Truth

  • Implementation Repository: dasomel/openforge
  • Engineering Standards: docs/
  • Reusable Templates: templates/
  • Reference Implementations: Narwhal, KubeMetal, nfs-quota-agent, Beluga Manager