This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

abcd should help the technical facilitator of every abcd-managed repository set up the same personal-identifier protection this repository now has, as easily as possible. That means: no org member's login or name in any tracked file or anything abcd pushes or publishes (records, fixtures, credits, the site's contributors page, reservation and announcement trailers and ref names), with commit author fields left as the person's identity; code-owner sign-off through an org team rather than named people; test fixtures that use the standard abcd personas from .abcd/development/personas.json instead of invented or real names; and a private-names list that always and automatically includes the machine's names, its local user accounts and the org's members and collaborators. Today each of these was set up by hand in one repository, and a managed repository gets none of it.

issueopenminoriss-2610290811187925

abcd should help the technical facilitator of every abcd-managed repository set up the same personal-identifier protection this repository now has, as easily as possible. That means: no org member's login or name in any tracked file or anything abcd pushes or publishes (records, fixtures, credits, the site's contributors page, reservation and announcement trailers and ref names), with commit author fields left as the person's identity; code-owner sign-off through an org team rather than named people; test fixtures that use the standard abcd personas from .abcd/development/personas.json instead of invented or real names; and a private-names list that always and automatically includes the machine's names, its local user accounts and the org's members and collaborators. Today each of these was set up by hand in one repository, and a managed repository gets none of it.

Frontmatter

idiss-2610290811187925
typeissue
lifecycleopen
severityminor