Closed
Description
Now that we've renamed anaconda-conda-telemetry to conda-anaconda-telemetry to better account for internal naming (e.g. request header name), I think we're fine to either:
- rename this project to conda-anaconda-tos or
- just conda-tos (assuming we're going to push for having tos.json as a subset of the "vendor-neutral channel registry" CEP idea or a similar standard, maybe just focused on
tos.json)
Since we'll likely want to have buy-in for the tos.json from other conda compatible clients like mamba and pixi, it's going to be important to work on these standards at a community level.
Metadata
Metadata
Assignees
Labels
No labels