---
# System prepended metadata

title: Nushell core team meeting 2025-09-10

---

# Nushell core team meeting 2025-09-10
## Attendees
- Bahex
- Jakub
- Storm
- Rose
- Piet
- Stefan
- Darren
- Andy
- Jan9103
- 

## Agenda
- [ ] Revisit focus periods providing everyone has had enough time to think about the topic. We may have a thread in the core team channel regarding how to move forward
[Bahex Focus Periods](https://hackmd.io/kqrs9PkWRAapm-_0m4W7pg)
- [x] Quick question on issue status labels
- [x] 

## From Last Week
- [ ] Check in with Devyn if he is in our meeting next week so he can give us some more insight regarding PR 13414 in concert with 16523

## Discussed Topics

### Taking topics from the Vibesroadmap
#### Documentation
- out of dateness
    - split between two repos 
    - Rose: merge velocity vs docs requirement
    - https://hackmd.io/v7X5XWjGSJKk4YIKTxpaBA
- Search 
    - algolia powerful but has quirks
- Can we automate more parts
    - Stefan: default_config.nu could this be turned into a synced page
    - Piep: executing code examples in the prose docs to ensure 
    - building our own "cargo doc"
- semi-automate
    - label for tracking PRs that still need to land in the docs repo
    - autogenerate issues on the doc repo based on that?
        - tag the author/original PR id

### sqlite commands - Piepmatz new fun project
- Started as an attempt to improve error handling
- SQL injection risks
- wonky API shared across the different commands: `into sqlite`, `open`, `query db`, `history`, `stor`
- `into sqlite`: rename `to sqlite` makes sense as it is not a cast but its not generating data that can then be passed to `save` (currently it is a save operation itself)
- custom value type for sqlite connection ->
    - `from db`
    - `from sqlite`
    - `to db`
    - `to sqlite`
 
### Side discussion: benchmarking
- we don't trust the `tango` output (main..main, reruns flaky)
- `criterion` was bulky to handle -> antoine implemented a tracking repo that run 
- `divan` was the nicest to write rust benchmarks for but no automatic output for fair comparison available at the time

### Status labels:
- `status:ready-for-implementation`
