Document and systematically implement tool source and tool version somewhere
- Dominant language
- Python
- Stars
- 13
- Forks
- 17
- Avg merge
- 6h 59m
- Merged PRs (30d)
- 1
Description
> [!NOTE]
> Migrated from [augurlabs/augur#3628](https://github.com/augurlabs/augur/issues/3628)
> Originally opened by `@MoralCode` on 2026-01-26
---
tool source == Which Augur collector/task/worker inserted the data
tool version == the version of that tool
We typically only change the version when there is a significant change to its collection logic (i.e., API changes, or refactoring of collection tools).
_Originally posted by @sgoggins in https://github.com/chaoss/augur/issues/3587#issuecomment-3801178054_
If the version is only changed when significant collection changes happen to the workers, we should probably also consider giving each worker/python sub package/modular component of augur its own `__metadata__` file, possibly linked to/referring to the main one so its easy to update (and then having the tool_version pull from that)
Contributor guide
Assessment
This issue has not been assessed yet.