# 1st meeting

Time: Jun 27, SAT 11:00 AM - 1:00 PM ET

## Things to discuss
- [ ] slots (https://github.com/sveltejs/svelte/pulls?q=is%3Aopen+is%3Apr+label%3Aslot)
- `<svelte:slot>` for grouping slot content
- `$$slots`
- [ ] SSR + Hydration
- [ ] Fast Hydration
- [ ] SPA Mode
- [ ] RFCS / feature requests
- How do we want to handle them? A few RFCs are just sitting there at the minute.
- Child Component Styling... + RFC + Caveats + At least a FAQ item
- There are some RFCS / feature requests that are essentially a 'yes' but this hasn't been explicitly stated or labelled. Makes it hard for contributors to know what to work on (outside of bugs).
- Should we be stricter about FRs being RFCs? What is the criteria? What is the distinction between a FR and an 'enhancement'?
- Should there be some sort of X Approvers = Merge for Docs?
- Some sort of automation for docs deploy, to reduce the dependency on Rich/Conduitry
- [ ] Sapper
- There are quite a lot of feature requests and enhancements in issues, how do we deal with all of these? RFC process for Sapper?
- Sapper config?
- Sapper as Rollup plugin?
- Kill webpack support?
- Begin to Isolate Routing?
- Other Sapper goals?
- Roadmap?
- HMR Direction
- [ ] Language Server
- Is there anything on the svelte side that can aid these efforts?
- More forgiving parser - https://github.com/sveltejs/svelte/issues/4818
- implicit TS support - https://github.com/sveltejs/svelte/issues/4797
- [ ] Preprocessors
- template expresssion processing - https://github.com/sveltejs/svelte/issues/4701
- [ ] ...