Skip to content

chore: establish public maintainer and security governance #169

Description

@0monish

Problem

The repository lacks a Code of Conduct and maintainer identity, CODEOWNERS lists a broad individual set because no team exists, and the security policy points to private reporting without establishing its settings/support scope. Main currently requires no approval.

Scope

CODE_OF_CONDUCT.md, MAINTAINERS.md, SECURITY.md, .github/CODEOWNERS, .github/ISSUE_TEMPLATE/config.yml, and narrowly scoped public-intake changes in AGENTS.md/docs/agents/workflow.md/coordination consumers as needed. GitHub team, Discussions, private reporting and repository protection settings.

Acceptance

  • Identify @0monish as confirmed applicant/founding maintainer and retain real existing maintainers.
  • Create visible @gyldlab/keld-maintainers with repository write authority, without granting new outside users access.
  • CODEOWNERS parses and covers critical paths using that valid team.
  • Publish enforceable conduct/reporting and pre-release security-support policies with working contact routes.
  • External contributors can use public GitHub issues and ordinary forks/branches; internal agents retain claims/specs/gates.
  • Require PR, current CI checks, at least one independent approval and critical CODEOWNER review; deny force-push/deletion and preserve administrator enforcement.
  • Record before/after settings and independent review; no fabricated independent participation.

The user explicitly approved this foundation/governance direction. Linear connectivity was verified after initial tool discovery. Internal claims and dependencies remain in Linear; public contributors use GitHub without needing private access. No product boundary change.

Internal coordination

Maintainer execution: KEL-179. Public scope, progress and acceptance remain visible here; contributors do not need access to the internal board.

Activity

  1. self-assigned this
    on Sep 7, 2026
  2. added
    foundationOpen-source foundation readiness and its evidence
    on Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

foundationOpen-source foundation readiness and its evidence

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions