VMware Velero Community Meetings, 5 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Velero Community Meeting/Open Discussion - Jan 5, 2021

Description

Jan 5, 2021

Status Updates
carlisia
- Back from 2 weeks PTO
- This week will be PR reviews and addressing code reviews on my PRs
bridget
Catching up after PTO
On community support this week
Will pick up work on multiple credentials support again
PR #2403 needs another review
nrb
Also catching up after PTO - need to catch up on opened issues and outstanding PRs

Discussion Topics
carlisia
are we ready to start with the GitHub Discussion? I started a list of potential categories here: https://hackmd.io/OFFTp_RIRmOQ7xwhxkv0yA

A

Welcome everyone to the first bellero community meeting of 2021.. This is the valero community meeting and open discussion uh today is january 5th, 2021 everyone's back from pto. What has happened and uh what are we doing.

B

Happy new year, um everybody from vmware was on pto for two weeks and we are back and I don't think I'm gonna be able to open any pr this week. There are a lot of pr's to review and I also have a few pr's that I need to address the code reviews for so that's gonna, be it for me this week.

A

Sounds good, um do you know if you have any blockers this week.

B

I don't think so.

A

Not right any questions, comments for kalecia all right, moving on to bread, yet.

C

uh Very similarly to everyone else, catching up after pto, um I'm on community support this week, so trying to get through the backlog of issues and things that have been opened uh during the break. So I apologize if you've had to wait for things um we're getting there and we'll hopefully get to you uh pretty soon um other than that. um This week I before I left for pto I'd, updated the pr for the multiple credential support, based on um a meeting uh that the maintainers team had had.

C

um So I think that neat that that needs another review and then hopefully we can come to a decision on the approach that we're going to take um and then I'll try and start making progress on that work. um So that's it for me.

A

Awesome um any questions, comments.

A

Any blockers here.

C

I think other than maybe just having another review on the pr, um as I mentioned, but um I know everyone's got a lot on their plate with reviewing other pr's as well this week. So um that's it.

A

Sounds good all right, uh nolan.

D

Again um also catching up after pto, uh we all took two weeks off um need to catch up on open issues and outstanding prs. um We've got a few things that were in flight uh prior to the new year and need to pick those things up. um uh One thing I will say uh is we didn't get much merged in the last two weeks uh and right before uh break. It was mostly some small things from genting.

D

So uh just a pre preview, there's not much in contributor shout outs this week, um but I think most folks were off for the holidays, so yeah slow slow week this week catching up and remembering what what I was working on half a month ago.

A

Yeah, ramping up and and getting uh getting started again. uh I feel that um any questions comments for for nolan any blockers.

D

uh I don't think I have any blockers at the moment, but I'm still like going through my backlog of emails, somehow there's a lot of generated email even over vacation and some of it's twice.

A

All right, uh let's dive into a discussion topic instead, uh carlesia.

B

Yes, I wanted to bring this up to see if we are ready to start thinking about starting the discussion. I think I think we agreed that we wanted to do that.

D

B

D

I can I back up and have we talked about this in a community meeting before I don't remember.

A

Don't I think we brought it up a while ago, but um yeah. I think it would be worthwhile to just rehash it.

D

Yeah, can you so? Can you give some background for alicia just so we just so. We know yeah.

B

Yes, so right, I I backing up, uh so we talked, and now I don't remember if we we definitely talked among ourselves, the the maintainers. I don't remember now if we talked openly, but we were looking well. I start bridgette looked into this. I looked into this uh separately and then we figured oh and join us as well, so basically we're having the idea of enabling the discussion tool in in the in our github repo and having that be where we do support and also incentivate people to help each other.

B

It works like a stack overflow like if we for for categories that we just assigned to be where q1a or support help is going to be it will.

B

We would work like a stack overflow where anyone can answer and if an answer is the most appropriate answer or the correct answer would be marked as the correct answer and the person who answered that correct answer will get uh recognition from github as a contribution so that it's a good way to uh acknowledge people's contribution and and and and yes so unless, if going that route, we can people when people open an issue.

B

That is that we notice is a support question. We would transfer to the discussion area and handle support there, but we cannot have different categories too, like we can have a category for announcements where it's it's it's a place where it's more permanent, like you can take. You can open the announcement page, for example, and see the previous announcements, whereas twitter or slack it just disappears uh after a while. So I suggested those categories. um I know there were categories added by other people too. As suggestions, I think the last two or three anyway.

B

That's the idea.

A

So with this, we would move discussions off of the valero mailing list as well and keep but keep that for uh meeting invites and uh announcements, uh maybe but other than that we would essentially retire that for discussions completely. Yes,.

B

I forgot about that. Yes, we would lock that for for for posting and and try to redirect people to just this one central place and of course we still wanted slack, but also even slack. I think we, you know it would be preferable to to have these uh support interactions here. Slack is, is not as good, but we will not we're still monitoring slack, but not the google groups I mean, like jonas said: we will just use it for announcements, but we'll lock it for for posting.

D

Yeah and now a benefit here is like: if someone just has a question, they don't have to open a github issue. um One thing from from our perspective is sometimes we get questions that aren't really bugs or issues with the code they're, just hey. Where do I find this um that's easily converted into a github discussion in the github ui? um So that's that's. I think something for us to help kind of streamline our.

D

A

Is it possible to move things around uh if we wanted to change the categories later on? Can we move content to another category? Let's say we we wanted to retire, the valero featured uh to to be something else. Can we move content before we retire it or you know how that works.

B

I don't know: okay.

A

Just something to to think about.

D

These these discussion categories are effectively forums to use like old parliament's right yeah, similar to that yeah. So, there's there's like a community support q, a forum.

D

Old internet lingo.

A

Before social media.

A

Yeah, I I I say: go.

D

Does anyone outside of the outside of vmware have a have any thoughts on this? Have you used it? Have you had feedback.

D

If not, we will take lazy.

C

Consensus, I'm trying to post the link here in zoom chat, um but it looks like if you delete a category uh github will move all the discussions in that category to another, one that you specify so so, there's no, I think, there's any fear of things being lost. If we decide to change the.

A

A

All right um kalisia, do you, um do you want to set this up, or do you want me to set it up.

B

I can set it up um just wanted to get like uh before I set things up like: let's get an agreement on what we want like this I mean. Does anybody want to add anything to this list, so we can like look at it all together right now or do we like? I think there are certain certain things here for sure we know we couldn't want so to avoid opening a category and then thank you. We should delete it.

D

um Yeah, I think the design one could be removed because I think we could. Those could just be issues in pr's. In my opinion,.

D

Because like if we're, if we're talking about refining a design, I think that should be in the discussion on the design. Otherwise we're looking at like two different places, and that can be difficult.

D

What do you think.

B

I'm fine with that. Okay, um I think I so the reason why I put design there is because I'm thinking so so with the github discussion, you have the ability to like thread off of a different different.

B

How to say like there is. No, the thread is not just linear you can you have sub threads, so it just makes it so much easier to like hone in on one thing, as opposed to like copying and copying and pasting, I'm coming commenting on this part of the document now which which also works. So it's not, I mean what yeah so like we you. We could use that to like talk about something that we are discussing and then update the documents as a result of the discussion, but you're right.

B

It's with looking at two different places, so trade-offs.

B

That bugs category in contributor tips, I'm not sure.

D

Yeah bugs, if someone thinks it's a bug, you should.

B

Just open up an issue.

D

B

In contributor tips, um we don't have that much load for for contributor interactions so to then I wouldn't open it and we we do have documentations for contributors. That we are, I think, are pretty up-to-date.

D

Yeah, I was going to say: should that just go straight into the documentation.

B

Yeah community shout outs, I like I don't even know if I wrote that or not.

A

um What about feature ideas? uh Because we already had feature requests as an issue template as well.

B

Yeah we could remove that and just use issues.

D

Yeah I know in the past there's so in other communities. I've been in um they have like this is like a user support, mailing list that people use and then there's like I'm specifically thinking of python. uh They have python mailing list and then they have python ideas mailing list, but I think the python ideas mailing list is of questionable value. So, um but that's where people kind of brainstorm and go back and forth on hey, should we even propose this thing, um but there's a lot of noise on it.

D

Also python's way better.

D

There's also nothing to say, we can't add these later if we find a need for them, so I I think it would be good to start small um and then add as we as we find a need.

B

So uh we cut out features like features right feature ideas. I think.

D

So I think people can raise an issue and we can flag it. um Where did we land on design.

B

D

I think design can be similar. I I I think I grouped that with feature ideas and discussion about me mean existing in flight design would be on that pr.

B

B

This velero featured category, I think it's good yeah. It doesn't cost so much. There's not so much work to just drop something in there and people can have a running ta a running view of what's been happening.

A

B

A

Yeah, it's it's an easy way for, for others to um say hey. I found this cool thing that someone where someone talked about valero as well, that we might not know about yeah.

B

Yeah, it's hard to keep up with that on our blog on our website, so yeah.

A

Yeah, I think this is uh this is a a better way to do this.

B

Community, shout outs: do we want to have that.

A

I say: go for it for now and we'll see.

B

A

I don't see the harm in that one.

B

I mean it would be yeah. It would be a a place like again like uh it's almost like documenting, for because we give people shout out here and that's awesome, but.

D

Yeah, it could be a little bit longer lived.

B

Yeah longer lived and like a dedicated place that we have to to honor people all right community meetings, I think, is great to um I don't know, I I think it's good.

B

We posted the link and the content of the hackmd, so it makes makes it easy for people to search people searching something that we had a meeting on. They see. Oh, they talked about this in the meeting. Then you know they could go and watch the video if they wanted.

D

Octant does that I really like that.

B

I don't think they faced the content of the the meeting, but I think I think that would be like extra helpful. I thought.

D

They did really well or.

B

Maybe they do okay, yeah.

D

I thought I thought wayne did and he just they just used the community meetings.

B

Yeah yeah, I think you're right, I think you're right. I think yeah.

D

B

D

They just have real short, they have real short agendas. They they use their heck md for that meeting that day and then they they move everything out.

B

So and then general discussion and um announcements community support, I think those make sense.

A

B

Anything else, of course, we can add things later.

A

Yeah, I think that's good yeah, all right.

B

A

B

I'll do it I'll set this up this morning.

A

B

Thank you thank.

A

B

And then bridges, you can start moving things there.

B

That would be that'd be very good.

C

A

All right uh does anyone have anything else they want to add in as a discussion topic for today.

A

All right, then, it's a short meeting uh happy new year. Everyone welcome back um hope. You all have a fantastic rest of the week, ramping up again and uh see you all next week have a good one. Bye have a good one.

A