Kubernetes SIG Contributor Experience, 30 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: [SIG Contributor Experience] Weekly Marketing Meeting for 20201030

Description

[SIG ContribEx] Weekly Marketing Meeting for 20201030

A

Core.Com, hey friends, welcome back to another uh kubernetes community uh communication wow, I'm just gonna put all the c's out there. uh Sig contributor experience commute uh com team, the upstream marketing team. Clearly it's a rough friday hi good morning or good evening um and yeah it's just the two of us ph. So, let's just you know, do a little stand up and talk through anything. That's on our minds. Oh yeah today is not the 9th. It is the 30th.

A

huh What's going on on your end,.

B

Yeah right from apec point, we do have few more uh submissions for meet our contributor blog, so that looks good. uh I hope, probably you know. In a couple of weeks we should be able to at least put out one blog and.

C

We can actually.

B

Yeah, that's that's good, but I guess that's the only thing we are planning on doing something for next kubecon. uh That's the eu one, probably some some apex specific stuff, but no clarity, yet nothing finalized.

A

Nice yeah, you.

B

Can come up yeah? I would be open to ideas, for that I mean.

A

This is awesome, yeah, that's actually a great segue, so the the one big win I wanted to share is like um uh we are all set with slides. So myself, caslin and rajula put together a slide deck of like what we've been doing, and I want to share that with others. So you um I think you could clone this and reuse it for apac and and present kind of the community marketing. You don't have to cover the exact same topic since we all kind of did it from our own perspectives.

A

But um if that's of interest like yeah I'd love for you to reuse and kind of keep, the story going, um slides are here feel free to copy and reuse.

A

But we do all right, I'm linking them in the meeting notes, but yeah they're. They turned out really pretty um rajula found this great uh website that gives creative commons like free free for non-financial use, um iconography and images, and we use those as like a way of kind of having a through line through the project and then caslin did what she does so well, which she drew her own pictures.

A

Just unbelievably cool.

B

That's brilliant.

A

Yeah, I'm such a talent uh so yeah, um I think the yeah. We cover three main things like how we design the communication structure, how we help people through storytelling and how we're building bots to help navigate and get the same message across multiple channels, so yeah pretty universal stuff. It should be fun, um feel free to use it. And let me know if I can be any help.

B

Yeah, that's great I'll, probably bring this up in our next meeting.

A

Perfect great okay, so you know in progress is pretty much nil. um I there was, we got one thing merged into the community, repo related to the technical lead role that I helped shepherd through and did some copy editing.

B

A

That was nice. um You know I'm thinking kind of in a pre and post kubecon mindset, I think post kubecon into the end of the year.

A

We should think about getting some more blog posts going on the dev site on the contributor site, um but for right now, like I'm thinking about something like the meet our contributors, we have like a long-standing open issue for it, but I wonder if there's a good place for us to document like these are core stories, we're always after um and kind of, saying like like in our documentation like here's, what it is, here's how to ask questions for it, and then people open issues whenever they take one and like move forward with it.

A

B

A

The workflow a little differently um all right, I mean.

B

Open issues kind of a thing, or it's just a theme that people would want to pick up on.

A

Yeah, I'm thinking so we've got kind of a mix right now right. We've got these long-standing umbrella uh issues. That say like write a story about every cig. Like you know, unless we get an army of volunteers, like that's gonna, take a couple years, uh there's so many things I don't think for the project it's well.

A

I guess it's not unusual to have issues open for a while, but um I was just trying to think if there was like a nicer, more marketing friendly way to do this um yeah, you know incomplete thought, but I'm just keep trying to come back to this theme. Like I feel like we have.

A

um We have these themes that we're trying to encourage people to use as a device, and it's still pretty confusing to get in there like if a new person showed up today and said they want to write like what do I tell them like. I think the story of what we tell them is a little to go to this issue open this issue go over here pop over there, like I kind of want, like a a single artifact, like probably a markdown page.

A

That says, like here's, what here's your options for articles to cover and here's, how we do it and then link to the documentation caslin put together.

B

Yeah yeah. Let me first yeah, okay cool! You should probably have something like that: fine, but.

C

B

Also, sorry, oh no.

A

No keep going keep going, yeah.

B

What are you thinking? Yeah I mean I was just thinking that also makes that I mean again. It goes down to the that that bottom line, that you know what all we want to cover right, I mean we need to write that down by keeping it open as providing stories keeping it. That way, I mean it's just confusing stuff right I mean, even if it's vague right and there has to be some pointers of some leading direction. I mean, as you said right, there are thousands of stakes like.

B

If we start uh you know we just open it up that you know we just want to cover safe stories. That would never be enough right, but if we can just jot that down probably you know, these are the six we are targeting for now, rather than just opening it up for everything, so that basically gives a more targeted approach.

A

Yeah yeah yeah, like um you, know, a fancy term, for it would be like operationalizing it like. We we've done this a few times and we can take the best steps of it and simplify it for the next person. You know still leave a lot of room for creativity, but you know make it not so much a hunt and peck through the world yeah.

B

A

Okay yeah, I like that, I aspire to you know yeah, maybe that's the thing to document here is like there there's an open issue of you know, um there's something brewing.

A

Yeah, uh it's basically migrate from you know from.

A

Umbrella issues around blog posts to a methodology, a single artifact.

A

That describes the goal and tools to get there.

A

Yeah yeah kind of go from yeah migrate from these umbrella issues to a single artifact that walks people through the storytelling um strategy, and I feel, like caslin's, already documented a ton of that, so it would be updating to existing issues, and you know, oddly enough us us marketing, that, like here's, your definitive guide uh and like here are the sigs we're targeting who who's taking, which one, like kind of yeah being a little snappier about it.

A

Yeah cool all right I'll, complete that issue. It's very roughly draft I'll. Keep that open cool our bots and bots in progress got. um You know the the ones that we're using are going well and uh karthik is working on his edits to the extension to the the tweet one. um So nothing, nothing crazy to report.

A

A

A calendar walk anything happening on the calendar that we should.

A

C

A

What day is it? Oh, you gotta look at next week: oh yeah! Well, there's a releasing meeting. That's pretty normal.

A

Yeah seems like a ton going on, but pretty normal week, nothing pops out as a we better cover it.

B

Looks pretty standard.

A

Yep, there are no drafts out there and I walk through issues and I there's nothing new on the the website or no new ones on community and no new ones on the contributor site that are tagged for us. There are, of course, things in progress, but uh they're these long-standing series again, as opposed to like discrete solvable issues and that's a little bit of a challenge, we're we're working through but totally doable anything in the github world. That is on your mind,.

B

Nope all looks good.

A

Cool, well that covers it. For me, um yeah, I think it's we've. We've made some really good progress and I think just thinking through what we want to tidy up before kubecon, so that when people show up when we get the word out and people show up that they know what they're showing up to that would be the only thing on my mind, maybe I'll bring that up next week. Maybe we can do like a bit of a push of uh walking through docks and cleaning them up.

A

B

uh One thing that I wanted to discuss was uh so, since there was a discussion on making it a sub project right.

A

B

What changes exactly I mean, I know we are, I don't know I mean what level we are in. What exactly would change.

A

Yeah, I I've been asking that myself um so bob and george, um they basically said not not much, officially changes. um Well, no, that's not! That's not true. We officially become uh like part of the kubernetes sig ecosystem, in a way that I think we get added to the owner's file and.

A

That's all I really know.

A

Yeah so it looks like it definitely passed. There's everyone just bless wand uh in the thread and.

A

I think we just become more legit, it's it's a it's a tbd to me and I think there's there's an acknowledgment of permanence here like oh. We should continue to be what we should continue to be a big part of the kubernetes project as opposed to a temporary one.

A

um With with that in mind, I see our owner's file is a little uh out of date. I mean I would like I'd like you to have review access at the very least, and um certainly rajula since uh and in caslin too so, there's a gap there.

C

A

I'll open an.

A

C

C

C

A

Anyone else regularly show in.

B

I think chris is already there right.

A

Yeah, I'm not sure if suresh is a org member yet, but I want to help him get there if he isn't already and karthik cartha canyon is still getting in there too. So I think that would be.

A

Cool all right well at least there's that issue open. Oh, I should probably add some.

C

C

Experience working group.

C

Area contributor.

C

C

A

Okay, tagged signed and delivered.

A

All right, my friend, I think, uh well anything else on your mind.

B

Nope, that's not.

A

I think we have.

C

Look that looks like it passed, lazy.

C

A

What does that mean to do? Ask bob or george to join and talk us through that yeah? I think um I'll ask bobber or george to join next week and kind of just give us a deeper dive as to what that means.

B

Yeah, I guess george was here last week. We didn't have the meeting.

A

Right yeah, I I uh was very much afk and needed to be.

C

A

Yeah well, stay healthy and safe. It's great to see you gonna, stop the recording.