Merge pull request #497 from nikomatsakis/master

announce upcoming lang/compiler design meetings

Author: nikomatsakis

posts/inside-rust/2020-01-24-feb-lang-team-design-meetings.md

@@ -0,0 +1,32 @@
+---
+layout: post
+title: "February Lang Team Design Meetings"
+author: Niko Matsakis
+description: "Lang Team Design Meetings scheduled for February"
+team: the language team <https://www.rust-lang.org/governance/teams/lang>
+---
+
+We've scheduled our **language team design meetings** for February. The current plans are as follows:
+
+* February 3rd -- we will do an overview of **specialization**. We'll cover details from the RFC but in particular talk about the [as-yet-unimplemented plans to make it sound](http://aturon.github.io/tech/2018/04/05/sound-specialization/).
+* February 10th -- we will cover interactions between the `&T` type and LLVM's dereferenceable attribute, such as [rust-lang/rust#55005](https://github.com/rust-lang/rust/issues/55005) and [problems modeling MMIO](https://github.com/japaric/volatile-register/issues/10).
+* February 17th -- no meeting, it is President's Day in the US and many of us are absent
+* February 24th -- we will summarize discussions from [the ffi-unwind project group] about whether we should permit foreign exceptions to propagate across the "C" ABI boundary, or establish a separate ABI (e.g., "C unwind") for such cases.
+
+[the ffi-unwind project group]: https://github.com/rust-lang/project-ffi-unwind
+
+## About the language team design meetings
+
+The idea of the design meeting is that it's a time for us to have
+in-depth discussions on some particular topic. This might be a burning
+problem that we've discovered, an update on some existing design work,
+or a forward looking proposal.
+
+The meetings are open for anyone to listen in and attend. They are
+typically also recorded and posted online, along with minutes, after
+the fact. They generally take place on Mondays at "noon Boston time"
+-- but for the precise scheduling you should check the [lang team
+calendar]. Scheduled meetings are subject to change and
+cancelation. In that case, the calendar events will be updated.
+
+[lang team calendar]: https://github.com/rust-lang/lang-team/#meeting-calendar

posts/inside-rust/2020-01-24-upcoming-compiler-team-design-meetings.md

@@ -0,0 +1,33 @@
+---
+layout: post
+title: "Upcoming compiler-team design meetings"
+author: Niko Matsakis
+description: "Upcoming compiler-team design meetings"
+team: the compiler team <https://www.rust-lang.org/governance/teams/compiler>
+---
+
+In our [planning meeting on January 17], the [compiler team] has scheduled our
+next batch of upcoming design meetings. You can find the exact times
+on the compiler team's [meeting calendar]:
+
+* On Feb 7th ([calendar event][ce1]), we will discuss
+  [rust-lang/compiler-team#237], which describes some potential ways
+  to extract a Rust parser that can be shared between rustc and
+  rust-analyzer.
+
+[rust-analyzer]: https://github.com/rust-analyzer/rust-analyzer/
+[ce1]: https://calendar.google.com/event?action=TEMPLATE&tmeid=Mmk4NmZqaWVtcHVmZDRmanZob3ZrMXJ1N28gNnU1cnJ0Y2U2bHJ0djA3cGZpM2RhbWdqdXNAZw&tmsrc=6u5rrtce6lrtv07pfi3damgjus%40group.calendar.google.com
+[rust-lang/compiler-team#237]: https://github.com/rust-lang/compiler-team/issues/237
+
+### Did you know?
+
+Most weeks, the compiler team has some sort of design meeting. These
+meetings take place on Zulip and are open to all. Every 4 weeks, we do
+a planning meeting to pick the next few meetings from the list of open
+proposals. You can find [more details about how the compiler-team
+steering meeting process here][details].
+
+[details]: https://rust-lang.github.io/compiler-team/about/steering-meeting/
+[meeting calendar]: https://rust-lang.github.io/compiler-team/#meeting-calendar
+[planning meeting on January 17]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/planning.20meeting.202019.2E01.2E17
+[compiler team]: https://www.rust-lang.org/governance/teams/compiler