Prepare a contribution
Make an observation useful before sharing it.
Describe the software and setup
- Application or library name and exact version, when known.
- Operating system, protocol, and relevant configuration.
- Capture tool revision, capture point, and repeatable steps.
- Observation period, scheme ID and revision, and output value.
- Evidence supporting a label and anything that remains uncertain.
Review privacy and permission
Share only observations you have permission to collect and publish. Do not prepare packet dumps, credentials, request bodies, IP addresses, hostnames, or identifying request paths for public upload. Canonical inputs can also contain identifying material; a hash or formatter output is not automatically safe.
The publication field allowlist and contributor terms are still being defined. A future submission channel will state exactly what it accepts.
Corrections are contributions too
When a record is available, cite its dataset version and record identifier. Explain the disputed field, provide supporting evidence, and distinguish a better label from a changed fingerprint. Do not infer intent from a collection source alone.
Planned publication process
Samples will be checked for permissions, privacy, reproducibility, and label evidence before publication. Reviewers will retain uncertainty and source attribution, document corrections, and produce versioned releases.
Read the community approach and the planned contributor terms.