Document the data-governance model - #43
Open
timlichtenberg wants to merge 1 commit into
Open
timlichtenberg wants to merge 1 commit into
timlichtenberg wants to merge 1 commit into
Conversation
Add an Explanations page that states the policy the manifest-and-registry mechanism enforces: what counts as a data change, who may make one, and how it is reviewed and tested. A dataset is pinned by two committed files, a fetch reads the committed registry rather than the live Zenodo record, and a data change takes the same pull-request path as a code change. The page states the testing asymmetry plainly: the scheduled drift check covers only the shared manifest, and a model's own datasets get the pull-request review but no scheduled drift check in fwl-io. It links to the design and manifests pages for the mechanism and adds one nav entry under Explanations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an Explanations page stating the policy the manifest-and-registry mechanism enforces: what counts as a data change, who may make one, and how it is reviewed and tested. A dataset is pinned by two committed files, a fetch reads the committed registry rather than the live Zenodo record, and a data change takes the same pull-request path as a code change. Closes #22.