Node.js Inclusivity Working Group, 21 Apr 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Inclusivity WG Meeting - 2016-Apr-21

Description

Meeting agenda is at https://github.com/nodejs/inclusivity/issues/124

A

Hi everyone: this is the April 21st 2016 meeting of the inclusivity working group, I'll start off with introductions. My name is Brian Hughes I work for Microsoft doing know things and on github, my user name is Nev rias bo. You want to go next. uh Yeah.

B

I'm Bo Gunderson Oh Gunderson everywhere on github and Twitter and whatnot I work for personal genomes, org and I'm taking notes today, I.

A

C

Gonzalez I work for a clipper magazine and I'm Scott cansados on github and rich.

D

I'm rich trot on trot TR, 0 TT on github, Twitter and other things and I want to express gratitude to vote for taking notes.

A

Guess bo is our awesome. Note taker always does a great job happy to do it. Alright, so first we'll take a look: oh and uh yeah I'm gonna be moderating. Guess I should mention that as well. So what's up with a working group operations, this is gonna be a short meeting is pretty much going to be. The only thing we talked about today first is onboarding of new members. We have some more news, members that have joined a helium, Duke and Charlotte Spencer.

A

Neither of them could join due to some scheduling issues today, but hopefully we'll see them next week. We're really excited to have both of them going through the onboarding process. We're just about done. I think the only thing we have left for both of them, which we actually still have it for you as well Scott, is getting everyone added to the mailing list, but everything is done there. Anyone have any thoughts, comments on onboarding process in general, anything with I guess three of you.

C

Just good that we have checklists now ya made the process a lot smoother. Yes,.

A

Indeed, if I'm really glad we have those two and yeah thanks for your work on that yep all right next up, this is probably the big one is the slack in vidor Scott. Would you like to give us a rundown of kind of where we're at how that's working and all of that.

C

Sure so it's it's up and running and we do have a link from the contributing guidelines. So you can see. Let me just make sure that's where it is should be named. No! Yes! So if you, if you look at the, if anyone wants to join the slack team, you can go to the contributing md file on github and there's a discussion section which links to the slack inviter and you can just go there.

C

It will pull your email address from github, so uses a loss to grab your information from github and then it will just Sunday invitation.

C

So it works it handles as far as I know, all the edge cases and it's and it's live so I think we've had some people use it. We don't have logs on crews, getting invited so I'm not entirely sure.

A

Yeah we haven't, we seen you and else actually joined the slack. They don't recall.

A

Let's see, does it look like it yet we have been advertising at lunch. So I guess it's not surprising and.

C

Maybe we can tweet about it or yeah or something I. Don't know, I mean it I assume that some people who were interested would have been following the issues and would have seen that we have done this, but perhaps not maybe.

A

We could put it in the readme, so it shows up on the main repo yeah.

C

We could do that too. Yeah I was actually looking at that when I sent a pull request, update they're contributing guidelines, but it didn't seem to be an existing place and I didn't have time when I was doing that to try to add more sections to the readme mm-hmm.

A

I'm looking at the reboot right now, maybe we could add it up, but because they had like that little blurb of if your instant running, please submit your application here. Maybe just that like another sentence after that, I can add that to ya here, I'll be great. There is also a bug that it or an issue that is open about a bug, I believe William khaki submitted. That can you talk about that in?

A

Let me pull that up, see that's issue. 123.

C

um Oh, you know what.

C

This might be an issue that resolved already oh cool. Let's see one two three, so I can write it doesn't work yeah. This bug is fixed doo, doo doo. Let me just close that or maybe can you just.

A

C

A

Mr. saying this should be sticks, can you try it again, you know, verify that's closed and let William close it by.

D

A

Cool thanks awesome, so I'll go ahead and mention this in the tsc meeting today as well. I think they'll be really excited to hear that as well.

C

Yeah, so what happened was when I was working on that issue. I filed an issue in the slack inviter repo and then that pull request got merged and deployed, and so the issue is fixed, but then we never came back to the inclusivity repo to close the issue.

C

But yes, we can I just posted a comment on that issue, so we're good now: okay,.

A

Awesome all right and the other one. This was a small one. I did real, quick, so I stumbled across it. This is issue number 126 clean up the inclusivity, github team, just I noticed while doing a little bit of administration. I think when I added Julian yeah, I know there's a lot of other people is kind of. This was back from the very early days of the group.

A

Whenever we reformed raptor know adventure, we just kind of added a whole bunch of people before there's, like any sort of you know, policies or whatever around like who should have what permissions and so I kind of, went through and I basically removed everyone who wasn't a member and I filed this issue mostly to track, because I'm sure some people I didn't want to just remove people and they'd have no idea why just trying to get some transparency there. I was thinking kind of leave this open for like a week or so say.

A

But what do you all think.

C

um I, don't think it needs to stay open. The fact that you put it there and anyone that was paying attention would have gotten to notice it's fine. Once you close it, people can still comment on their if they think that it wasn't a mistake, but I mean we have our members list that we're working from so okay.

A

All right, yeah I'll go ahead and close that then tells good to meet you. Okay,.

A

All right close that just now looking back the list on the agenda, that's actually everything we have on the agenda for today I next time, so we've had only so much participation in meetings. I think scheduling has been a big part of it that we have a shared calendar somewhere. I think it's a it's. A shared google calendar and I. Don't use gmail, so I, don't see that myself but I know is this something we want to continue with. Is there may be some other way of giving us some people's calendars? I?

A

Think that's the big barrier to entry right now. I would love a shared calendar. Okay, all right, I think Kat was managing that I'll chat with her, and so you can get something worked out.

A

I will talk about that one, the slack will get that worked out there. Well is there anything else even wants to talk about here.

A

Thanks, that's it and a rich bow or anything else.

C

I'm good, you know nothing, nothing that enough nothing to talk about.

A

Alright, with that I'll go and call it a shortest meeting, you had thanks for joining in everyone.