VMware Carvel Community Meetings, 10 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Carvel Office Hours - June 10, 2021

Description

Carvel Office Hours - June 10, 2021
We meet every 2nd and 4th Thursday of the month at 11:30am PT and would love to have you join us live!

This week's office hours focused on continuing the discussion surrounding issue triage processes and best practices. If you have any feedback you wish to share after viewing, please reach out to us on slack: https://kubernetes.slack.com/archives/CH8KCCKA5

Notes + agenda from this meeting can be found here: https://hackmd.io/5Bh2IXwTShSrA0YdBY4AGg#June-10-2021

A

All right, hi everyone welcome to this week's edition of the carnival office hours if you're tuning in from home. um We encourage you to attend these live. We meet every second and fourth thursday of the month at 11. 30 am pacific time.

A

If you aren't able to attend the office hours, we also have community meetings and those are every monday at 11 30 a.m. Pacific time the office hours in particular is just an opportunity for you to bring anything up with the team that you need more in-depth help on or have a particularly particular discussion topic. You want the maintainers to go over, and the community meeting is another opportunity for that, um with more focus on what the team is currently working on.

A

If you have anything you would just wish to discuss today. Please add that down here in the discussion topics, or if you have anything you need help with down here below and open questions, help needed when you attend the meetings, be sure to read and abide by our code of conduct and just a reminder these are being recorded, so they are uploaded to our youtube playlist for everyone to consume.

A

Also, while you're attending, please add your name and any company or organization that you are representing so that we can keep track of who from the community is, is attending these, and we can, you know, keep those communication panels open with each other.

A

All right today on discussion topics uh we are hiring. We have this particular uh return ship opportunity for working uh with the carville team, and we also have one for a member of the technical staff. uh Erin. Do you want to go over these two particular items? You'll call out for some yeah.

B

I I guess, like one thing, I'll call out for the return ship is, that is part of um a specific program that we're running here at vmware, and the idea is targeting folks that um have engineering engineering experience um like five years or so of experience, but have been out of the workforce for the past couple of years, so uh really focused on, like folks that have been doing uh caretaking and are looking to get back into the workforce.

B

um So the return ship is an 18-week. um You know internship like thing and the idea is you know if, if that goes well, it would likely turn into a full-time role.

B

The other role software engineer- that's that's also just a a regular opening, not part of any particular program, um and then I was actually about to add a third item here, which we we do still have um an opening for a senior engineer, role in india um so I'll be sure to add a link to that opening.

A

Great thanks, aaron, and would you be the hiring manager for those two roles and well now the third role as well.

B

uh The first two, but not not the one, the third, not the senior engineer role, okay,.

A

Right moving on to the next item, um bringing up something that we've been discussing in a recent community meeting as well as office hours that we had uh last time we have the github issued triage proposal. However, we're looking to manage our uh issued triage processes. um John, do you want to go over this.

C

Yeah yeah thanks nancy. um So let me let's see if I shared my screen, there's a couple of tabs. I wanted to to go over. That's okay,.

D

One second, let me get the right one. Can you see my screen, there's that doc, okay,.

C

Cool um so yeah last we left off with this. We had gone through the label, definitions in issue states, and these are like talking about how stuff would flow through.

C

um One thing we could do is there's been a number of conversation, slash questions in the document, so some of it we can just sort of bring that real time. So that's one one piece: the other is looking at our zenhub board with no issues on here. This is what it looks like, which actually includes definitions of these swim lanes, which the observant reader would notice that the first set of these actually matches perfectly with the names of these issue states and that's on that's on purpose.

C

So that's another view to kind of look at this as we're trying to figure out what means what where another view is the pile of issues. So this is how somebody who's not using zenhub, would see it um and then, finally, just to kind of round it out. Here's an example of like this is currently um this is a sketch. This isn't not visible on our github per se, but there's a way of like creating something.

C

That's like a zen hub, it's github projects and you can move stuff in in this sort of like compound board.

C

So anyway, so I thought what would be valuable sorry, then there was one more thing that I that I thought was useful is between last time and now we've actually done a couple of rounds of issue, triaging and so folks have have made an attempt at working within that that'd be useful, maybe to just start with that. To start with folks who have been doing the community triage talking about how clear this is or not like. How did it go um say?

C

I think I'll just sort of open that up like what you what you did and all that anybody want to share their experience.

D

E

I can start off. I've done the triage for two days in the last two weeks and during those days my process is generally that I go to the zen hub board and I go to the carnival accepted lane here and I read through all the issues in that lane and I attempt to create some kind of acceptance criteria for it.

E

So if it's in that carnival accepted lane, then I know that it's something that's been looked at by a reviewer of that tool and that they know that this is something that we may want to look at further in the future, and that is like ready for uh possibly ready for development by someone from the community.

E

If that's something that a community member wanted to push through um so giving that acceptance criteria is vital for that community member, if they have submitted an issue that they want to work on and have that like kind of stamp of approval from the maintainers.

E

um So a couple of the pain points that I've experienced- I would start there is um one of them is if we're waiting for more examples. um I think one example of that um might be the key matcher path, one for k build and so at the bottom of this one there's a comment that says.

E

Let's kind of wait for more examples for this uh before we make like a decision, we do have a possible solution, um but there was a workaround for the problem that was being experienced, so we're not seeing any in the wild examples of. We need this capability in cable that we need this functionality in k-build, but we did come up with an idea of one way to address this as an enhancement.

E

So I didn't feel comfortable drafting acceptance criteria for this.

E

Yeah and then a couple of them are labeled with discussion. Sometimes it feels like we're awaiting more replies and then in the github triage document, the proposal document at the bottom in process steps or maybe yeah near the middle.

E

It says to like put the acceptance criteria and wait for a thumbs up or if it's been a week, just move it to the next column and by putting the acceptance criteria through an edit at the top of a comment that already exists. It's hard to tell if a new thumbs up has come in towards that comment. So uh just a little bit of ambiguity, though that hasn't, I think, been fully fleshed out. uh So what.

C

E

Where are we describing that in.

C

Here it's like wait a week here we go, give it if a thumbs up is given within a week should be moved. That's interesting. Does anybody remember the context around what that delay would be about.

E

If a thumbs up was given or a week has passed like, I give you a week two thumbs up and if not then move it along anyways.

E

That's what I'm reading there is that what you guys are seeing.

C

Yeah, does anybody remember what the rationale was behind sort of this automatic time-based approval or we're moving it along.

A

C

From the others.

A

That aren't are um aren't on. The call might be a little end.

C

It's kind of landing that way for me, I'm not sure why. That would why we would decide that. Okay! Well, a week later, it's now yeah I feel like, I feel like something moves from a lane, because new information has arrived and that's what changes its state rather than time is that, yes, you see a lot of nodding, so all right, so maybe what we can do here is just say.

C

Okay, that's a great call thanks: okay, it also means that, like you'd, have to put the acceptance criteria in a comment so that somebody could thumb up that comment and it's not confused with a thumbs up or down of the issue itself.

E

C

Exactly um interesting, and so who would be giving this thumbs up, prove a review of the except it would ensure that you criteria is that? What is that? The implication is that this gets approved.

E

I think so like I, when I added acceptance criteria I didn't at like if it was ytt, I didn't at you, john or if it was a cap I didn't at dimitri, um felt like they would see the email update or the github update notification.

E

And then, if this is on your guys's routine as well, then you'd see an update.

E

I don't know if that's a bad assumption.

C

Yeah, um I tend to I've been using the notifications, github notifications, try and keep up on stuff. So if you make any kind of edit I'll see it.

E

C

um Personally, would we do we do we need uh approver reviewer to thumbs up acceptance criteria.

C

What might what might they know that somebody who wrote the acceptance criteria wouldn't no.

E

I could see a world where the comments are misinterpreted and so the acceptance criteria doesn't align with what the comments said.

E

But I don't feel like like personally, I would try not to write acceptance criteria for something I don't feel like. I have a great grasp on so I would feel if I put acceptance criteria on a story I feel like it doesn't really need the thumbs up.

E

um Maybe we'll get a comment from a community member if it is confusing, and that would be a signal.

C

Yeah, so I wonder so, may we maybe carrie did you? Did you have some thoughts around that I'm just trying to not miss the comment. Go ahead.

F

No pretty much what what garrett said too, like I wouldn't probably write acceptance criteria if I didn't feel like it captured the issue and if I felt like I needed someone to give a second opinion on it, I could pull in a reviewer.

F

But I don't think it needs to happen every time.

C

C

Does that capture what you were thinking gary okay,.

C

Yeah and frankly, like from from what I saw like the stuff that was going on, there was like top-notch like really good acceptance. Criteria very thoughtful seemed like good coverage, just kind of poking at it. So I don't know I feel like that. Piece is starting to work.

C

Okay, I felt like there was other stuff. You were gonna mention garrett.

E

Yeah, I I was gonna say maybe some of the positives since I picked some of the points.

E

Some of the positive things is that it's not overwhelming as it as it used to feel. um There is often enough context to like really immerse myself in a concept that maybe I wasn't so familiar with in the past, and it's both provided some good opportunities for me to learn and um some areas to like just to be like uncovered, like the veil, has been lifted in this like certain area of ytt.

E

That's that was maybe somewhat interesting but scary at first, so it feels much more manageable and no matter how much progress like I make in one of those triage days. It doesn't feel like it was unproductive. So I was a little worried about that as well.

C

Yeah that that's been the case in the past, hasn't it yeah, yeah cool. Oh that's great, to hear also it's more satisfying like on a personal level. It's like, like you say like at the end of the day, you feel productive. It's important.

C

What was the first thing you were talking about? You said it was like further.

C

D

There was one item: you know the weak one, the one that you had. Oh, oh, okay, all right. Okay, so we got that okay, great cool.

C

Anything else about folks experience is there more garrett that you're thinking um carrie? Did you have any.

D

Feedback or reflections yet on this side.

F

um One thing I've been able to do a couple of times since being on this role, is triage bugs um and um well pretty much every time I do this role. I go immediately to the triage document and like remind myself what it is that I'm supposed to do, um and it's been really clear.

F

So that's really helpful for me because things are changing and it's nice to see exactly. You know what I'm supposed to do in with triaging bugs.

F

It feels very straightforward, like try to replicate the issue, try to get any more information if it's needed, add these specific labels and um it feels really manageable and like I'm not wasting cycles.

F

You know trying to uh maybe triage an issue or feature that doesn't have enough information like I used to in the previous process. It's it's pretty well explained. So, overall, that's been a good experience.

C

Okay, great and are there that's, that's really good to hear that this is useful and not just a document for document's sake, but like a working document. That's what I'm hearing um are there any parts in particular that you like, or you wish, were different or like, as we continue to refine this as things we should make better here.

C

Like what what where does it start for you? Do you come here to this state, or do you go to the triage bug or.

F

um I think I start here.

C

F

And first triage bugs and then if there are none, then I go to the second process. Carbo accepted.

C

Oh, I see and then is, is what's here enough or do you jump down to the link.

F

I jumped down to the link.

D

Okay, um that's nice.

F

Yeah, it's like boom boom boom. One two, three.

C

Yeah yeah yeah just do this thing: okay, cool okay, so that I'm hearing like that helps like load up in your head. Like oh yeah, that's right this process, and so it's sort of less times figuring out what to do and more of just doing it.

F

Yep, just read it once at the beginning of the day and then I don't have to come back to it or wonder.

D

C

Cool and then the other one was the carville accepted one.

F

Yeah um I haven't done as many carnival accepted issues.

F

um One thing I did find myself doing is wasting a lot of time reading through the comments on an issue only to find that the end was either like really clear and didn't need acceptance criteria or the acceptance criteria was already there which, if it was already there, that was a quick fix. The next issue, I just scrolled all the way to the bottom and checked, um but it did happen a couple of times where I I spent time reading through the whole issue and then ended up not needing to do anything about it.

F

I think that corresponds to what we have with. We were talking about earlier about waiting one week to get approval or like a thumbs up on acceptance criteria. So this issue was hanging out in the carnival accepted column.

F

It already had acceptance criteria. We were waiting for someone to like approve that acceptance criteria.

D

F

And as the rev uh community roll, I went in here and it was like: oh it's in the carbon accepted column, it must need attention.

C

I see okay, so if we, if we end up like not saying that you need to wait a week or even get any kind of approval or whatever that would help fix that issue of like hey. If there's, if I added acceptance criteria, then uh it means that I'll pi put it either in unprioritized or prioritized backlog, which, like is this, is this happening to you like, since I upgraded to big sur like now, my fonts hero is black?

C

Is anybody else going having that experience like this is supposedly white and it won't display as white.

C

Americans you're smirking carrot yeah, it's like.

D

I don't know anyway, okay.

C

um Okay cool, so it sounds like that would be addressed through that. Okay and then do you also like click down in here and like remind yourself about this? Is this useful.

F

F

I think there's a different section that I look at.

F

Maybe not I I don't read the elaborate features section.

D

Okay, okay, workflow consideration.

D

Okay, I think it's a little a little fuzzy all right.

F

Yeah, that's my experience like overall, I think it's an improvement, but um you know I haven't worked in this role very many times, so I also you know, I'm interested to see how it goes from here.

C

Okay, cool all right. Well then, the next thing occurs to me: unless somebody has commentary about what we just talked about.

E

Yeah, I have one thing: um I think that in the future uh the community pair could also um triage duplicates, I'm not really sure how that would be easily identified at all, um but that just does seem like something.

E

That's certainly within the power of someone um doing the community payroll.

D

E

It would just cause a lot of filtering for them that they wouldn't have to do otherwise, like, if you just added it to the list of responsibilities.

E

It's like this.

C

Like when it's a new issue, yeah.

F

So this would be like someone submits a bug, and that issue already exists. This would be like labeling it as a duplicate.

E

Yeah, that's what I would see like, maybe labeling it closing it saying like hey just if please reply on this issue and if you really don't think it's a duplicate, we can reopen and continue the discussion here, but.

F

Yeah that totally makes sense. I I think even that could be expanded to say, like change the label of any issue that isn't appropriate.

F

C

F

And it should be enhancement, you should change the label right.

F

I think it's similar to duplicates.

C

Yeah, maybe this is I'm hearing two things there. One is that, like we all have like the ability to uh garden this, this garden together like and you see something wrong to fix it like we're all there we're all like at that point, um and then the other thing I heard was um that like it might be helpful, I think that's what I was hearing from you guerra is like might be able to have a call out.

C

That specifically um reminds reminds you, like, oh you're, doing a community pair like go to triage a bug, and then one possible outcome is that it's a duplicate like it isn't always gonna be you can reproduce it right like there might be like we might learn interesting ways to share with each other on how you can identify a duplicate, for example, um so there might be like an overall process that could could speed that part.

C

um The sooner we catch those the sooner those conversations get concentrated on a single issue, etc, etc.

C

D

All right uh market has duplicated.

C

Error messages: what are ways might that you might do that.

E

Are you obviously searching right.

E

Thank you. I've I've noticed that sometimes a look for the faq in our docs.

D

C

Okay, well, we can elaborate that later, following our hunches yeah seriously, yeah some of it's is- is up in the wet wear right, yeah. Okay, that's a great one! Great call out carrot: okay, we'll elaborate on this outside.

D

This meeting it's nice to.

A

um So, while we're kind of talking about this community pair item, I'm thinking in in the broader community, thinking about it being an open source project, eventually, hopefully we'll get outside contributors, people who do want to help with triaging, um you know maybe even eventually become maintainers, and I'm curious as to how well one um ident like describe or have some sort of description of what a community pair is. um It doesn't seem like that's here. I know that we know what that is.

F

A

Outside of us is unsure of what we mean by what is a community pair um and how that's assigned each week and two. If someone is outside of vmware and is not interested in contributing, how do they actually work with the community pair on helping out.

A

Is that something like when we're in the public um carville channel? We say these are the community peers for the day for the week you know if you're interested reach out to them.

F

E

F

I don't think we broadcast that right now, but that's a great idea.

C

Yeah, I feel like I missed something just there nancy to write down in here to elaborate on.

A

Oh, uh so whoever is the community peer for that day or for that week to identify themselves in the public cargill channel and so that folks know to reach out to them. If they're interested in helping out with any triaging.

C

Like I don't know, pairing on it,.

A

Exactly so, they insane be part of that.

C

What the you mean like learning, how to do a thing by working with somebody, who's done it before that's insane.

A

C

Aaron, did you have any particular thoughts around that I'm just drawing you in.

B

No, I'm I'm mainly just observing here. um I I guess, like one thing I have noticed in other communities is that like they have essentially uh assigned or someone volunteered to be like the triager of that week, um and that has been handed off in like community meetings not really suggesting. We do that, but mainly just sharing that that is a practice that I've observed.

D

Coco, this is good all right.

C

Anything else, otherwise I was gonna kind of sort of go down, go down the comments and see, if there's stuff, that we can pull up together. I think there's a couple conversations here that worth hitting on.

D

C

Just chime in um one piece here is aaron making sure that whatever we end up doing here, we start to move these into the um contributing markdown. I think it's like currently mark in in governance, we'll like move that into the contributing markdown and the main repository okay.

C

So that's where this will sort of ultimately end up.

C

Okay, dispatch, the description, okay,.

B

And also I'll defer to nancy for organizing all these things properly.

A

um One thing I was going to just ask I zoned out for a split second, but I don't know if you just said this: when is the?

A

um When is like that? When do you feel like you're at a point where this can be moved to they're contributing.

C

Yeah, that's a good question. I think right now we're just sort of using a google doc like it started out as a proposal, and then we like reused, recycled that we're recycling the bits and now it's turning into like this process. Definition dock sort of evolving. Its way um I feel like if we can it's quite editable and and highly collaborative here in this format, so maybe maybe when we get the feeling that things are sort of settling out um hitting some kind of steady state.

C

We're not making huge edits, then, which feels like we're getting close to that. Then that might be a good good time to sort of pull the trigger and make this all marked down.

A

D

Good question yeah.

C

Okay- um let's see this one in particular was about the can be replicated. So there was a conversation here asking about whether or not this was useful or maybe do a duplicate, especially with respect to bugs, um like couldn't carval accepted mean that the that the bug was duplicated.

C

I wish um daniel was here, but he you know this basically said be nice to know whether or not a bug is reproduced, but would we actually accept it without trying to reproduce it.

B

Yeah to me, I wonder if there's overlap with ready for dev.

B

Are they kind of getting to the same point as in someone could work on this.

C

Yeah, it's interesting. I think one thing that we've been trying to do is break up the total amount of work into smaller tasks in order to evolve an issue, and I can imagine being able to just reproduce the issue and capture what I did to reproduce the issue, but I didn't necessarily go into well. How would you fix it.

C

Which, I suspect, might be part of what would get get that bug into ready for dev would be at least some kind of conversation around.

C

Even if it's like, oh well, this would obviously be fixed in such and such way, but often it's not obvious.

C

So I feel like that elaboration, that contextualization of like okay, here's the problem like what would be a potential solution that the ready for dev piece in my mind would be about that. Second half.

B

Yeah, that makes sense. I guess what I'm trying to minimize for is like overhead and that's where I, I think, try to reduce the number of labels or anything as much as possible. So I'm wondering like, under what circumstances would you search for that can be replicated condition like I'm looking for what value this label provides? Oh, that's so.

C

Good one thing I think of is like visually, so if I see bug- and I don't see can be replicated like boom like has this been.

C

C

Oh yeah, and this this one has.

C

In fact, it's uh there's there's a piece of it. Yeah this this one's, pretty fuzzy but like this is even like getting close to well. We can fork this off and do some better documentation.

C

C

huh So I didn't see anywhere in here where so many directly replicated reported. They replicated this, but I mean that's, that's the flip side of what you're talking about which is well. If you create a lot of stuff the things like, if you have to like all these process steps, then you know we don't do one, then that is also noise.

C

Oh well there's this and I think you know this happened in february, so.

D

I'll just add that.

B

Cool yeah, I mean I'm happy to try out these things. I'm just trying to be conscious of again kind of thinking about a new person joining the project, and we we say like this is how you manage our backlog.

B

Right now it might be a little intimidating.

C

Yeah, especially if, when you start off you're like just learn these 20 labels.

F

C

Yeah, it's a great point.

C

Anybody else have thoughts on on that particular topic like yeah. Does it seem like this today just right now what you know and experience is this: a useful label.

C

This can be replicated.

F

One thing I was thinking is, this is likely done by the community pair or the label would be added by the community pair they're able to replicate the issue um and then a reviewer or approver would come in and review that bug further. Maybe car will accept it.

F

So it's kind of like almost a signal that the community pair has looked at the bug and is able to verify it so that the reviewer and approver they don't need to take that step again.

F

But I think that that could easily be done by a comment saying I'm able to reproduce this issue such and such.

F

So I I don't, I think it serves a purpose, but I think that purpose could easily be taken care of in a different way.

C

Like a comment.

B

So here's an idea- and maybe I'm jumping, jumping to solutioning too quickly but like like what I view the conditions to be helpful for is knowing what is the state of this like bugger issue like how mature, I guess is it um something could consider, would be like adding something to the issue template where you would have like these check boxes like if I'm following a bug then like there are these different things like can be replicated.

B

uh I don't know what the other things would be like identified, solution or something like that, but that way at a high level, you can just kind of see like what state is this in which I think is what the conditions achieve that value right.

C

Now yeah interesting, so would this be like in the template? There's a section: that's like maintainers only like office. Only it's like the.

B

Maybe- and I've seen I've seen this for proposals before to show like what state a proposal is in.

C

Because I might imagine that, like if I'm reporting a bug- and I see a check box and it says- has been replicated like yeah- I just did- I don't know- I don't know I I guess interesting, so you were just thinking just more generally, you weren't thinking specifically like manage work workflow just for maintainers in the issue you're just saying: let's just what are the things that need to happen to mature this issue.

B

Yeah yeah kind of just thinking out loud as well just uh trying to surface ideas and see if there are ways where we can just make things a bit more.

B

C

Yeah, because some of these labels do feel like that right, like there's this action that has been taken on it.

C

Cool, well, maybe we'll let that one percolate sounds like there's an opportunity to try some some of this out a little okay.

D

That's just it to.

C

Do right, let's just uh adding another label.

C

uh The suggestion here is there's greater context than what's available on the issue. Conversation might be needed sure I was pointing out. Well, if you've marked these things, then hopefully the context is there that is broadly present.

C

So I'm not sure why you would need that and then he also noted that perhaps it'd be helpful to clarify the difference between what unprioritized backlog and prioritized backlog means.

C

What is that? What does that mean to folks today the difference between unprioritized and prioritized.

A

uh Just from my perspective,.

E

A

Means that it's actively being worked on and unprioritized means it'll be worked on, but it hasn't been assigned.

A

B

Yeah, what does it mean for you aaron?

B

For me, it's planned and unplanned so prioritize work is work that we generally have planned or as unprioritized as we know, it's a thing, but we're not planning to do it again. As the maintainer team at least right now, gotcha.

E

Yeah, I I see it as prioritized as currently approved by product and will be worked on in the next three months in the next quarter, and unprioritized is unlikely to be gotten to for us to get to in the next three months.

C

Okay, yeah, that's making sense to me and, as a matter of fact, I wonder if it's tough, we'll even think of it as a bit of a spectrum that the things at the top of them prioritize backlog are the most likely candidates for things that would make it into the prioritized backlog that it's that it's prioritized within the unprioritized bank that it's like ranked so that the things at the bottom are things that's like.

C

If, if you want to, if you want to make sure you can pick up something, that's valuable and useful, and and not very likely, the team's going to want to get at it soon.

C

You could you could pull from here, but um if you want to understand what what the team might might likely be up to next the stuff toward the top would be those kinds of things. But you know because it's not a commitment, things may change.

D

Yeah, what do you think about that? Aaron.

B

Yeah, I think, like I know we have done some work to kind of relatively prioritize these items um within the unprioritized backlog.

B

I guess like the disclaimer I I do just always try to present is like we call it the unprioritized backlog, so there's no promises there, like once it's over to prioritize, is when I feel like it's actually planned, um but yeah. You could consider the things that are in there at least like relatively stack ranked within like relative to one tool. Maybe I wouldn't consider them to be stack ranked across tools.

C

So if I put on a particular filter, so if I just look at I've been having trouble with zen hub like there, we go so just looking at um image package likely. These are ranked with an image package.

C

B

So but yeah I would rely on people that are organizing this more, um which were like image package I felt like was helen and joao and dennis, but I would, I would say roughly yes, okay.

C

That's something that we could aspire to in terms of improving the clarity of that column are taking a run at so like for ytt, for example. There's 57 issues be great if if there were nothing toward the bottom, that was a likely candidate to be picked up by the maintainers, um and vice versa, like the things at the top weren't, actually very likely to be picked up by the maintainer teams.

A

I have a question: uh if there is someone from the community that decides, they want to work on something in this and prioritize block and they're actively working on it. Does it then get moved to in progress like what lane does it get moved to if at all, and how do they do that? Do they do it themselves or does someone from the maintainers have to move it out of and prioritize, or does it stay there.

B

I yeah, if you know the answer, feel feel free.

F

I did look this up a while back um if they open a pr, um it will show up in the in progress column.

F

The issue needs to be linked to that pr to move to the same column, however, and I I'm not sure if a maintainer has to do that or not, but basically, if you open a pr, it will show up in the in progress column.

A

Okay, so it sounds like that might be something that we should add whenever we're moving it to the contributor markdown about like. If you are interested in contributing to these particular issues, you know pr will be open and issue must be linked to pr to be moved from.

B

Yeah and I'm not sure if just anyone can link things like that's something, I'm not sure about, but generally, if someone wants to claim like work on an issue, I'd say just talk to us about it and we can assign that issue to you and move it in progress for you if they.

B

D

Cool all right, I see that we're basically at time there are a few more other.

C

Comments here, but I feel like we've, we've been able to sort of clarify a number of things, um get some feedback on how it's going so far.

A

Yeah, it sounds like um this might be something that we just continuously bring up with in the community meeting and office hours, uh ongoing discussion, making sure it's working for everybody.

A

All right so with that, um thank you, everyone for joining today. For this week edition of the cargo office hours we meet every second and fourth thursday of the month at 11 30 a.m. Pacific.

A

We also have our community meetings every monday, that's also at 11 30 a.m. Pacific time, if you found that this particular discussion item is something that you have experience in feedback on, we would love to hear from you whether that be you attending one of those options, live the community meeting or the office hours or you can provide feedback directly to the team within the kubernetes black workspace in the carville channel.

A

We would love to hear um some outside perspective on this and, and you know, help the team with with this process and uh or anything else you may need help with. You know we're eager to engage with the folks from the community. So uh with that, we look forward to hearing from you bye. Thank you. Thanks, bye.