Kubernetes Usability Special Interest Group, 30 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 20200630 Kubernetes SIG Usability

Description

Josie reviews her proposal to improve tagging of upstream Kubernetes issues to highlight usability related issues and make it easier for UX/non-coders to begin contributing to the project.

A

Quote: hi everybody welcome to our regularly scheduled Stig usability meeting today. Josie has a proposal for improving how we tag upstream kubernetes issues for better usability, visibility for the sig and others who want to improve usability in our code base and then, after that, we'll take a quick look at the data. The initial data coming in from our usability survey.

B

And so this is less of a proposal for tagging and labeling and more just like what that scope of work could look like and I'd like to use this time to gather feedback and thoughts, and just things I can do in this scope of work. Oh can I share my screen.

A

Yes, sorry they unused to the lockdown permissions. I'll just make you a hosts.

A

B

All right, so the basic hypothesis is that by creating labels for requests and issues relevant to the sinc events, there's an opportunity to learn about the usability needs of the like from the community itself.

B

For the sake, I think, there's it's an opportunity for a way to discover exploratory tracks of usability. Work means to quantify subsequently triage community concerns. With regards to usability, it's an opportunity to increase visibility for our sake and create non-technical opportunities for community engagement, so risks labels are not relevant, labels, don't get traction and specifically because people aren't aware they are interested. There could be short-term memory and, like you hear about it and you're like oh okay, that's interesting, but you might do it once, but never leverage them again and another risk.

B

Is we get too much traction and there are not enough numbers in the sink to drive meaningful action?

B

Are there any other risks that I should think about for this scope of work? I.

A

Think that the only other risk I can think of is getting the labels approved, yeah, okay or I- guess getting sort of buy-in about adding labels. If we need to.

B

um So for outcome, one it was to align on a set of labels that are relevant to SiC usability and ie accessibility. Internationalization UI is the construction really loud. Yes, I.

A

Can hear you but more than I can hear the construction, so it's yeah I would say it's not disruptive and.

B

So the plan is to create an inventory of needs from the cig, possibly reaching out to folks on slack. Look at what other community projects have done so recommendations that I've gotten is UJS, tailwind and rails, create a list of tags and get feedback from the community again via slack and also from local subject matter. Experts and I was thinking of Brian lily, Lyles.

A

B

A

There's one too many eyes in there: ah okay, probably auto-completed.

B

Is is there any other community projects? I should think about is? Are there other ways I can reach out and learn about community needs, yeah.

A

I think it's always a great idea to just ping in contributor experience.

A

Just because there's a bunch of people there who are really engaged, you might have some good ideas and I guess we could oh, and this will probably happen if you can contribute or experience, but the release team might have some good ideas too, since they're kind of you know in the meat of how everything gets made. Okay.

B

And are there any other community projects? I should look into.

B

Okay and anyone else from the community that might provide good insight or have feedback that they that we would find valuable.

A

We could always pink Brendon since he's super interested in how we're sort of automating all of this. He might have some ideas but I think overall, like we'll probably get some interested people who kind of will point us to other people. As we start kick this off so yeah, okay,.

B

All right so I'm hoping that this won't take too long, maybe end of July or by the next sig meeting have a list of labels that we can talk about then outcome. 2 is community. Members are aware and can leverage labels to bring awareness to our sake about UX concerns so I'm, assuming that we're gonna have to create some documentation measure whether or not the labels are being used, gather feedback and iterate I was thinking.

B

Maybe have some way of communicating this at cube con, so that folks are aware of the labels but yeah open for feedback.

A

Yeah I think that that's really great, we can definitely use the platform that the sig has and but maybe we could even make some movement before coop con I think coop con is in q3, q4 I know this year. This year is time is very strange this year, but yeah I think that this is a really great idea. We can definitely communicate what we have at coop con using the cig platform, but then it would be awesome if we try to kind of have the labels available for people to start using at at coop con.

A

So then like there's an immediate action that they can take.

B

So I'm hoping that before cube con, will have those those labels and we'll we'll start iterating before then and see if people are using them or not. Yeah.

A

Yeah and then we can just kind of enhance visibility and I, really like the part of your plan at the very top about making it easier for non coders to contribute, because I think that's something that this cig could really make a difference in is sort of opening it opening up the kubernetes community to people with other talents, so I think having this at koukin and then sort of having people start.

A

You know, know about it and take it back to their organizations to tell others who may not have come to khoob khun, because right now they don't feel like you know, they're contributor, and then you know kind of take it from there. So yeah, okay,.

B

Maybe there's something specific we can do to sure engagement from from non if, like that's our target audience or not just target but like we'd like to be able to leverage I, think.

A

I think we'll see it kind of organically in sort of just engagement with the sig, especially if our Doc's are good and we explain to people like here's, how you look for issues you can start tackling you know we can. We can really your point about. Documentation is really, you know very important, like basically being like hey.

A

If you want to get started, and this is what you're kind of looking for here's, how you can quickly discover it using tags and then here's sort of the getting started thing and then we can actually just start to see it if the issues that we're tagging are getting resolved, so there can be kind of like an active and a more of a passive sort of view. Okay,.

B

Cool and then part three is that as a sig, we're able to identify and pursue exploratory tracks of UX work based on this data yeah. So that's obviously like we'll iterate when we get there yeah.

B

But this is the plan outcome, one hoping to make some headway before the next meeting and then I'll come to by Keep Calm awesome.

C

Yeah I can give up there too I'm Abby Gabby had been working on the presentation with cube Khan for August, and one thing we also discussed was like: how can we encourage, because there are two tracks that you're looking at right? One is the developer contributor and one is the non coder like me. Who's.

A

C

Ux designer has been working on kubernetes. How do we encourage them to kind of understand that Zig usability is also for non coders, so we are going to be in a presentation which we don't share out. One thing and examples are welcome. We want to kind of share, share our examples of how people can contribute, be it the examples that you know medium articles that they might have written. You know around kubernetes and their work that we can start sharing out, giving them a little bit. Leverage through say gives ability.

C

We've done work around the survey that Gaby's done. You know share that. That's very much research focus so kind of expand our horizon on how we can reach out to people, so we're gonna be giving really concrete examples from the community at the cube con, so that people know that there is a lot more out here that you know people can do and then there's this developer experience track that you want to start focusing on which we are still trying to kind of see like what that means, but definitely two three different tracks.

C

So that's their multiple conversations happening through this thing. Awesome.

B

Cool any feedback on the plan, huh any risks I should consider. This is a fairly like easy low-risk, big I'm, not too worried about it.

B

And so I'm happy to share the document and if anyone wants to pair with me on the first part, to do like some research look into other projects.

B

Yeah I'm, happy to pair and I can put my contact information at the bottom of this dock and where's the best place to share it in the slack. Okay.

A

Yeah I would a sudden this out of this fact. In the end, the mailing list- okay,.

B

A

So the other thing that we have is that we do have the data from the sig usability survey, and so we have about 120 responses, which I think is cool and then the other fun thing about looking at it is a lot of the people. Don't work at managed service providers, which is always sort of what we're trying to find. So many people in the kubernetes community do work at managed service providers.

A

I really haven't had time to dig into this at all I'm happy to share this with anyone who does want to start kind of exploring this a lot more, and we can always try and do more to get more responses to if people are interested. But this kind of gives you an idea of what we're looking at and see. Yeah so yeah I mean it was not a short survey.

A

We kind of tried to keep it short nish, but you know kind of gives you an idea of what people are using size of their fleet, what they're trying to do as far as how they're choosing to use kubernetes whether they're using containers in production in the past. So kind of just see them so it looks like we got some good data to start digging into and I know that panel.

A

You and Gabby were planning on sort of using this for your presentation in August, so yeah yeah I'm happy to forward this to anyone who wants to really start looking at it and I may remove the IP tape. Ip addresses I'm, not sure why we have those.

A

But yeah so I'll send that out. I know, Carl was interested and I think he was gonna. Send me his email over slack or something and then pamel did you? Do you want that Gabby already? Has it so yeah it's okay, gabby is helping me out.

C

Okay, Doxil, okay,.

A

Awesome yeah cool, so I'll share that out, and then you know kind of. Let me know if we want to try and push for more responses or if we're happy for like our first one, like I, actually think 120 unique responses. Right now is actually pretty solid. It looks like at least half of them are from people who aren't building kubernetes solutions themselves, which is cool because, like that's kind of the community, we want to make sure that we are understanding and yeah cool. Any questions about that. That I can answer real fast.

D

Question alright, um when I explore it I'm, probably gonna, do it in R, which will mean if we get more responses, it'll be pretty easy to pull through, but I was curious. Are there any brand colors for kubernetes for like making.

A

D

Because I looked and I couldn't find them.

A

Yeah is: did you check just like kubernetes I? Oh because there's like all this stuff I, they might be more about where you can use the logos, but they I think they might have a brand site. I can try digging it up. Okay,.

D

If you think something out there, I can I can look to I. Just didn't even know that that was yeah.

A

D

A

And also pinging sig sig contributor experience like they can often answer my questions like really fast. So if you ever have a question you're like random question, you know that's kind of my spot to ask.

D

A

Okay, cool so yeah, so Carl make sure you get that data right after this call and if there's no other questions I think we can probably wrap early Josie, awesome presentation and I think that having that tagging mechanism will be really valuable, so yeah, let's, let's keep pushing that forward. Cool. Okay thanks everybody hi.