Right now our two main repos are stac-rs (Rust crates) and stacrs (Python package). There's some obvious problems:
- It's not clear, at first glance, why stacrs is a Python package
- It's not clear which repo to open an issue on if you're having a problem
- It's not clear what a new repo w/ bindings to another language (e.g. R) should be named
During Development Seed team week 2025, we whiteboarded the idea of a rename to rustac:


Advantages
- Clear, memorable name
- Still has
*stac* in the name to indicate what it's for
- Scales to other languages:
- rustac-py: Python
- rustac-r: R
- ...?
- Vibes with "rustic", which brings to mind a cabin and maybe a whisky
Disadvantages
- We already have mind share around stacrs
- Renames are annoying for both maintainers and users
Open questions
If we decide to implement:
- When do we do it?
- Do we restart version numbers? (@gadomski thinks no)
- What packages do we actually rename?
- Rust: keep as stac, stac-api, etc
- Python: We do want to move to rustac
Actions
#653
Right now our two main repos are stac-rs (Rust crates) and stacrs (Python package). There's some obvious problems:
During Development Seed team week 2025, we whiteboarded the idea of a rename to rustac:
Advantages
*stac*in the name to indicate what it's forDisadvantages
Open questions
If we decide to implement:
Actions
#653