Embedded WG meeting, July 2

[japaric]

6-7 PM CEST on Google hangouts

Agenda.

• Upgrade to LLVM's master branch (LLVM 7) rust-lang/rust#51966

• Rust 2018: the home stretch. cf. https://internals.rust-lang.org/t/rust-2018-the-home-stretch/7810

• Maintaining the cortex-m ecosystem. cf. Maintenance of core parts of the embedded / Cortex-M ecosystem #46, Embedded WG meeting, June 25 #109 (comment)

• Triaging issues on the 2018 edition milestone.

• Commercial testimonials. cf. Collect commercial testimonials and well polished examples for the revamped website / embedded WG page #108

[korken89]

Hi, will the link to the meeting be shared here when it's approaching?

[japaric]

This meeting happened! Minutes are up here. The agenda for the next meeting is in #111.

---

@korken89 you made a question on IRC. Answering here since you are not online over there.

What does it take to join the WG team, and do you happen to have a reference for the how the
Embedded WG works internally? I only have experience of C++'s SG14 (embedded / low-latency trading
/ gaming) WG where all meeting were open, so closed meetings strikes me as a bit odd, but I am not
very familiar with how Rust's WGs works yet.

The WGs operate a bit differently from Rust teams. How a WG operates is entirely up to its lead. For
the embedded WG, which I lead, we have a video meetings the first week of each month which only
the "team" attends -- minutes for these meetings are published in this repository. All other
meetings are done in IRC and are free for everyone to attend. Discussions in the issue tracker of
this repository are, of course, also open to anyone.

Rust teams tend to operate more uniformly: most of them only have video meetings, some have a 50/50
mix of video and IRC meetings (mostly for triaging issues) and one or two only have IRC meetings.
Rust teams also have the job of reviewing and merging RFCs relevant to their area (compiler
changes, language changes, tooling, etc.).

That being said you don't have to be in the WG "team" to participate in the GH / IRC discussions,
propose stuff (just open an issue here), or work on existing issues. The "team" has a few more
responsibilities than other participants: writing the biweekly newsletter, triaging issues (i.e.
posting updates) in this repo and writing meeting minutes. And the lead has the extra task of
communicating more directly (e.g. reporting needed language features and critical bugs) with the
other Rust teams.

[korken89]

Thank you for the clarification! Helps a lot to understand how it all operates.