# Nushell core team meeting 2025-01-08
## Attendees
- Piepmatz
- Ian
- Rose
- Jack
- Stefan
- Andy
- Darren
- Wind
- Devyn
- Jakub

## Agenda
- [x] 2024 in review
- [ ] Plans for 2025
- [x] Core team availabilities and projects
- [x] A roadmap in a fun-driven development project?
- [ ] 0.101.0 things to fix?
- [ ] External completers can hang the shell. Signal should be handled with external completers (SIGHUP doesn't work) or possibly timeout support.
- [X] Run-time type checking for command pipeline input ([#14741](https://github.com/nushell/nushell/pull/14741))

## Discussed Topics

### 2024
- 12 big releases
- plugins
- semantics clean up
- IR
- config simplification
- New folks on the core team and in the regular meetings

### 2025
- Continued refinement of the config
- Internals
- new-nu-parser picking up steam
- ditching the AST-walking old evaluator
- despanning
- Plugins as modules, or ability to have an alias for a plugin on import.
- Modules for the builtins
- can we ditch the distinction between the default builtins and std called Nu implementations
- Rose's find from the old road to 1.0 listing
- https://docs.google.com/document/d/1JQiQMXpgxjVcI8dqAh25adxC89BeoVkzD6_HTC9k9k4/mobilebasic
- Ctrl-c issues
- no "universal" solution, have to check wherever you might have a loop
- no way to interrupt blocking I/O
- rel: [issue](https://github.com/nushell/nushell/issues/12129), [discord thread](https://discord.com/channels/601130461678272522/1314634010198278204)

### run-time level type checking
divergence between the command internal matching and the declared I/O types
same error messages can be provided