Ask or answer
Add local context, share practical experience, cite sources, and identify what remains uncertain.
Browse questions →Build the shared foundation
There is more than one way to contribute.
Bring practical experience, a careful question, an unsuccessful trial, a sampling protocol, a dataset, analysis code, scientific review, or a clearer explanation.
Choose your path
Contribute from where you are
OpenSoil is designed so practical and technical contributions can strengthen one another without pretending they are the same kind of evidence.
Share field data
Document a baseline, intervention, outcome, source files, methods, privacy, and license.
Import workflow plannedPublish a method
Contribute a sampling protocol, calculator, indicator definition, or reproducible analysis workflow.
Versioning plannedBuild open tools
Help with schemas, APIs, R and Python workflows, accessibility, search, maps, or visualization.
Developer path formingReview evidence
Check methods, units, reasoning, citations, limitations, and whether a claim matches its evidence.
Reviewer criteria plannedTeach and explain
Create plain-language guides, calibration examples, teaching datasets, and accessible visual explanations.
Educator path plannedContribution standard
Useful does not have to mean perfect
A contribution should be honest about what it is, where it came from, and what it cannot establish.
Show the source
Attach the original report, observation, image, method, code, or reference when permissions allow.
Name the evidence type
Observation, measured value, calculation, model estimate, interpretation, or AI-assisted draft.
State limitations
Missing controls, inconsistent sampling, possible confounders, commercial interests, and uncertainty matter.
Respect ownership
Choose visibility and licensing deliberately. Do not expose private farms, clients, or unpublished research.
Founding contributors
Help define the first useful workflows
The early goal is not scale for its own sake. It is to validate whether structured questions, field timelines, project records, and transparent methods solve real problems.
- ✓Bring one real soil question
- ✓Review a trial template
- ✓Test the data vocabulary
- ✓Identify privacy concerns
- ✓Contribute a method or dataset
- ✓Improve plain-language explanations