Stream: t-compiler/wg-meta

Topic: parallelization WG


nikomatsakis (Feb 27 2019 at 20:12, on Zulip):

So @mw or @Zoxc, would one of you be up for creating the template file for the parallelization working group?

There are instructions in the compiler-team repository. I can create the Zulip stream/user-group -- what should I call it?

Maybe wg-parallel-rustc?

Zoxc (Feb 27 2019 at 21:00, on Zulip):

So is wg-compiler-performance too broad to cover this?

mw (Feb 28 2019 at 11:27, on Zulip):

I'll create the WG.

mw (Feb 28 2019 at 11:29, on Zulip):

@Zoxc, as part of the governance discussion during the steering meetings and the all hands, the compiler team made the plan to have explicit working groups for specific tasks. More concretely, for tasks with concrete goals (e.g. "make parallel rustc the default") instead of more vague ones (e.g. make the compiler faster).

mw (Feb 28 2019 at 11:30, on Zulip):

The purpose of these working groups is to provide insight into what the time is actually doing at any given point in time.

mw (Feb 28 2019 at 11:31, on Zulip):

Usually such a working group has 2 or more leaders.

mw (Feb 28 2019 at 11:32, on Zulip):

and each working group has an entry here: https://github.com/rust-lang/compiler-team/tree/master/working-groups

mw (Feb 28 2019 at 11:32, on Zulip):

wg-compiler-performance turned out to be kind of an odd bird.

mw (Feb 28 2019 at 11:33, on Zulip):

it is more of a communication device than a working group (for the definition of "working group" that we are now using)

mw (Feb 28 2019 at 11:33, on Zulip):

@nikomatsakis do you have links to the discussion during all hands?

mw (Feb 28 2019 at 11:33, on Zulip):

this is probably a good one: https://paper.dropbox.com/doc/Topic-Organizational-Planning--AYYWmomNsUrvqG~0XHEKphO9Ag-f2C6R3Qic5WSDfEORTW9I

mw (Feb 28 2019 at 11:35, on Zulip):

@Zoxc It would be great if I could list you as one of the (initially) two leaders of the parallelization working group.

mw (Feb 28 2019 at 11:35, on Zulip):

and then we could come up with concrete goals :)

mw (Feb 28 2019 at 11:35, on Zulip):

there is no strict requirement for have regular meetings

mw (Feb 28 2019 at 11:36, on Zulip):

we'd get our own Zulip stream though :)

Zoxc (Feb 28 2019 at 12:04, on Zulip):

It seems like wg-compiler-performance could have some more concrete goals though. Also the requirements for incremental compilation tend to overlap well with parallelization. For example https://github.com/rust-lang/rust/pull/58019 and https://github.com/rust-lang/rust/pull/58679 parallelizes passes which were previously made incremental.

Zoxc (Feb 28 2019 at 12:04, on Zulip):

But you can add me as a lead

mw (Feb 28 2019 at 13:17, on Zulip):

I think the goal is for a working group to go out of existence once its goals are reached.

mw (Feb 28 2019 at 13:24, on Zulip):

@Zoxc what do you think of the name wg-parallel-rustc as @nikomatsakis suggests?

Zoxc (Feb 28 2019 at 13:45, on Zulip):

I can't think of anything better =P

mw (Feb 28 2019 at 13:48, on Zulip):

yes, seems fine :)

mw (Feb 28 2019 at 13:53, on Zulip):

I created @WG-parallel-rustc but can't add anyone to it.

mw (Feb 28 2019 at 13:53, on Zulip):

@nikomatsakis Could you create the zulip stream? Or give me permissions?

davidtwco (Feb 28 2019 at 13:56, on Zulip):

I've made #t-compiler/wg-parallel-rustc.

nikomatsakis (Feb 28 2019 at 16:19, on Zulip):

Did you make a Zulip user group @davidtwco ? Should we?

nikomatsakis (Feb 28 2019 at 16:19, on Zulip):

I think we should :)

nikomatsakis (Feb 28 2019 at 16:19, on Zulip):

But it doesnt' really matter that much

davidtwco (Feb 28 2019 at 16:25, on Zulip):

I think one was already made.

nikomatsakis (Feb 28 2019 at 16:30, on Zulip):

:+1:

mw (Feb 28 2019 at 16:42, on Zulip):

Opened https://github.com/rust-lang/compiler-team/pull/15

mw (Feb 28 2019 at 16:43, on Zulip):

Let me know if you agree with the things in there, @Zoxc (especially regarding the goals).

Last update: Nov 18 2019 at 01:20UTC