Discuss the work
Post questions and evidence on the Project, Resource, or Version they concern.
Collaboration
Share evidence without losing ownership.
Discuss Projects, request data, develop a contribution branch, or fork a published Version. Each path keeps its own history and attribution.
Discuss the exact work. Questions and evidence stay with the Project or Resource they concern.
Ways to contribute
Choose the path that fits the work.
Use a discussion for context, a Data Request for structured evidence, a branch for proposed changes, or a fork for independent work.
Respond to a Data Request
Send answers, measurements, observations, or files under the request’s stated requirements.
Develop a contribution
Start from a public Version and work on a branch that remains under your control.
Fork a Version
Create a new Project with its own owner and direction while preserving the source lineage.
Data Requests
Ask for evidence, data, or responses.
A Data Request states what the Project needs, how to respond, and who decides whether a response is used.
Ask
State what the Project needs and the conditions a response must meet.
Respond
Send the requested answers or files with consent and requirements attached.
Review
The Project owner accepts or rejects each response.
Use
Accepted responses can become a Dataset Resource with the decision history attached.
Branches and forks
Control stays with each owner.
A contribution changes the canonical Project only after review. A fork remains independent.
A contribution branch stays separate
Its owner controls the work until the Project owner accepts a proposed change.
The Project owner reviews changes
A contribution does not alter the canonical Project on its own.
A fork is independent
It becomes a new Project with a separate owner and direction.
Attribution and lineage remain
Versions record the people, agents, sources, responses, and earlier work behind them.
Start a Project