Skip to content

0015 contributions in git

github-actions[bot] edited this page Nov 17, 2026 · 1 revision

Data contributions start as pull requests; a web editor comes later

Status: accepted · Implementation: planned · Date: 2026-11-17

The file format, the schema and where the data sits in the workspace are not chosen yet and get their own record.

Context

The database (ADR 0013) needs a way for people to add and correct records. The large crowd-sourced projects have web editors with accounts, public edit history and voting (MusicBrainz), or open editing with moderators who revert (Open Food Facts). Both need a server, accounts and a privacy policy, which LibreLifts does not have (ADR 0005), and people to moderate.

OpenPowerlifting takes all of its data as merge requests to a git repository, and that has been enough for a large public dataset.

Decision

  • At first the data is files in the repository, and a contribution is a pull request. It follows the same workflow as code (ADR 0012).
  • CI checks every data change: the schema, that ids are unique and never reused, and that every media file has an author, a source and a licence (ADR 0014).
  • Git is the edit history. Who changed what, and when, is public from the first record.
  • A web editor comes later and gets its own record. It is built when pull requests demonstrably hold contributors back, not before. It will need accounts, a public history of edits, review before a change is applied, and limits on new accounts.

Consequences

  • Contributing costs the project nothing to host, and one maintainer can review it.
  • Only people who can use git and GitHub can contribute at first. That keeps early quality high and the number of contributors low.
  • Translations and media are awkward as pull requests. They are the likely first reasons to build the editor.
  • Two things are left open on purpose: whether the data moves to its own repository, and how review is shared once there is more than one reviewer.

Clone this wiki locally