Stream: t-compiler/wg-meta

Topic: upcoming meeting


nikomatsakis (Feb 26 2019 at 18:42, on Zulip):

That reminds me, I wanted to brainstorm a bit about what to do in the next meeting. One thought I had was to try and come up with some specific "procedures" that we could document and work on those.

Santiago Pastorino (Feb 26 2019 at 18:44, on Zulip):

seems like a good idea

Santiago Pastorino (Feb 26 2019 at 18:46, on Zulip):

as I was mentioning in the other thread, I guess clarifying better expectations for members and leads would be great to lay out a bit better too

Santiago Pastorino (Feb 26 2019 at 18:47, on Zulip):

maybe this is only reasonable to me :P, unsure to be honest, but I've learned that a lot of things often don't work great because of the difference of what one think should do and in what way and what the rest expect you should do and how :)

nikomatsakis (Feb 26 2019 at 18:48, on Zulip):

yes, definitely

davidtwco (Feb 26 2019 at 18:48, on Zulip):

That somewhat ties in with the good neighbor guidelines that I had linked in the big ideas list (I feel like I'm referencing that video a lot..).

Santiago Pastorino (Feb 26 2019 at 18:48, on Zulip):

another thing I'm not sure is how many people from rustc team is willing to take a WG lead role and how much availability they have

nikomatsakis (Feb 26 2019 at 18:48, on Zulip):

as a meta point I feel like our goal right now should still be trying to find concrete tasks and doing them :)

nikomatsakis (Feb 26 2019 at 18:50, on Zulip):

ah, another semi-urgent item .. we should probably create some place to record the set of WGs and to document when they last had a "check-in".

In my ideal world, we'd be "broadcasting" results from these check-ins, that process doesn't quite feel "smooth" yet, but I think that's ok for now.

nikomatsakis (Feb 26 2019 at 18:50, on Zulip):

(maybe that's the "big table"?)

Cem Karan (Feb 27 2019 at 15:03, on Zulip):

ah, another semi-urgent item .. we should probably create some place to record the set of WGs and to document when they last had a "check-in".

In my ideal world, we'd be "broadcasting" results from these check-ins, that process doesn't quite feel "smooth" yet, but I think that's ok for now.

If each working group is supposed to have its own place in the repository, could we use a script to see when they updated their meeting minutes last?

Last update: Nov 11 2019 at 22:05UTC