Kubernetes SIG Contributor Experience, 7 Jul 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: [SIG ContribEx] Weekly Contributor Comms Meeting for 20230707

Description

[SIG ContribEx] Weekly Contributor Comms Meeting for 20230707

A

Hello and welcome everyone to the Friday July 7th edition of the contributor comms team meeting I'm your host Carolyn Fields uh as usual reminder that we operate under a code of conduct which essentially says to be respectful of your fellow speakers and attendees and generally be excellent to each other.

A

um We have got our notes ready to go here today, but before we get into that, we like to offer an opportunity at the beginning of the meeting for anyone who's new to the call to say hello and introduce yourselves I'm, not sure. If anyone new is on today, I think we got one maybe um but totally optional. If anyone is new and would like to introduce yourselves, you are welcome to do Sonia.

B

Hey hello, I'm Rohan attendant the last bi-weekly meet on Wednesday and today this is my first meet for uh comms team. I'm excited to be a part of the team.

C

A

Wonderful welcome anyone else.

D

Yeah hi um same for me, I attended the meeting earlier this week, and this is my first quantifix comms meeting so hi.

E

A

Excited both of you joined.

A

um I know uh Rohan is that right is your name yeah.

D

Yeah, yes, you're.

A

Interested in uh tasks that you could take on so I suggested joining our meeting, so you can hear about our six Spotlight blog post, which might be a good opportunity.

B

For you to contribute.

A

To so good idea, we'll make sure that we cover some of that essentially as kind of a review here.

A

Our group um is one of the sub projects of contributor experience and our goal as a group is to make sure that contributors within the community understand what's going on and also to some extent that folks, outside of the community, know the awesome work that contributors are doing so six Spotlight blog posts are a way that we do some of kind of the external communication really internal, do um where we interview the different special interest groups within kubernetes and write a blog post about it, so that people can understand a little bit about what these special interest groups are doing and what kind of help they need.

A

um So we'll go for some of those um Frederico is our blogging lead, so he'll be someone you'll want to know for that.

A

And with that, I think we'll dive into our regular agenda feel free to interrupt it anytime. With questions comments, concerns.

A

And we'll get going here, yeah! Thank you folks for filling in the the notes. Much appreciated so starting with updates and big wins. Chris kick us off.

C

Hello, so I think we mentioned this two weeks ago. uh We discussed it I think more in depth this week at the second trip, X meeting right, like contrabx, would like to deliver a project update and I was like oh yeah, those one minute, things that talk about the whole project and like just for the whole Sig and off. We go kind of thing. So I was like. Oh, let me see what one looks like so I found it uh from last year or last cubecon.

C

uh The Youtube links in there I'm happy to take this on. It could obviously be anyone.

C

um I would need some help. Just proofreading grammar right like it has to it. Doesn't it has to be more bulleted list than a typical one slide kind of thing that I would do right so yeah.

A

A little bit more content, dense, yeah, they'll.

C

Be and it's time Gap, they.

F

A

C

Bound to one minute so, yeah like I, need to reach out to all the other leads of the Saab projects and.

E

C

The actual Sig lead and and I'll get their inputs and synthesize all that happy to do it happy to have help, but you know happy to assist anybody else that might want to do it too.

A

This is a really big project.

C

A

Has landed in our group, but it's also a very small one, because it.

C

Is it's really big and the output is one minute so like yeah.

A

C

Know, like don't spend 10 days working on this kind of thing right like that's, unless it's 10 days of waiting for people to get back to you kind of thing, I.

A

Think I think it would be a good idea if you, it sounds like you're up for leading this this time. If you were to lead this and kind of give us a sense of what this could look like and.

C

Everyone else is kind of along the way yeah.

A

Yeah as much as you can contribute to this and um follow along with this I highly recommend it, because if our group is going to be doing this in the future, that is going to be a really nice opportunity for you all to do.

C

Something for the project like I'm happy to do it this time to kind of like figure it out, but it should not be me next time right.

A

Yeah somebody else.

A

Awesome, and could totally do this work once yeah.

C

And, like I said, if the goal is figure out, the process get, it documented put it in a rule book perfect right, like.

A

C

Like and that's the goal, and then we put it all under the events, thing events group and uh just make it like that becomes just a coordination thing. You know, like here's, the questions you should ask, here's the people, you should ask them to and off you go right like it's, not that easy, but yeah I.

A

Hadn't thought about it as a roll handbook, but that's actually not a bad idea as just like.

C

It needs to go. It comes up twice a year right, like this thing happens twice a year and we're taking it on right, like if that's and.

A

We need one person completed each time exactly.

C

Right, like one person to lead, and maybe a couple helpers or a shadow or something I, don't know.

A

C

A

A big enough, an impact that it needs that level of dedication, though it's small enough that it's not a huge lift.

A

Well, maybe it is we'll see you do kind of have to coalesce the entire project into a minute. So well.

C

It's not the entire project, it is just sign contribex, but you have.

A

To remember how.

C

Many sub projects- yes, it is.

A

I thought it was the whole project- one, oh I guess: do they do each Sig for con.

C

Yeah do each Sig and we've never done contrabacks before so.

A

That's less I was understanding.

C

Right, no, that it is significantly less terrifying than what I was thinking. Where.

E

It was because I thought it was.

C

Yeah, that has to be like a a bunch of like steering folks, not me yeah. That's.

A

Why I was like, why is this? Coming to us, I mean no.

C

This is why I wanted to find the video, and it took me a little bit too so like thank goodness the video goes through like it starts with Sig storage right and then it's just like the next minute. It's another Sig, the next minute. It's another seven minutes long.

A

So seven six.

C

A

Then they do a separate one for all of the other projects in cncf, where each one of the projects it's.

C

A keynote yeah, the projects get a keynote, but then they go through graduated projects just like they do the sigs. It's a whole thing right, like there's a lot of this to get easily confused about and yeah I will confirm today that this is what we're talking about um and yeah. Actually, since I have.

A

um Much less terrified of that now.

C

Yes, right like this is this is like I'll Blaze the trail and we document it and adjust accordingly kind of thing.

A

I think that sounds like a wonderful plan. Yeah I see there are a couple of plus ones here.

C

Oh okay, cool I, didn't know how folks felt about that um much.

A

A

Folks, sharing their their input on this is very much appreciated. Right. Well, I mean that's how we explained it to you.

G

But yeah anyone.

C

G

C

Like I think, what I need to do is figure out all the people we need to contact and then we can break that up and get updates.

A

Fica might have some good stuff to add to this since we're working on the right.

C

Exactly or yeah blog.

A

Posts which hopefully, will actually make progress on because we met about that before this meeting perfect.

C

Awesome that means you've been up for a long time, though,.

A

Yeah, the cats wake me up at around seven or six thirty these days, so cool okay, not that it makes me any more alert so.

C

Fico team here what tool I mean normally I, would go to a Google doc for something like this is that, okay with everybody right and then we once it's kind of been beaten into the right shape, it becomes a GitHub. You know event rulebook thing section, essentially is everybody here: okay with that, is there another thing: you'd rather use like yeah. Let's just go with the Google Doc and move on with life: okay, cool, easy enough; uh I'll start it and like the comms folder, when I find it there, it is uh yeah and I.

C

Don't know how to give access to people in this folder, but we'll figure that out too it'll be an adventure. The whole time.

A

Sounds good to me all right go team if there are any questions or comments or anything about that do, let us know. I'll move on maintainer track comes Chris.

C

So also in that same contribut meeting uh this week, it was pointed out, and almost at the exact same time in the marketing cncf slack. Another friend of mine was poking cncf to send stuff to maintainers and I was like okay cool.

C

We can dual hat this it'll be great, um but Bob never saw it because it got stuck in queue for pending to the leads list which I don't know how that happened, because I guess they've, just onesie 2z allowed my emails through in the past, but now I'm on, like Auto, allow because it's all through Google uh there's no configuration file. I could change to be like hey, make sure Chris Short's emails get to the leads kind of thing so Bob had to just automatically do.

E

C

Or manually do that so that it automatically goes through in the future, uh so those actually just went out like minutes ago um so yeah. It was good that I circled back on that yeah.

E

C

Good that Bob mentioned it, but he probably should have checked the queue to begin with. I, don't know.

D

Yeah, if I say something.

A

C

I'm gonna do something I I will do it.

A

It's black conversation so often how things happen. Yes,.

C

um Yeah I can't tell you how much stuff gets done via slack in this uh project as a whole. It's pretty wild.

A

I think a lot of folks when they're, first starting out with the project you're like okay, how do I officially become part of the project? How do I make contributions where, like it's kind of a check box, I've done the contribution? Everybody knows it doesn't really work like that. I.

C

Don't know none.

A

Of us know what we're doing.

C

Well, some of us kind.

A

Of have, we know what we're doing, but also it's.

C

What we're doing we're supposed it's.

A

Much less less formulaic than one might think: I guess it's a better way to say it much more conversational and natural, uh then one might think at least than I thought when I was first getting started with the project.

F

Chris, are we talking about mail for maintenance only or is it for anyone leads.

C

The leads list- yeah yeah, so.

A

What is the name of the list? It's like.

C

Leads at kubernetes.io exactly.

A

C

So yeah, so it goes, we've significantly changed the aliases uh like I, think over the past few months I feel like, um but that list obviously is like moderated. Not everybody can just send to it, uh because that would be crazy. Could.

E

C

All the vendors contacting all the leads, all the time, that'd be nuts, uh so my emails were stuck in the leads queue and Bob freed them from their prison, so they had been sent um so yeah. That was my thing and slack was Bob. If you didn't see them should I do something else and no Bob went and looked and there they were stuck in the queue so done, um but yeah if you're not on, leads you're not going to see it. Basically, um it was and.

D

Strongly encouraged.

C

That I only send it to Leeds.

A

Yes, and not at the level of sub-project leads, this is like Sig leads right.

C

A

I said, co-chairs and tech leads yeah all those throughout the whole project.

A

Yep, so that's out, um we had discussed the possibility of doing like a tweet. Just to say, like hey, leads, go check, your email, I, don't think it's strictly necessary. Bob seemed a little hesitant about that. So maybe we shouldn't, but also I, know that I would miss that email, foreign, but I would notice it if we put it on.

C

Well, here's the thing you just need to set up a filter for leads to just put that in your inbox. You know: that's all.

A

I do need to do that.

C

Yeah like, if you don't like there are, like many I, think ways to manage email and GitHub notifications and such like Joe beta has a process.

A

One of the hardest things about contribution, yeah.

C

And there's George Castro sent me a link about how to manage like the actual kubernetes stuff and, like the second I implemented a little bit of it, made my life a lot better. I.

A

Would like to see these documents? Yes,.

C

Probably don't have them bookmarked on my work laptop, that's the problem.

E

C

Let's show data they're.

A

Not easy to find you don't have to do it right. The second, but.

C

Good no I'm gonna find it I'll find that I'll find it.

C

Anyways, so that's uh that's done or has been sent that.

A

Is something I need very good? um Okay,.

A

So what do we think on writing doing a buffer post on that? Do we want to or not.

C

A buffer post on for leads we're, definitely not.

A

Yeah, just saying like hey, leads, go look at your email.

C

A

No okay, well just not.

C

Well, I mean we can, but do all the leads even follow that account.

A

They definitely don't it.

C

A

Be just like a if there are any oh like me, which is probably just me honestly, because my sweets are much better about their email than I am at this point.

C

uh uh I mean we can but I, don't think we should right like I feel, like that's a bad look to publicly say: hey leads, go, look at your email.

A

Well, I mean do.

C

Your it would be a job by tweet right, like.

A

It would be more better worded than that. It.

H

B

E

A

For preparations for kubecon and for contributors, that means um preparations for the maintainer track.

C

A

Sure to keep your eye out for details, yeah.

C

C

We could do it, but perception is reality and if it's like, if they need to send out social media I.

B

Don't know how that.

F

Would get taken right like.

C

I, don't know, maybe no one would care who knows.

A

I mean I figured that the purpose of our Twitter account was to communicate with the contributor community. So I think it makes sense as a use case for it, but sure.

C

I'm not arguing that I'm arguing the like effectiveness of such a thing. I guess basically.

A

Fairness, so we'll move on from that maintenance track. Comms is done. Thank you very much Chris for spearheading that and getting it done. Much appreciated. As usual um next item I already mentioned, FICA and I met this morning to unblock those Spotlight blog for contribex. That is mostly my fault, because I have been very, very busy lately, um so we looked over it. uh I actually didn't need much editing. We had mentioned that it was kind of written from the perspective.

A

Just interviewing me, but I think it'll benefit a lot from having the perspectives of the other co-chairs and tech leads in it, and the Way It Was Written, honestly, it I think it'll work. Just fine, so I think we're good to go there. If I get anything else, you want to add.

I

Thank you for your time today, yeah.

A

My apologies that I have not given you more of it earlier is entirely my bad.

A

All right noted on that um and Chris to share resources on managing contributor notifications and email and GitHub and stuff yeah.

C

I'd love to see those, and you know what it's probably changed since then and I might be the only person with like a live good set of filters. That'd be scary,.

A

um And so we have one new item from sujay. uh He caught a YouTube issue, which is a zapier thing. Oh CJ, would you like to go over it.

G

Yeah I just saw that the video title is still marketing meeting I.

A

Think we talked about that. Yes,.

C

We talked about that and where? Where did we have to change it? The calendar.

A

C

It's in the notes like it's in here somewhere, search for marketing, meeting and I bet. We get a hit.

F

C

A

But it's not the.

A

I thought that we fixed that actually because I worked with Bob I had him like walk me around Zoom, stuff and.

B

A

I thought we changed the name of the meeting in Zoom because there's like two places where it is in Zoom there's like the invite that goes out and there's like the meeting itself.

E

A

I think the meeting itself has marketing meeting somewhere in like the definition of it, and so we had to change that. I thought we did but yeah.

C

A

Should go check that out because Bob already taught me how to do that.

I

Yeah, so if you're looking for a temporary solution, then I can change uh the title of the videos as of now but yeah for the permanent solution. You have to change it from the calendars yeah.

C

I mean we have the ability to morph ourselves choose happier, but let's fix it for good I mean that's kind of my thing and we could maybe or I could.

I

Make retroactively.

C

Go back and fix them, but that's a lot.

C

But yeah it needs to like we shouldn't make a patch for the problem. We should definitely fix it at the source.

A

Yeah yeah I totally thought that we got that, but I should check on that. um But.

B

C

A

Even if we got that, though, it'll only fix it for future meetings right.

C

A

Past meetings after.

C

That way, myself or a YouTube admin has to go back and fix them and.

D

A

C

That hard, but.

A

Jay said that he could change it. Are you getting involved with YouTube Administration stuff.

A

F

Was that yeah I.

C

F

It was pritish, oh, that was pretty.

A

Sorry I wasn't.

F

Paying attention to my.

A

F

Also in the previous as I see in the previous meetings, they they showed this contributor comms.

C

uh Oh so maybe it was fixed and got put back.

I

Weird sequence:.

F

Yeah I do see, contributor comes.

A

Their contributor comms ones, but then is the most recent one contributor comms or is it marketing, which one is this one, this one's June 30th? So that would be huh weekly.

C

Marketing, weird, okay,.

F

Two weeks ago it was contributor comes weekly meeting. If you see.

C

I wonder if Zoom did a restore on it.

E

C

Know, like you never know, it's all configuration and zoom somewhere right, like yeah. Each.

A

I

Those elements hasn't been done, like someone has manually, changed it to contributor songs, because till now we are getting recordings as weekly marketing thing, so it conquerors.

A

I

Thought I went.

A

In and fixed that, but I guess not: okay,.

C

All right that sucks.

A

I also thought it might be that, because the the elements in Zoom each have like a end date on them and like it, the end date wouldn't go as far out as we wanted it to so I thought. Maybe it just ended the one that we fixed and like.

C

A

I don't know anyway, I'll, look into zoom and fix that yeah. Thank you very much for bringing it to our attention. I.

C

Apparently also can.

A

Look into the van oh: can you nice.

C

Let me make sure these credentials are good, but yeah I, don't know why I have this.

A

You do a lot of stuff with the automation so probably related to that. Somehow.

C

Yeah contributor experience, okay, cool I'll, look for it, let's meet and we can continue. The meeting has one I can hunt this down.

A

Sounds good: we are only 32 minutes into the meeting and we're already going to the board. That's amazing! It's pretty great.

A

I'm so slow, but we have fun, though, all right so we're going to the board motherboard the board, all right. First item Federico is on and on his iPhone. um The two things in writing for review are yours, Frederico, uh add readme for storytelling resources. We looked over this last time.

A

uh You were just ready for review, updated with suggestions.

H

E

Okay, there you go yes, I.

H

Was gonna go over it.

A

In case you couldn't unmute, but yes.

H

No, no, no worries uh Fleck your wireless, but uh it should go through so um I have Chris actually um commented on that. Pull requests and I've um made the changes and pushed them today in the morning. So that should be that should be covered. So I reflected everything that you mentioned. So uh unless there's a spelling mistake there or something like that, I I think that we can proceed with it.

H

Obviously, there's more to add, because it's very basic what we have there, but maybe we can have this initial initial um Skeleton version and uh add more stuff as we go as additional commits.

A

I think it's wonderful I'm, very excited about this yeah.

C

A

No one knows what those resources are.

H

So that was one and the other was.

A

Cli Spotlight I, don't know if that one's.

H

A

H

So last week, I I I wasn't able to to attend and I I. Remember that I was supposed to have linked this into the select discussion for hack, MB review first and then the pr I ended up doing that today, as well so I've shared the I can view Link in our uh slack channel. One thing armpit that I I would um ask you, as I I asked there, is that my following the link, I I, have access to the content and I can comment on it.

H

Etc, but um I don't seem to be able to actually access the markdown version. I think this is a ACL kind of thing you need to provide me. Add me as something there, um because it's easier um to actually pick up the markdown and um and add it to the to the pr I already created the a branch already created, the the the the header for the pr uh with a target of next week, Thursday or Friday I.

H

Don't expect us to have a lot of comments in the next three days, um so I think we can more or less agree that we will open the pr on Monday or something like that.

H

um So if, if you can check that out and and just add my email there as a and edit is there, a reviewer um I will just copy the markdown as is and make a commit with you as an author, and we with that, we we should be able to to push this forward.

J

Yes, actually uh I actually saw the messages like and I tried to add you, but I didn't find the option on it can be. uh If that is not possible after the changes I can provide you the.

E

Hack to the files, if.

J

I can add you as an editor. I will do it by today.

H

Okay, excellent.

J

H

H

um For my size, actually I can also provide another two updates. Maybe it's uh it's because I don't know how much more time I can actually stay. um I have the kids at the pool, so some of one of them is not shouting. I I need to run.

C

I love your dedication by the way yeah.

H

No, this is two two weeks missing is too much, uh so, let's let me see, um there's one with them. uh Contributor Summits um thing uh I've already had a conversation with um Noah this week uh and uh we are good to go for the written um interview already uh ask the initial question so we're on the waiting for uh feedback stage um I. One thing that we've mentioned before was was um within ourselves here in this group.

H

Was that maybe in this one possible approach would be to have a written the interview with the blog, an article Etc and then following up that idea around the uh Twitter spaces kind of thing, assuming that it survives the next couple of weeks. Maybe we could um pick up that interview and then maybe uh open up something like that. So I've mentioned that to Noah as well um and um depending on his feedback. Maybe we can entertain um this as a possible approach.

H

um That's it for the contributor. Sorry, the other one is the Sig architecture, one uh which is uh almost the same as last week when I checked a little more more content in one of the on the fourth um sub project.

H

So we are getting there um if in a week or so, um we don't get any feedback from the others which don't have anything I, guess that we can just simply start a series with the ones that we have and then catch up later on with the second part, if the others give a end up, providing some content so and and I think this is mostly it for my son.

A

Wonderful, thank you. um So I moved the contributor Summit Spotlight into in progress. Yep sounds good.

C

Update on Zoom, the access I have is to the top level. uh Contribex account. Sub-Projects might live elsewhere, apparently, so this is now.

A

Yeah, there's two back in Europe all right: do we need the top level for this I? Guess it's a little confusing, what's on which it's.

C

Quite confusing yes,.

A

E

J

C

You into that confusion, I feel like too so. Yeah.

A

Yeah see them more confusing than I expected in configuration anyway, um yeah cool. Thank you. So much for joining British got a few folks dropping off um all right. Thank you very much Frederico for the updates. I'm really excited about the readme, the storytelling resources, one other thing that we had discussed for that was renaming the storytelling resources, like section like folder to blogging resources or something we need to work on that as well.

A

Do we have a thing on the board for that I? Don't.

H

Think we do sorry yeah uh on that I actually made that change as Chris suggested. So the actual document already has that on the markdown I can easily do a git move on this folder as part of this uh okay of this and change the storytelling to blogging. If you think it's okay or we can just keep this one on under readme and then create another one to move things around, both work.

A

Sounds good to me, so any preference blogging.

H

Resources yeah, but should I black movies sounds great, should I do that change inside this PR so add the commit now moving things around and add, Bell to the readme and the renaming of the of the folders go.

B

H

B

H

I'll I'll I'll I'll I'll take a look later today.

C

I mean it's a total Shakedown of the the story and telling stuff so.

H

Yeah, true true more than just read me yeah, absolutely okay, so I'll I'll, I'll upload it later.

A

On your issue, for that.

C

Yeah as a reminder, Chasm will ping you yeah. Thank you Federico very much.

H

Yeah, thank you so much. Thank you for your comments on this and I think this is actually useful because we have actually good content. That is uh not updated, because people didn't actually know it exists outside of uh some some some some files in a direction here.

A

Yeah, it's confusing for everyone.

A

We originally called it storytelling resources to share the context again, because when we originally when this group was originally created, everyone who contributes to it was called was in the role of Storyteller, because what you do is you do.

D

E

A

Blog posts and tell stories about what people are doing within the contributor Community, but nobody knows what that means. So we're just going to get rid of it.

A

Just made things complicated.

A

Wonderful, thank you. Avinash checking that out reviews very much appreciated. We should do more to increase you.

H

Did you did mention that we have new people here and that yes, they might be interested, so maybe we have a list of six spotlights articles in the to do right. So maybe that's a good. uh This is a good point to absolutely.

A

To show it yeah, it looks like we've only got one left in to do should probably refresh that. Okay.

A

um So, if you're looking for a task to take on uh here in the to do column of this board, which I'll grab the link to it and throw it in the chat, um we've got Sig Spotlight on Sig API Machinery, um some sigs, like you, might not have understood what the name meant before you do.

A

The spotlight, um API Machinery does some really cool stuff, um there's a whole bunch of other special interest groups that we haven't done these spotlights for so this is just one that we had in the to-do list, I think, but we could put in several more if folks need more.

A

And let us know if there's one you're particularly interested in we'll, let you know if we've done it anything else, you want to add Frederica sound like a good process and let Frederico know I just like Ping in slack in the countrybeck's comms Channel. Just tell us: hey I, want to take on the Sig API, Machinery, Spotlight or I want to take on a spotlight but I'm, not sure which one I'm interested in XYZ yeah.

H

Absolutely yeah and uh you don't need to know anything about the process or what you need to do, because we are right. Fortunately, we we have it documented and on top of that.

H

It just needs um the interest in doing doing it, um and, and that's more than enough in the time and.

A

Time yeah it takes a while, as uh we have seen, I.

A

Right, so let us know if you have any questions, comments, concerns about that um and let us know in control xcoms about what you would like to take on. If you want to take on one of those tasks, all right, so move on to some other things in the board. Here. One thing we talked about in the Sig contribex meeting this week was slackbot. Thank you very much sujay for trying to figure out what is going on with the slackbot I have been very confused about it.

A

We got a few more hints about where to look during the meeting um anything you want to update on there CJ.

G

Yes, sir, just like Bob mentioned in that meeting, I started with adding those Blackboard in challenge so for now, I'll just added it into big spawns and Country mix. You know to test it that it's working, fine but I need help in trying that, because I don't have access to that and as per the.

G

Select configuration, it seems, like only one person got the authorization, and we just think this is Josh.

A

So what was it that you don't have access to that? You need help with.

G

uh Sorry take your time.

A

G

Mean I uh I can't post um any message using the announcement board.

D

G

You know the screenshot I posted there, you can see, only one person got the access or somehow I need to figure out authorization model.

A

E

A

C

Is this? Is this an issue? Can you convert this into an issue.

A

uh Yeah we can convert it into an issue. Yeah.

C

Or yeah, it's got it like yeah I,.

A

Don't know if we already have an issue, but.

C

We probably do, and it might just be like linking the two things together at this point. Let me go look.

E

A

Which repository does this go in, though,.

C

uh The immunity.

A

C

A

That hits a lot of it. One of.

C

A

With the slackbot stuff is that it's.

C

It's actually in Kate sigan for a even though it's part of contribex and.

E

Yes, Community is.

C

The right place, because that's where our group lives.

G

Yeah in one piece I saw that you know to post a comment.

G

um Not exactly I saw something about country, Banks,.

G

A

All right there's the link to the newly created issue. um What.

C

C

Are you tagging it saying stuff now I'll? Do that real, quick.

A

Not at the moment, I was gonna update.

C

Our groupless tag thingy every time.

F

The issue should be uh in the slack infra project, but I don't see an issue over there as well.

C

No, like the issue lives with us under control X. The work actually gets like. It is our thing: it just lives in Sig, Kate's, infra, there's like a lot of.

B

Stuff that actually lives.

C

In Kate's infra, it's not just Kate's in for a necessarily like the CI testing and everything else. It is like web servers or redirects and DNS and all kinds of stuff lives in infra. So that's why it's there.

A

So our group is doing the work, but the work that needs to be done will be done within Sig Cades infra.

E

Resources, probably so.

D

C

Yeah, it's it's an interesting like because here's the thing we have to run some kind of software to do the thing. That's.

G

What the code belongs to contradicts right right.

C

Yeah so the the place it lives. You know it lives on a kubernetes cluster somewhere managed by control the Sig Kate's infra. It's still like our project, our responsibility, basically.

A

Yeah and there's also the slack sub project within contribex, which.

C

A

Some hold on this as well yeah.

C

Yeah, like they want to use.

A

It there's several groups moderating.

C

You know, like everybody kind of, wants, to use it, but, like the select team moderates, we actually like our comms and part of contravex.

A

So we're the ones that are supposed to use it and.

C

E

A

And fix it because.

E

We care about it what's wrong.

A

With it, but Kate's infra is the one that's supposed to like run. It.

F

Well, so so there is a project called slack influence, said kubernetes, six, that's where the code lives for the slack board, no.

C

It lives in Sig, Kate's, infra, okay,.

A

Should it be in slack infra.

C

I mean there's an argument for that, but does slack infra have all the people and access and so forth that Kate zenfra does right, like? Is this code running somewhere on a thing or stuff that, like we've just done in Slack.

A

We have the following tools: event log report, message, moderator moderator words, welcomer, post message;.

C

Oh, it's in palaces in here.

A

To post message in multiple channels.

C

It's like well, what is slack post message. That's the same thing as this thing: yeah.

A

I noticed when I was working on this, that there are two Bots.

C

Okay, well, that's a problem.

A

Are similarly named I, don't know.

G

A

Was months ago, I.

G

Think we are getting about slack post message.

D

C

Other, to be honest with you right, like intentionally.

A

Or unintentionally,.

C

You can see our configuration for that okay, so they have a cluster for themselves running all this stuff too. So, like okay, new problem old slack button, said Kate's unfra, or this slack post message thing: one of them has to go away right, like think of it like that, so, like whichever we choose is the thing it's gonna be the thing for the whole project.

C

So if we choose this make sure the psych team knows hey we're deprecating slack, but ain't gonna use this instead is that cool because they might not have designed it for the same purposes? I, don't know right exactly.

A

C

Where's, the uh slack interest yeah, okay right here- got it yeah. This is wild. um I'm super curious, It's.

A

So confusing we also.

C

This is the post message thing right, like okay, what the hell all right. Are they the same thing? Are they literally the same thing and they've just documented it in two places.

D

C

No there's actual code living here. So that's no like oh my God. This is not.

A

Is there actual code in the other place, I, don't know if there is I'm.

C

Gonna go look, it was nuts.

A

I mean maybe this is part of sick Kate's, infra.

C

I mean that that is I, don't know where, what's the directory say.

A

Remember when you reached out to me about like what we know about this CJ.

C

Oh, my God, it is under, it is under there. um So.

A

There are two of.

C

Them, okay, so there's it lives in two places, kind of thing. So there's, but it's the same actual slack post message, deployment, secrets and service, the actual kubernetes stuff getting deployed to the cluster lives in slack infra. But that's also under.

E

C

Is under big kids infra, so there.

A

Is some overlap.

C

Here but it is the same thing.

A

Hey Ben: this is well documented somewhere yeah.

C

This is well documented. We need to document this like really bad I, don't care if it's under the slack admin stuff right but like we need to understand how this tool works. The stuff that lives in infra appears to be the service file, the deployment file for Kate's for an actual cluster, the things that live in the other folder or other directory that we've or web page. Whatever we're looking at right now, that's important too, and that's the stuff that could be broken. So yeah documented well.

C

Like a Looney Tunes cartoon, everybody yeah.

A

I believe in you, CJ.

C

All right so and here's the thing I had this bookmark I have this bookmarked I have the secrets and everything else bookmark here the link that I dropped in there that's booked that that's actually bookmarked. How did I not find this? This is crazy.

I

C

Like I even have the slack post message thing and because it's under contributor comes that's why there is confusion.

A

What other links should I, add I'm gonna, add a comment.

C

A

Like these links have something to do with this.

C

So yeah the slack post message thing is here and then there's the deployment files and Kate's yaml's there so yeah. The first link is the probably the stuff we care about. The second link is getting it actually deployed, which.

E

C

Been touched in two years, so that's kind of crazy, but.

A

Josh fixed something to do with it like last year,.

C

A

C

Last commit was from.

A

Maybe it was two years ago.

C

It was two years ago from our no.

C

G

I think he fixed it around September last year.

A

Josh did yeah yeah? What did he fix.

C

Ed, the doctor.

F

The question should be: where did he fix Ed yeah.

A

E

C

Right, modal types: what is modal types? Okay, that's interesting! All right! This is just nuts configuration the deployment that yaml's linked in here all right. So there you have it this page, which lives in slack infra points to stuff in Kate's infra, so yeah I can see why we're confused. Now, it's.

A

Just in both places it's in.

C

Both it's across, but it's two different things right, like.

A

Different things yeah that work together to form this thing thing.

C

And slack infra is the code that does the job of the bot in slack the thing in Kate and fra is the deployment file, the external Secrets all that stuff to put it running somewhere so that it's accessible to our folks in slack yeah, Juan, so much fun, Dear God.

D

A

We just add it to all of the channels.

C

We should just add it to all the channels to be honest with you, but then can anybody post anything anywhere is maybe a question. Can we combine them in one place I doubt it I seriously. Doubt it uh here's? Why? Because if we put all the code for the thing in the Sig, Kate's infra directory they're going to be like what.

B

Is all this this.

D

C

Not the thing to deploy the thing: this is the whole thing, so it's like the Kate's or the slack infra team makes updates and it just goes out the door. Basically, that's what it looks.

A

Like sometimes things that make sense to the engineers that run and build the thing, don't make as much sense to the users of the thing.

A

Lessons for life in software development.

A

All right so now that we've confused ourselves sufficiently with that, we have only one minute left. Oh.

C

And by the way, there's also cluster code for the slack post message thing and slack info that hasn't been touched in two to three years.

A

Well, add any more links to the issue and any details that you want to add to that issue.

C

A

I'm not going to try to go through the rest of this I think.

C

E

This is another recording. We can go back to and learn things from.

C

Like every other week, we have these now.

A

A

All right thanks so much for joining today, everyone, um you know where to find us on slack. If you need anything, if you just want to shout your confusion into the void, we are here for that.

E

I'm gonna stop by recording. He is okay.

A

One last thing before I: stop the recording again.

C

Somebody asked me for links to all the stuff for contributor Summit. Comms I just want to make sure you're good with that. If.

D

You're not that's right, yeah.

A

Ooh the thing we should have also talked about contributor Summit, but we didn't so.

C

Next week,.

A

It'll actually start up next week too, I think probably here at least very soon, so we'll get that sorted out. Thank you. Everyone for joining today, I'm going to stop the recording now goodbye YouTube.