Stream: t-compiler/wg-meta

Topic: procedure to add a working group


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

Hey @WG-compiler-meta, I created a PR that tries to describe the "procedure" for creating a working group:

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

I envision this directory eventually containing docs for other sorts of procedures. Also, I'm sure this text is strange or incomplete, so please feel free to add suggestions. I just thought it'd be nice to have some directions I can point people at as I start to bug them to setup the initial set of working groups.

Maybe this document (or a similar one) should be created to kind of cover the "advice for working group leads" that @Santiago Pastorino was mentioning?

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

@nikomatsakis I think is key to have the info there

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

reading your PR :)

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

I guess, when you describe Step 2. Figure out key information which you talk about leads

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

it may be good to give some advice

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

@nikomatsakis and actually about that point 2

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

there are concrete suggestions like do meetings, summarize, etc

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

but I guess higher level things like, your goals are to encourage people, provide support, etc, etc

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

I feel like that should be pulled to its own document somehow

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

yep

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

we should maybe give even fewer details here

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

and just link to the other doc

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

yeah, I think more general ideas are better or even everything in another place is ok

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

to be honest I'm not thinking that much on where

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

I'm thinking a bit more on what exactly is key to say

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

I guess communicating expectatives is also very important

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

if there's a task that must be done by the end of month and you hand that to a person that is volunteering I guess is key to both to know and agree that it can be accomplished

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

I guess there are a lot of things like that, that could fail if not explained properly

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

I guess communicating expectatives is also very important

yes, makes sense

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

I definitely think we need a what is a working group section

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

have added some of these thoughts to the PR

Cem Karan (Feb 27 2019 at 14:48, on Zulip):

How about adding a checklist as well? This is less for people who have never formed a working group, and more for people that are used to forming/leading one as a quick 'pre-flight' check, just to make sure that they haven't skipped any steps.

nikomatsakis (Feb 27 2019 at 19:52, on Zulip):

I did have a checklist? I guess it's more in 'paragraph' form

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

Hey y'all, I incorporated edits meant to address all the suggestions on PR https://github.com/rust-lang/compiler-team/pull/12. I'm going to go ahead and land it, but please feel free to make PRs amending it etc.

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

I mostly want something in place to point people at :)

Cem Karan (Feb 27 2019 at 21:06, on Zulip):

I did have a checklist? I guess it's more in 'paragraph' form

I was thinking more in terms of an actual bullet list, kind of like the Rust API Guidelines Checklist.

Last update: Nov 18 2019 at 01:45UTC