Compiler Team Weekly Agenda

[pnkfelix]

Prioritization Procedure for the Weekly Meeting: https://hackmd.io/pHb6eTZ2Sjy6XZmwXZHIBA?view#Prioritization-WG---Procedure

(look at the above link first; we are trying to make the above document be the canonical resource for preparing for and running the weekly T-compiler triage meeting.)

The agenda itself is constructed by following this procedure: https://hackmd.io/WJ0G17DHTHGgv0OW9I2PxA?view (which is also linked from the above document, since it is the canonical resource for running the meeting).

---

This issue exists to describe the compiler team triage meeting and to collect links about it. It is closed for comments since it's not meant to collect discussion; if you'd like to give feedback about the steering meeting, please feel free to open a topic in Zulip.

If you are looking for the description of the compiler planning (aka "steering") meeting, see #58850

Compiler Team Meeting Stuff

(A replacement for the unsupported+EOL'ed etherpad)

WHERE IS THE COMPILER MEETING TAKING PLACE

We are in the process of evaluating various chat platforms.

• See (and weigh in) at associated async discussion here: https://internals.rust-lang.org/t/where-should-the-compiler-team-and-perhaps-working-groups-chat/7894/44
  The next meeting is scheduled to take place ON ZULIP

• October 4: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/subject/weekly.20meeting.202018-10-04/near/135183234
• September 27: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/subject/weekly.20meeting.202018-09-27/near/134744613
• September 20: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/subject/weekly.20meeting.202018-09-20/near/134310881
• September 13: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/subject/weekly.20meeting.202018-09-13/near/133886161
• September 6: Discord in the #compiler channel
• August 30: Discord in the #compiler channel https://discordapp.com/channels/442252698964721669/443151243398086667/484724478689935360
• August 23: Zulip https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202018-08-23
• August 16: Zulip https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202018-08-16
• August 09: Zulip https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202018-08-09
• August 02: Zulip https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202018-08-02

If you are the meeting organizer, you can see the steps for running the meeting after the Agenda section below.

AGENDA

Short period for any announcements

Review/Continue Weekly Pre-Meeting Triage (30min)

• Either enumerate unassigned P-high issues, or ask people to review them (based on how many other items will fill up agenda).
• Explicitly enumerate the beta-backport nominations and stable-backport nominations.
• If there is time,
  • Waiting for our team, and
  • I-nominated T-compiler

Working Grop Check-in (30min)

• schedule

Procedure (for meeting organizer)

• On the day of the meeting, some hours before hand, create two #t-compiler topics on Zulip
  • First topic name weekly meeting YYYY-MM-DD #54818; message text:

    Hi @*T-compiler/meeting* ; the triage meeting will be starting in H hours M minutes

  • Second topic name pre-meeting triage YYYY-MM-DD #54818; message text:

    I will be doing pre-triage in this channel.

  • Right-click that first pre-triage message, choose "Copy link to conversation", then post that link into the weekly meeting channel, with text like:

    I will be doing [pre-triage in a parallel topic](LINK-GOES-HERE)

  • If you haven't already, figure out which working groups (at most two) should do their check-in's this week. Consult the WG checkin schedule. In any case, state on in meeting topic channel which WG's will be doing check-ins, and be sure to @-address the relevant leads as reminders to them.
  • Switch now from the meeting channel to the pre-meeting triage channel, and do the pre-triage (see process with lists of issues below).
    • If during the pre-triage you identify issues that are worth bubbling up to the larger group, post corresponding messages back on the meeting channel itself.
• When it is time for the meeting to start:
  • Write Hi @*T-compiler/meeting*! Add a :wave: emoji to show you're here :) in the meeting channel to announce it is starting (and get an approximate attendees list).
  • Immediately after starting the meeting, state that there are 5 minutes for general announcements that anyone can chime in on.

PERSISTENT URLs

Pre-triage Process

• Unprioritized I-nominated issues T-compiler and also no team assigned (for comparison see all-teams); prepass to identify candidates for P-high marking.
  • As you traverse the nominated issues, be sure to remove nomination tags from issues where it is not clear whether there is actually a point to discuss. (Sometimes nomination is just an implicit request for prioritization.)
• Also for pre-pass: beta-regressions without P-label and nightly-regressions without P-label
• Also for pre-pass: I-nominated issues where the label should be removed (e.g. because it was discussed in the last meeting).
• I-BetaNominated T-compiler, and also no team assigned (see also all-teams).
  • During pre-triage, make sure to add T-compiler where appropriate to the cases of no team assigned.
• I-StableNominated T-compiler (and all-teams)
• Traverse Waiting for our team and explicitly nominate any that you think may be able to be resolved quickly in triage meeting.
• P-high T-compiler
  • P-high T-compiler unassigned

• Pre-triage may reveal bugs that are good candidates for the ICE-Breakers (groups dedicated to hopefully-small tasks in focused sub-areas). You can tag issues accordngly with the corresponding team.

---

• Stable-to-beta regressions (all! not just T-compiler)
• Stable-to-nightly regressions (all! not just T-compiler)

---

• Waiting for our team
• I-nominated T-compiler and (all-teams)

---

• Outstanding Tool Breakage (needs a link for appropriate github search)

• Unprioritized T-compiler

  • Just our team's ICEs
  • Just our team's non-ICEs

• Stable-to-stable regressions (all! not just T-compiler)
  • excluding things already labeled

• RFC spreadsheet
• RFCs
• perf regressions
• rust-icci regressions

RLS Related things

• A-rls bugs not tagged T-compiler
• T-dev-tools bugs not associated with other teams

IRC nicks to ping when meeting starts

Add yourself if you are missing in the list and want to get pinged

nmatsakis eddyb oli_obk nagisa pnkfelix mw varkor oli_obk_ qmx wesleywiser davidtwco

AGENDA

Move away from etherpad, possible solutions:

• a gist (this page is mostly static anyway)
• a google doc
• a dropbox paper
• https://notepad.pw
• https://cryptpad.fr (has a markdown thingy)
• http://hackmd.io

eddyb writes:

#48575 (comment)

nox writes:

#50825 is a blocker to do a rustup in Servo and see the impact of MergeFunctions there.

[pnkfelix]

(discussion with some other team members made me realize that there's no reason for this issue to remain open, even if I still want to keep the number around for ease of hyperlinking from e.g. zulip. People can still visit closed issues, edit them, etc)