Stream: t-compiler/wg-meta

Topic: meeting 2019.05.02


nikomatsakis (May 02 2019 at 18:00, on Zulip):

Hello @T-compiler/WG-meta =)

nikomatsakis (May 02 2019 at 18:00, on Zulip):

I can't believe it's been a week already since we last met

davidtwco (May 02 2019 at 18:00, on Zulip):

Two weeks for me.

nikomatsakis (May 02 2019 at 18:01, on Zulip):

https://github.com/rust-lang/rfcs/pull/2689 is not quite out of FCP

nikomatsakis (May 02 2019 at 18:01, on Zulip):

But once it is, there is going to be some work associated with that

nikomatsakis (May 02 2019 at 18:01, on Zulip):

But I get ahead of myself

nikomatsakis (May 02 2019 at 18:01, on Zulip):

https://github.com/rust-lang/compiler-team/issues

nikomatsakis (May 02 2019 at 18:02, on Zulip):

Or, rather, let's look at open PRs first https://github.com/rust-lang/compiler-team/pulls

nikomatsakis (May 02 2019 at 18:02, on Zulip):

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

nikomatsakis (May 02 2019 at 18:02, on Zulip):

expert map as toml file

nikomatsakis (May 02 2019 at 18:02, on Zulip):

we..can prob just land this

Santiago Pastorino (May 02 2019 at 18:02, on Zulip):

I think so

Santiago Pastorino (May 02 2019 at 18:02, on Zulip):

there's stuff to add but we can keep doing that

Santiago Pastorino (May 02 2019 at 18:03, on Zulip):

I meant, in particular directories are not filled

nikomatsakis (May 02 2019 at 18:03, on Zulip):

TOML permits comments, right?

nikomatsakis (May 02 2019 at 18:03, on Zulip):

well, nm

nikomatsakis (May 02 2019 at 18:03, on Zulip):

I was just thinking maybe it'd be nice to some spot with more details

nikomatsakis (May 02 2019 at 18:03, on Zulip):

to make it easier to read

nikomatsakis (May 02 2019 at 18:03, on Zulip):

but I think that could go more as a meta field

Santiago Pastorino (May 02 2019 at 18:03, on Zulip):

or I can make a quick pass adding some more directories and then ping you @nikomatsakis ?

nikomatsakis (May 02 2019 at 18:03, on Zulip):

either way

nikomatsakis (May 02 2019 at 18:04, on Zulip):

@Santiago Pastorino that sounds fine

Santiago Pastorino (May 02 2019 at 18:04, on Zulip):

:+1:

nikomatsakis (May 02 2019 at 18:04, on Zulip):

Finish out-of-tree crates policy. compiler-team#68

Santiago Pastorino (May 02 2019 at 18:04, on Zulip):

we can go over this PR again in next meeting after we do this :+1:

davidtwco (May 02 2019 at 18:05, on Zulip):

Should things like rustdoc be added to it? Or strictly rustc?

davidtwco (May 02 2019 at 18:05, on Zulip):

Since RLS is there?

nikomatsakis (May 02 2019 at 18:05, on Zulip):

I'm pondering @centril's comment here

One thing that I'd like to see in the out-of-crates policy is that anything that comes close to "stabilization" or "a change in semantics" in the language should always be decided on rust-lang/rust. I don't want to have to dig into submodule or crate update PRs to see if anything important, relnotes relevant, or T-Lang relevant has happened in the update.

I don't know how that can be achieved exactly -- I guess that if nothing else it would occur when we "bump" the version numbers.

nikomatsakis (May 02 2019 at 18:06, on Zulip):

Should things like rustdoc be added to it? Or strictly rustc?

I think including rustdoc makes sense

nikomatsakis (May 02 2019 at 18:07, on Zulip):

ah, I like the language you added @davidtwco -- so if that works for @centril, it works for me

davidtwco (May 02 2019 at 18:07, on Zulip):

I don't know how that can be achieved exactly -- I guess that if nothing else it would occur when we "bump" the version numbers.

I added some wording to the document, a best-effort approach.

nikomatsakis (May 02 2019 at 18:07, on Zulip):

one thought I had here:

 1. Create `P-high`, `P-med`, `P-low`, `I-nominated` and `T-compiler` labels.

we might want to also have E-mentor and such things

nikomatsakis (May 02 2019 at 18:07, on Zulip):

but for now let's just mergre the PR I guess

davidtwco (May 02 2019 at 18:07, on Zulip):

I can add that quickly if you want.

davidtwco (May 02 2019 at 18:08, on Zulip):

Save opening another PR for it.

nikomatsakis (May 02 2019 at 18:08, on Zulip):

I was imagining that it'd be nice to have the process for "finding work to do" be the same

nikomatsakis (May 02 2019 at 18:08, on Zulip):

but I think let's not add it just yet

nikomatsakis (May 02 2019 at 18:08, on Zulip):

because i think we may want to tweak that process ;)

nikomatsakis (May 02 2019 at 18:09, on Zulip):

shall I merge then?

davidtwco (May 02 2019 at 18:09, on Zulip):

Feel free.

nikomatsakis (May 02 2019 at 18:09, on Zulip):

Determine working group check-in schedule w/ a formula. compiler-team#67

davidtwco (May 02 2019 at 18:10, on Zulip):

So, I think this is sort of blocked on getting the compiler team documents into a website of some sort, it's hard to improve on the presentation of this in a markdown file IMO.

I'm fairly confident that it results in a window of two working groups each week that works for any number of working groups, I messed around in Excel for far too long confirming that.

davidtwco (May 02 2019 at 18:11, on Zulip):

I think having the schedule be more dynamic is an improvement though, as having a list that needs updating regularly with the upcoming check-ins wasn't ideal.

nikomatsakis (May 02 2019 at 18:11, on Zulip):

So, I think this is sort of blocked on getting the compiler team documents into a website of some sort, it's hard to improve on the presentation of this in a markdown file IMO.

Agreed -- here is a question

nikomatsakis (May 02 2019 at 18:12, on Zulip):

I was contemplating making the first "Help wanted" thing be "somebody to do that work"

davidtwco (May 02 2019 at 18:12, on Zulip):

Feel free to disagree with that though, I don't run the meeting so it isn't me it'll affect.

nikomatsakis (May 02 2019 at 18:12, on Zulip):

I think I agree

nikomatsakis (May 02 2019 at 18:12, on Zulip):

it's probably ok for it to just run on autopilot

nikomatsakis (May 02 2019 at 18:12, on Zulip):

some groups might get skipped once in a while if we e.g. skip a meeting

nikomatsakis (May 02 2019 at 18:12, on Zulip):

but that does't seem like the end of the world :)

davidtwco (May 02 2019 at 18:14, on Zulip):

I was contemplating making the first "Help wanted" thing be "somebody to do that work"

Assuming by "that work", you mean, "website-ify the compiler team repo", I'm happy with that.

nikomatsakis (May 02 2019 at 18:14, on Zulip):

Yes, that's what I meant

davidtwco (May 02 2019 at 18:14, on Zulip):

I can try to carve out time to do it myself if it starts being a blocker for other things we want to do.

nikomatsakis (May 02 2019 at 18:16, on Zulip):

OK, well, shall we look at the issues? (link fixed)

nikomatsakis (May 02 2019 at 18:16, on Zulip):

oops, wrong link :)

Santiago Pastorino (May 02 2019 at 18:17, on Zulip):

last meeting we've said that the ones which we should pay attention are the assigned ones, right?

Santiago Pastorino (May 02 2019 at 18:17, on Zulip):

the other are more like ideas

Santiago Pastorino (May 02 2019 at 18:17, on Zulip):

unsure if that still applies

davidtwco (May 02 2019 at 18:17, on Zulip):

I think there are some that are ideas and some that are more concrete to-do list items for us.

Santiago Pastorino (May 02 2019 at 18:17, on Zulip):

you meant, still unassigned?

nikomatsakis (May 02 2019 at 18:18, on Zulip):

it is a bit of a mix

Santiago Pastorino (May 02 2019 at 18:18, on Zulip):

anyway, at some point we would need to decide what to do with the ideas, right? :smile:

nikomatsakis (May 02 2019 at 18:18, on Zulip):

e.g. Unify labels across compiler team repositories. compiler-team#65 feels like a work item

nikomatsakis (May 02 2019 at 18:19, on Zulip):

but I guess the question is -- do we want to assign thing presently unassigned :)

davidtwco (May 02 2019 at 18:19, on Zulip):

I think only compiler-team#64 and compiler-team#56 are ideas.

davidtwco (May 02 2019 at 18:19, on Zulip):

Maybe compiler-team#62 too.

Santiago Pastorino (May 02 2019 at 18:20, on Zulip):

but I guess the question is -- do we want to assign thing presently unassigned :)

I guess we should

nikomatsakis (May 02 2019 at 18:20, on Zulip):

https://github.com/rust-lang/compiler-team/issues/58

nikomatsakis (May 02 2019 at 18:20, on Zulip):

seems like an easy one

davidtwco (May 02 2019 at 18:21, on Zulip):

Only reason I haven't done it was because it is sort of subsumed by the formulaic schedule.

nikomatsakis (May 02 2019 at 18:21, on Zulip):

I feel like things are "pretty ok", I guess we'll see what happens tomorrow

nikomatsakis (May 02 2019 at 18:21, on Zulip):

at steering meeting

nikomatsakis (May 02 2019 at 18:21, on Zulip):

the main thing then is to try and maybe draw some attention to the "make dynamic repo" issue

nikomatsakis (May 02 2019 at 18:22, on Zulip):

I'll make an issue for that and assign it to me :)

davidtwco (May 02 2019 at 18:22, on Zulip):

I'm not even sure who has permissions to do this one:

Unify labels (compiler-team#65)

Santiago Pastorino (May 02 2019 at 18:22, on Zulip):

yeah unsure about that

nikomatsakis (May 02 2019 at 18:23, on Zulip):

I guess I do

Santiago Pastorino (May 02 2019 at 18:23, on Zulip):

I'm not sure what kind of permission I have in general :P

nikomatsakis (May 02 2019 at 18:23, on Zulip):

So, that's another issue we could file

davidtwco (May 02 2019 at 18:23, on Zulip):

I did comment on that with a list of repositories that seemed relevant and the labels we'd probably want.

nikomatsakis (May 02 2019 at 18:23, on Zulip):

to do the follow-on work to introduce "compiler-team contributors" rfcs#2689

nikomatsakis (May 02 2019 at 18:23, on Zulip):

I'm not even sure precisely what that is

nikomatsakis (May 02 2019 at 18:23, on Zulip):

but I have to go through and figure it out

nikomatsakis (May 02 2019 at 18:24, on Zulip):

I guess mostly editing the team repo

davidtwco (May 02 2019 at 18:24, on Zulip):

You'd need to decide who those people are.

nikomatsakis (May 02 2019 at 18:24, on Zulip):

Oh, I have a list :)

davidtwco (May 02 2019 at 18:24, on Zulip):

I assumed you would.

Santiago Pastorino (May 02 2019 at 18:25, on Zulip):

I guess introduce "compiler-team contributors" includes discussing with the rest of the rustc team

Santiago Pastorino (May 02 2019 at 18:25, on Zulip):

posting to internals

Santiago Pastorino (May 02 2019 at 18:25, on Zulip):

stuff like that I guess

nikomatsakis (May 02 2019 at 18:26, on Zulip):

yes. I think it's probably work for me to do :)

Santiago Pastorino (May 02 2019 at 18:26, on Zulip):

yes

nikomatsakis (May 02 2019 at 18:26, on Zulip):

I realize I should also check with those folks on the list to confirm

nikomatsakis (May 02 2019 at 18:26, on Zulip):

so i'll assign to me

Santiago Pastorino (May 02 2019 at 18:26, on Zulip):

:+1:

nikomatsakis (May 02 2019 at 18:27, on Zulip):

welp, seems like that covers it for today

nikomatsakis (May 02 2019 at 18:27, on Zulip):

anything else?

Santiago Pastorino (May 02 2019 at 18:27, on Zulip):

not that I know of

davidtwco (May 02 2019 at 18:27, on Zulip):

I can't think of anything.

Last update: Nov 11 2019 at 22:00UTC