FORK-001

Repository Naming

Patched-source repositories use a consistent `patch-` name in the finos-osera GitHub organization.

Status: Draft
Version: 0.1.0
Pack: OSERA-SP-0.1.0 candidate
Ratified: Not ratified
Fitness: Required check
Category: Fork Management
Applies to: Patch providers, OSERA maintainers
Machine-readable: YAML / JSON

Structured Requirements

FORK-001.REQ-001 MUST automated

Patched-source repositories must live in github.com/finos-osera unless the working group approves an exception.

Check	Severity	Evidence
FORK-001.CHECK-001 Repository is in the finos-osera organization	blocking	repository_url

FORK-001.REQ-002 MUST automated

Patched-source repositories must use the prefix patch- followed by the upstream repository or artifact name.

Check	Severity	Evidence
FORK-001.CHECK-002 Repository name uses the patch prefix	blocking	repository_name

Requirement

Patched-source repositories MUST live in the github.com/finos-osera organization unless the working group approves an exception.

Patched-source repositories MUST use the prefix patch- followed by the upstream repository or artifact name.

The repository name SHOULD NOT include osera when the repository already lives in the finos-osera organization. OSERA identity SHOULD be carried by organization ownership, feed metadata, and release evidence instead of duplicating it in every fork name.

Rationale

The prefix distinguishes forked upstream projects from OSERA governance, tooling, and operations repositories.

Because the repositories are public, the GitHub fork relationship with the upstream project SHOULD be preserved where possible.

Avoiding osera inside each repository name keeps fork names short and leaves the upstream project name prominent. The patch- prefix is intended to be broad enough for backports, downstream-only security fixes, and future remediation workflows without implying that every OSERA patch is strictly a backpatch.

Existing finos-osera/backpatch-* repositories are treated as legacy/proof-of-concept evidence that predates this standard.

Evidence

Consumers SHOULD be able to identify:

the OSERA fork URL;
the upstream project URL;
whether GitHub retains the fork relationship;
the artifact coordinates covered by the repository.