OvertureMaps / OvertureMaps/stac
Stop framing the README as a Rust-vs-Python migration
Open
@jjcfrancisco is already working on this.
Since Sep 18, 2026.
- Dominant language
- Rust
- Stars
- 39
- Forks
- 3
- Avg merge
- 4d 18m
- Merged PRs (30d)
- 7
Description
Type
Task
Scope
Multi-theme or Platform
Skillset
engineering
Description
Context
The README still reads like a migration announcement — Rust-vs-Python framing, a parity section, and a "verify against the Python implementation" section pointing at the migration PR. That was useful during the switchover; it isn't anymore. This is the tool now, and someone landing on the repo shouldn't have to parse the history first.
Proposed change
In README.md:
- Drop "(Rust)" from the title and rewrite the opening so it says what the tool does (generate, validate, reconcile) instead of what it replaces.
- Delete the
## Parity strategysection. - Delete the
## Verify against the Python implementationsection.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.