Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiler Team Weekly Agenda #54818

pnkfelix opened this issue Oct 4, 2018 · 1 comment

Compiler Team Weekly Agenda #54818

pnkfelix opened this issue Oct 4, 2018 · 1 comment


Copy link

@pnkfelix pnkfelix commented Oct 4, 2018

Prioritization Procedure for the Weekly Meeting:

(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: (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)


We are in the process of evaluating various chat platforms.

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


Short period for any announcements

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

Working Grop Check-in (30min)

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.


Pre-triage Process

  • 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.

RLS Related things

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


Move away from etherpad, possible solutions:

eddyb writes:

#48575 (comment)

nox writes:

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

@pnkfelix pnkfelix closed this Oct 4, 2018
@pnkfelix pnkfelix reopened this Oct 4, 2018
@rust-lang rust-lang locked as off-topic and limited conversation to collaborators Oct 4, 2018

This comment has been hidden.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants