Head of Open Source & GitHub Platform
Build and operate TitleChain Foundation's GitHub ecosystem as the authoritative home for open standards, specifications, reference implementations, developer tooling and the global contributor community. This is a senior hands-on role combining platform engineering, open-source program leadership and developer experience.
What this person owns
Organization + repository architecture
Organizations, teams, roles, permissions, repository taxonomy, CODEOWNERS, branching, rulesets, tags, releases and versioning.
CI/CD + automation
GitHub Actions, tests, build/release pipelines, deployment gates, automation, developer tooling and integrations with websites/APIs.
Governance + contributor system
CONTRIBUTING, GOVERNANCE, CODE_OF_CONDUCT, SECURITY, issue/PR templates, Discussions, Projects, DCO/CLA choices and contributor onboarding.
Software supply chain
SAST/code scanning, dependency review, Dependabot, secret scanning, SBOMs, artifact provenance/attestations and release integrity.
Developer experience
Docs-as-code, quickstarts, API/SDK repo standards, local setup, contributor paths, good-first-issue systems and maintainable reference implementations.
Governance + IP separation
Keep TitleChain Foundation open standards, ICSN work and M5 commercial implementations clearly separated by repository, license, access and release policy.
Core capability requirements
First 90-day proof outcomes
Repository taxonomy, ownership, teams, access model and boundaries across Foundation, ICSN and commercial implementation surfaces.
Default community health files, contributor policy, code of conduct, security policy, governance, licensing/DCO/CLA decisions and review rules.
Rulesets, CODEOWNERS, required reviews, signed commits where appropriate, release/tag/versioning standards and CI gates.
Dependency and secret scanning, code/security workflows, SBOM approach and artifact/release provenance for reference implementations.
One-command or clearly documented setup, contributor quickstart, issue/PR templates, good-first-work queues, docs and maintainer workflows.
Define how accepted issues, PRs, reviews, docs, courses, SOPs and releases become statusable M5 contribution evidence.
GitHub Sponsors/FUNDING surfaces, transparent roadmap and public contribution signals without giving sponsors control over standards or members.
What a candidate should prove
Examples of GitHub org/repo architecture, permissions, rulesets, CODEOWNERS and release systems they have designed or operated.
Real Actions/CI workflows, build/release automation, repo tooling or platform-engineering artifacts.
Maintainer/OSPO/community work showing governance, contribution design, licensing awareness and developer onboarding.
Supply-chain controls, code/dependency/secrets scanning, SBOM/provenance or secure release patterns.
Documentation, quickstarts, templates, SDK/repo conventions or tooling that measurably made contributor work easier.
Evidence they can decide what belongs in each repository and preserve governance/IP boundaries without needing to write every component themselves.
Reusable company role schema
The same capability definition can be used by any company that needs a senior GitHub/open-source platform owner. Change the governance boundaries and company context; keep the proof requirements.
role: Head of Open Source & GitHub Platform role_id: OR-001 capability_domains: - github_platform_engineering - open_source_program_management - developer_experience - software_supply_chain_security - standards_and_release_governance proof_required: - platform_artifacts - ci_cd_workflows - governance_examples - security_provenance_examples - devex_documentation - architecture_review identity_disclosure: candidate-controlled until required
Future team under this lead
The human-facing counterpart
M5-GitHub & Business Activation Guide
OR-001 makes the open platform trustworthy and operable. OR-002 makes that platform understandable to nontechnical members and helps them safely configure their business stack.