# Embedded Rust in 2019
[+WG Embedded Rust All Hands 2019 Topics](https://paper.dropbox.com/doc/WG-Embedded-Rust-All-Hands-2019-Topics-JrPzUM1Z3SC859MS03lfC)

| Audience      | WG-embedded and anyone interested |
| ------------- | --------------------------------- |
| When          | Wednesday 9:00 AM - 10:00 AM      |
| Where         | Snow                              |
| Meeting Style | Brainstorming                     |

**Deliverables**

[ ] Embedded Rust 2019 theme and slogan

**Agenda**

- Brainstorm theme and slogan for embedded Rust in 2019 (20 minutes)
- Brainstorm theme-related goals (20 minutes)
- Identify and prioritize high ROI work items (20 minutes)

**Minutes**


- Last year was “Embedded Rust on Stable”
- We want to set up a theme for this year
- Mentioned on IRC:
    - Grow the ecosystem
    - Don’t maintain all the crates
    - Support the community
        - Give good guidelines on how to write APIs
    - Requests from the community:
        - USB Libraries (Device/Host)
            - Some people are working on this
                - STM, EFM, Nordic
        - RTOS
            - Pure Rust
            - Bindings
        - Libraries
            - Lib Blitz
                - Try to get important crates to 1.0 quality
                - Lots of these don’t exist already
                - Create a team focused on that?
                    - Prioritize things?
                - Not everyone has the same hardware
                    - Some vendors have expressed interest in sponsoring hardware
                    - Figure out how to distribute hardware
                    - Kick people off in person?
                - More advising, less development (from the WG perspective)
- Most improvement for the least amount of work
    - Lib Blitz
        - Review, assist API design
        - Embedded Showcase - reviewing apps instead of libs
            - Goals: Guidelines for application development
    - Documentation (“Embedded Rust By Example”, “Patterns Book”)
        - How to write a HAL crate
        - How to write an application crate
        - How to write a no_std crate
    - Identifying missing gaps - “Not Yet Awesome Embedded Rust”
        - Missing patterns
            - DMA
            - Interrupt Data Sharing
        - Tooling:
            - Post-Build Script
        - Libraries
            - logging
            - Unit conversion
            - Algebra
            - making them visible
        - Less about us doing the above, more about flagging them
        - Intermediate level documentation
        - What can they expect from us?
            - API design support?
            - Taking conversation off IRC, onto github when they need help with design?
        - Making examples more visible (in the patterns book?)

To discuss further / prioritize in the next meeting:

- Not yet awesome embedded Rust
    - get this ready for Oxidize impl days
- Patterns book (+ links to examples)
- Lib blitz
- Focus on embedded-hal (1.0?)

Theme: “Productivity”