# Nushell core team meeting 2024-03-06
## Attendees
- Darren
- Ed
- Jack
- Michael
- Ian
- Devyn
- ndyg
- Sophia
- Jakub
- Stefan
- Windsoilder
- Antoine
- Yash

## Agenda
- [x] Point release?
- [x] Are the selection (shift-arrow) panics resolved or do we need the clipboard PR?
- [ ] 24h emergencies?
- [x] du --exclude glob
- [x] [`calendar <tab>` alias panics](https://github.com/nushell/nushell/issues/12090)
- [x] Revisiting XDG

## Discussed Topics

### new release
Normal level of new issues -> no point release warranted so far
known issues seem QoL problems that can be resolved in the regular work

### config dir location: XDG
Sophia reencountered the sentiment pro-XDG on twitter

- platform specific standard seems to expands to more tools/platforms
- a lot of attempts

Darren: still the login-shell chicken-egg problem

General sentiment: let's implement for the config

#### login-shell is a different beast
-> among our developers it is a fraction that regularly runs nu as a tru login shell
-> Survey 30% replied to the question
-> among the team kubouch, ian, and wind have serious nu-login shell experience

### lightning round - Plugins
- WASM plugins?
- nushell if it contains the wasm runtime would need to grant a lot of permissions for plugins to access relevant system functionality we would expect plugins to provide
- plugin protocol evolving should allow more flexible plugin design (server style plugins, execution of closures)
- could also use different runtimes itselfs

## Issues
> :bulb: the issues which [needs-core-team-attention](https://github.com/nushell/nushell/labels/needs-core-team-attention)

> :bulb: **Note**
> to list all the PRs currently [opened in `nushell/nushell`](https://github.com/nushell/nushell/pulls):
> ```nu
> gh pr list --json url,number,author,title
> | from json
> | each {|i|
> $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
> }
> | reverse
> | to text
> ```