...

...

...

...

BRIDGE:

...

https://zoom

...

-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log 

00:13:10    Thomas KULIK (DT):    #proxy Thomas Kulik for Andreas Geissler (DT)
00:15:45    Priyank:    #proxy Priyank Maheshwari for Toine Siebelink ( CPS - EST )
00:20:00    Dan Xu:    #info Dan Xu, Huawei
00:20:45    Sandra Jackson (LFN):    https://lf-onap.atlassian.net/wiki/x/FUns
00:21:52    Seshu Kumar (SaiSeshu):    #info Seshu, windriver
00:21:54    Byung-Woo Jun:    #info proxy Byung-Woo Jun, Ericsson

...

Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative!   Information as to why .
They are included here as a time stamp cross-reference for the recording only!  The notes above this line and the actual recordings are authoritative. 

00:02:37.000 --> 00:02:56.000
Okay. Actually this needs to be updated. So I'll go back and update this, but remember last week we decided instead of the pound in your name that you would go in, I did drop the link in for the meeting going to edit and highlight yourself as green.

00:02:56.000 --> 00:03:01.000
To show that you are in attendance.

00:03:01.000 --> 00:03:11.000
Same applies the meeting is being recorded. That includes the chat. If you're dialed in and need to unmute yourself to speak, you need to press star 6.

00:03:11.000 --> 00:03:19.000
And then our reminder of our anti-trust policy. If you have any questions about it, you can contact your company's legal.

00:03:19.000 --> 00:03:30.000
Council or if you are a member of the Linux Foundation you can reach out to Andrew of the Grove at the firm Guest M up to Grove LP.

00:03:30.000 --> 00:03:37.000
Also a reminder that Pablo is on. Pto this week. So we don't have a lot on the agenda.

00:03:37.000 --> 00:03:44.000
Just. One or 2 cross organizational updates.

00:03:44.000 --> 00:03:54.000
And a brief. Update from Kevin on the Nexus 3. And then, Bayon and then our.

00:03:54.000 --> 00:04:10.000
Weekly housekeeping. Okay. Is there anything or does anyone have any questions? Regarding the agenda.

00:04:10.000 --> 00:04:14.000
Okay, then we'll jump into it.

00:04:14.000 --> 00:04:26.000
So last week I inform you all that the ONAP. Tagline page was gonna close at the end of end of the day.

00:04:26.000 --> 00:04:35.000
So that has happened. So look out for, We're ballot for the polling for the names that we do have on there sometime today or tomorrow.

00:04:35.000 --> 00:04:47.000
That will go out. And then we did have a TAC meeting yesterday. Mostly covered CII, CI, and CD and security.

00:04:47.000 --> 00:04:57.000
Actually, it was a lot on security. Amy and Olaf provided some updates on security best practices.

00:04:57.000 --> 00:05:05.000
And actually I will put the link. I will drop the link in the in here later if you want to go back and review the notes.

00:05:05.000 --> 00:05:17.000
And then everyone knows that the SPC meeting is on hold until after the special governing board meeting, this month.

00:05:17.000 --> 00:05:23.000
So I will go down to. David, I just wanna ask, I think I know the answer, but.

00:05:23.000 --> 00:05:28.000
No release updates, right?

00:05:28.000 --> 00:05:29.000
Okay.

00:05:29.000 --> 00:05:36.000
That's correct. We're waiting until we resolve, you know, to decisions around the release process.

00:05:36.000 --> 00:05:41.000
No worries, I just didn't wanna pass you by if you actually had something. That she wanted to say.

00:05:41.000 --> 00:05:46.000
Sure. Thank you.

00:05:46.000 --> 00:05:52.000
I didn't get to see if Kevin was in, on the

00:05:52.000 --> 00:05:55.000
I didn't see him.

00:05:55.000 --> 00:06:02.000
Okay. Alright, so we will, and I don't think I see anyone else from another lunch team either.

00:06:02.000 --> 00:06:09.000
So we will skip over the.

00:06:09.000 --> 00:06:15.000
The update for our Kevin right now.

00:06:15.000 --> 00:06:30.000
Okay. And we'll move down to subcommittee updates. Now, do you need to, share your screen or anything?

00:06:30.000 --> 00:06:40.000
Okay.

00:06:40.000 --> 00:06:43.000
You know what? I don't see him on either.

00:06:43.000 --> 00:06:54.000
Okay. Give me a minute, let me just go and check something on the stop sharing for a second.

00:06:54.000 --> 00:07:07.000
Okay.

00:07:07.000 --> 00:07:37.000
Bear with me.

00:07:42.000 --> 00:07:54.000
Sorry, folks that slack me, so that's. Why I folks are not on the. Not updated the meaning link.

00:07:54.000 --> 00:08:18.000
Everywhere where I thought the old meeting was showing. So if I've missed something, please let me know.

00:08:18.000 --> 00:08:48.000
Okay, I'm gonna go back and share.

00:09:03.000 --> 00:09:09.000
Here we are. So my apologies to the, team because you know I realize what happened with you all.

00:09:09.000 --> 00:09:18.000
When I did the new meeting invite. If you were not at it as part of the TSC committee or whatever.

00:09:18.000 --> 00:09:21.000
I need to add you manually and I did not do that. So my apologies for that.

00:09:21.000 --> 00:09:25.000
Oh, that explains it. So I think I've got stale link in the meeting invite. Perfect.

00:09:25.000 --> 00:09:28.000
I'll keep an eye out for an update at some point.

00:09:28.000 --> 00:09:37.000
Yeah, so, but I also updated the meeting links everywhere like on the, groups in groups. Dot I/O.

00:09:37.000 --> 00:09:42.000
So if someplace that I miss, please let me know.

00:09:42.000 --> 00:09:49.000
You know, I think it's just the TSCO Nap TSC meeting invite that, I haven't got, I think.

00:09:49.000 --> 00:09:58.000
Okay, so I'll go back. As everyone who needed to provide an update. Because they weren't here.

00:09:58.000 --> 00:10:10.000
And just a reminder for those who are coming on who outside the village team, last week we decided that we would, highlight yourselves.

00:10:10.000 --> 00:10:17.000
As in attendance, in green, so I said at the pound in your name. Please.

00:10:17.000 --> 00:10:25.000
Go into the. Meeting minutes and let me drop that link again. Just in case.

00:10:25.000 --> 00:10:35.000
Go on to the meeting minutes and, update yourself. As attended. And I'll share it again.

00:10:35.000 --> 00:10:43.000
There we go.

00:10:43.000 --> 00:10:50.000
Alright, so we'll go back to the next 3 update. Is Kevin on now?

00:10:50.000 --> 00:10:53.000
Yeah, I'm here.

00:10:53.000 --> 00:10:58.000
Okay, did you need to share or anything?

00:10:58.000 --> 00:11:08.000
Yeah, actually we got a couple of updates there. So the first one is that if we. Executed the next 3 update last week.

00:11:08.000 --> 00:11:12.000
And the update was basically migrating the volumes. We were having a very big bottom that was not a completely used.

00:11:12.000 --> 00:11:25.000
So we were getting built for a big balloon. That wasn't necessary anymore. It was in the past, but not anymore.

00:11:25.000 --> 00:11:40.000
So. The IT team held me to. Migrate that ball into a smaller one. We had a small issue when we tried to restart Nexus, but we were able to fix it It was working as expected.

00:11:40.000 --> 00:11:56.000
But when that a is more issue happened. He generated a lot of airlocks. That we didn't realize at the moment that we're filling up the smaller disk that we migrated to.

00:11:56.000 --> 00:12:08.000
So I believe on Sunday and Monday this week. We had a couple of a time events for the next 3 system.

00:12:08.000 --> 00:12:18.000
And Matt was able to find out the root cause and the root cause was that a Those are logs that we're filling up the disk.

00:12:18.000 --> 00:12:33.000
So basically the solution was to clean up the logs, make sure log rotation was in place. And now next 3 is up and running again and we haven't seen any issue since Matt fixed the root cause.

00:12:33.000 --> 00:12:36.000
And that's it.

00:12:36.000 --> 00:12:38.000
Alright, thank you, Kevin. Anyone have anyone have any questions?

00:12:38.000 --> 00:12:44.000
No problem.

00:12:44.000 --> 00:12:49.000
Okay, and let me just backtrack a little bit because I realize we have some folks who, just came on.

00:12:49.000 --> 00:12:55.000
I was we don't have a, a large agenda today, a lot to cover, so it's going to be a pretty quick meeting.

00:12:55.000 --> 00:13:04.000
But I do want to remind you that the tagline closed last week, the end of August, and I do want to remind you that the, tagline closed last week, the end of August tenth.

00:13:04.000 --> 00:13:06.000
And so look out for, tagline closed last week, the end of August tenth. And so look out for, your ballots for the poll.

00:13:06.000 --> 00:13:10.000
To come out either today or tomorrow.

00:13:10.000 --> 00:13:20.000
And then I gave a brief tack update. We had attack meeting yesterday, which was, security and CI CD was covered, but mostly.

00:13:20.000 --> 00:13:30.000
Olaf and Amy providing, security best practices and I will drop the link in here to the meeting, yesterday's meeting.

00:13:30.000 --> 00:13:34.000
In case anyone wants to review.

00:13:34.000 --> 00:13:39.000
Okay, jumping back down. Thank you again, Kevin, for the update.

00:13:39.000 --> 00:13:46.000
We'll go to the subcommittee updates they only need to share.

00:13:46.000 --> 00:13:52.000
No, I don't have to share, this week and just to update for, you know, what activity since, Here she approved her own upstream mining, plan, last week.

00:13:52.000 --> 00:13:59.000
So after that. These the subcommittee under that and then OEM team, we defined the roles, what to do for own upstream.

00:13:59.000 --> 00:14:15.000
So we defined it. So 30 ports where we are available. Sometime soon. Thank you.

00:14:15.000 --> 00:14:26.000
Oh wow, that was really quick. Okay. Anyone have anything else before I go on to housekeeping?

00:14:26.000 --> 00:14:29.000
Alright, well, go ahead. Someone say something.

00:14:29.000 --> 00:14:39.000
Yeah, to my CEO, so sorry. I see Semi on the call and, I like to ask him also for his opinion and also the full TSC.

00:14:39.000 --> 00:14:52.000
So because we discussed also with Beyond and Andreas. How to handle, documentation in future releases and, especially also.

00:14:52.000 --> 00:15:03.000
That, one up modules can have their own schedule and that they are not needed to create a branch.

00:15:03.000 --> 00:15:09.000
So the idea was to have some kind of. Marketing release for example Montreal and to combine in this Montreal release.

00:15:09.000 --> 00:15:30.000
All the relevant one app modules. With whatever version they have. So that's not typically that they Not sure, maybe create need to create a branch, maybe we can.

00:15:30.000 --> 00:15:44.000
At the tech or whatever the technically good way could be to, yeah, to, to reach the, this, goal that they do not have to create a branch anymore.

00:15:44.000 --> 00:15:56.000
But we have that we can implement the specific version in in for example in the Montreal and the the Montreal documentation.

00:15:56.000 --> 00:16:01.000
So a little true. What? And I tried a little bit.

00:16:01.000 --> 00:16:10.000
And read also in Richard Docks. Documentation and. But I'm currently quite uncertain how to.

00:16:10.000 --> 00:16:21.000
How to to implement this. If it is, if it makes sense.

00:16:21.000 --> 00:16:32.000
Yeah, Thomas, we can discuss that, in additional detail, OM or documentation, meetings.

00:16:32.000 --> 00:16:33.000
Okay.

00:16:33.000 --> 00:16:39.000
Yeah. So we discussed this at the, OM team this week, with the Thomas Andress and we have some several suggestion.

00:16:39.000 --> 00:16:45.000
So, okay, so we have some difficulty to implement. Okay.

00:16:45.000 --> 00:17:01.000
You know, I think the documentation is possibly the easiest part because the builds are after project already So the project can maintain his documentation on his own.

00:17:01.000 --> 00:17:12.000
As a question, as you mentioned, is more about So global documentation which using big Intel Thankss mappings to all the project.

00:17:12.000 --> 00:17:20.000
So I would say. From a documentation build, doxiny, etc, etc, everything is ready to take couple.

00:17:20.000 --> 00:17:32.000
The question is more about having a rule for maybe a branches for on. Matching the marketing needs.

00:17:32.000 --> 00:17:40.000
But from the documentation builds processes, I think everything is in place is in place. For project decoupling.

00:17:40.000 --> 00:17:54.000
Zen interest to both writings, there's a interest links mapping in Maybe that should be the responsibility of the projects if they know which tag must be in it.

00:17:54.000 --> 00:18:01.000
I don't know. Today it's easier because there is a single attack for every project. So we know already.

00:18:01.000 --> 00:18:07.000
Oh, to write synthetic things mapping, but if there are different numbering in other projects.

00:18:07.000 --> 00:18:18.000
Maybe should not be part of the responsibility of the Nap Doc team but the possibility of the project listed in Zenteslax mapping.

00:18:18.000 --> 00:18:19.000
I don't know.

00:18:19.000 --> 00:18:25.000
Okay, Sandra can I quickly share one page from last week presentations later? Just for first.

00:18:25.000 --> 00:18:28.000
You sure can. You should have co-hosting, guys. Let me stop.

00:18:28.000 --> 00:18:35.000
Yeah, for facilitator. Oops.

00:18:35.000 --> 00:18:52.000
It's a week 6 for your explanation, but let me ask you do you think it is possible to inter things linking also if we do not have a, a dedicated branch of the project.

00:18:52.000 --> 00:18:55.000
So the Not sure.

00:18:55.000 --> 00:19:05.000
But I mean, for my Yes, every mother works. The question is more if we want to be able to rebuild the documentation.

00:19:05.000 --> 00:19:16.000
So thanks for instance having latest in a stable intestines mapping it's wrong by design because as soon as you read the documentation, you won't have the same results because the sub project is in holding mode.

00:19:16.000 --> 00:19:18.000
And.

00:19:18.000 --> 00:19:31.000
So that's an an issue. We share onadmus care. As you can, you can mix and match different different, different tags in, intersx mapping.

00:19:31.000 --> 00:19:36.000
For instance, if someone is using your name and as a numbering, I don't know, you can use anything.

00:19:36.000 --> 00:19:37.000
Hmm.

00:19:37.000 --> 00:19:47.000
But the question is more about the responsibilities at the end. If there is a kind of, Maybe at the end there will be a branch in on.

00:19:47.000 --> 00:19:56.000
Because following the marketing schedules or needs But the contain in it will be tricky. I would suggest not to use latest in in it.

00:19:56.000 --> 00:20:08.000
I'll since it just, I think it's wrong. But, that's something we can delegate to the project.

00:20:08.000 --> 00:20:15.000
Hmm.

00:20:15.000 --> 00:20:16.000
Yeah.

00:20:16.000 --> 00:20:17.000
Okay.

00:20:17.000 --> 00:20:18.000
The no wish, they want to be in some marketing, marketing documentation. But at least from what we are doing today, nothing change, we are maintaining the toxo.

00:20:18.000 --> 00:20:26.000
Dot. SASTINI for everyone for every project. Zukov. Pi etcetera.

00:20:26.000 --> 00:20:40.000
I would say. From a technical to 10 point everything is done to build the project project and to have This distributed, it kind of distributed the documentation.

00:20:40.000 --> 00:20:52.000
Thanks to intersects mapping and. Also, it's a Docker sub projects we have created and maintained.

00:20:52.000 --> 00:20:53.000
Yeah.

00:20:53.000 --> 00:21:08.000
Yeah, so to the documentation will then, for example, create the Montreal branch, what was the name, and then inter things linking to whatever software module 2 dot 0 dot one or whatever the version number then or the branch then could be. Yeah.

00:21:08.000 --> 00:21:09.000
That was.

00:21:09.000 --> 00:21:15.000
Yeah, but but we My opinion would be that it should be up to the PTL, the project to maintain the documentation.

00:21:15.000 --> 00:21:27.000
BY, BASE, of, PASS, Into, A, in, on,pto team, we fail many issues because we know the branch but we are we are waiting for branches.

00:21:27.000 --> 00:21:33.000
So now as the model is. If we project can have his own, releases. I think it's up to the PTL to maintain the file.

00:21:33.000 --> 00:21:43.000
So comfortable, and then there's fax mapping in it. Not to son that took him.

00:21:43.000 --> 00:21:44.000
Yeah.

00:21:44.000 --> 00:21:45.000
Okay, yeah, that's also Okay.

00:21:45.000 --> 00:21:53.000
That will be will be my opinion on abducting will be more a kind of we check that the best holds to build the documentation in all sorts of projects.

00:21:53.000 --> 00:22:08.000
Okay, it's also mean that they that the projects are responsible to maintain the talks. That any file which is located in the dock repository.

00:22:08.000 --> 00:22:09.000
Yeah, yeah, yeah.

00:22:09.000 --> 00:22:13.000
No.

00:22:13.000 --> 00:22:14.000
Okay.

00:22:14.000 --> 00:22:21.000
Maybe not the talks that he's covered by, yes, the COVID. PI, why, the, the, in terms of my being is defined because on app docker is not the release manager of the project so we don't know which project you which numbers it's a

00:22:21.000 --> 00:22:22.000
Okay, makes sense. Thank you.

00:22:22.000 --> 00:22:31.000
Yeah, that's the, yeah, that conform to what our thinking. So this one, you know, 100 by project and this is kind of master marking.

00:22:31.000 --> 00:22:40.000
So that link to our project specific. So we'll see. So, this is what we are thinking about it, but how to do it that we're gonna talk.

00:22:40.000 --> 00:22:49.000
Additionally, now let me stop sharing. So. Okay, good, good information. We're gonna just Thomas, we're gonna discuss further.

00:22:49.000 --> 00:22:52.000
And we don't interested in. Next time, okay.

00:22:52.000 --> 00:22:57.000
Hmm.

00:22:57.000 --> 00:23:04.000
Okay, thank you. Thank you, Thomas and Cedric, and Cedric, welcome back.

00:23:04.000 --> 00:23:06.000
Thank you.

00:23:06.000 --> 00:23:15.000
Any other questions or comments before? We get ready to close out.

00:23:15.000 --> 00:23:24.000
Okay, so some reminders here. We have the one summit regional today, Spain that's happening in September, September eighteenth.

00:23:24.000 --> 00:23:33.000
And the regional. Day for China is September 20 sixth. And then India, the information for that will be forthcoming.

00:23:33.000 --> 00:23:38.000
As for the other 2 as well, we just have the dates. But information is forthcoming.

00:23:38.000 --> 00:23:46.000
And then the reminder about the face to face in Budapest. November thirteenth through November seventeenth.

00:23:46.000 --> 00:23:54.000
The topics page is open. So please get your topic proposals in. And if you have not already.

00:23:54.000 --> 00:24:05.000
Please apply for your visa so that it's not a delay or, hold up for you attending in person.

00:24:05.000 --> 00:24:08.000
Any other closing remarks before we go?

00:24:08.000 --> 00:24:15.000
Just a quick question on the Spain event. I think it's co-located with, Open Source Summit.

00:24:15.000 --> 00:24:23.000
Do we, Is it is it free or not or do you have to go to the to pay for the wall event and not only for the special day.

00:24:23.000 --> 00:24:32.000
You. Exactly. It requires a registration for the entire event.

00:24:32.000 --> 00:24:37.000
Okay, same as a sonic I think so Nick is also part of this this one summit So once I meet there Okay.

00:24:37.000 --> 00:24:44.000
All that. Would be the same thing.

00:24:44.000 --> 00:24:45.000
Okay.

00:24:45.000 --> 00:24:50.000
Every day it's been for India. By the way, I see India still wanted to confirm the date.

00:24:50.000 --> 00:24:51.000
Okay.

00:24:51.000 --> 00:25:03.000
No, we have a date. We have a tentative date. We are waiting on official confirmation or the event.

00:25:03.000 --> 00:25:08.000
Also location, I mean in India do we have a confirmation on location or do we have to wait for that?

00:25:08.000 --> 00:25:10.000
It will be in Bangalore. Okay.

00:25:10.000 --> 00:25:16.000
Thank you.

00:25:16.000 --> 00:25:17.000
Okay.

00:25:17.000 --> 00:25:20.000
So hope to see you.

00:25:20.000 --> 00:25:22.000
I'm sorry, didn't hear this issue. What did you say?

00:25:22.000 --> 00:25:24.000
I'm saying hope to see you people there.

00:25:24.000 --> 00:25:25.000
Alright, yes.

00:25:25.000 --> 00:25:30.000
So these are, yeah, these are regional events. They are not, major events.

00:25:30.000 --> 00:25:38.000
So, I prefer I will not do travel.

00:25:38.000 --> 00:25:40.000
Okay.

00:25:40.000 --> 00:25:42.000
Sorry.

00:25:42.000 --> 00:25:47.000
Yeah, sorry to hear that.

00:25:47.000 --> 00:25:48.000
Alright.

00:25:48.000 --> 00:25:58.000
But, it's not, it's not really, a kind of meetup meetup day.

00:25:58.000 --> 00:25:59.000
And walking.

00:25:59.000 --> 00:26:04.000
I mean if you have to register to a full Linux submit event, open source submit events. I think you can change a little bit, original scope, which was introduced.

00:26:04.000 --> 00:26:21.000
Do you play? For the co-located regional days. They are Have the events. No, those are set up to.

00:26:21.000 --> 00:26:34.000
Trying and draw and New participants. That wouldn't generally attend one of our own events. Which is why we're now, located for the event in India.

00:26:34.000 --> 00:26:40.000
It would be a standalone event that will be hosted by one of our member companies.

00:26:40.000 --> 00:26:45.000
And there should not be any charge for that as far as. Yeah.

00:26:45.000 --> 00:26:51.000
What about the topic? Song? I mean, what about the, the event topics or even discussion topics on that day?

00:26:51.000 --> 00:26:59.000
. Do you only publish CFP for that

00:26:59.000 --> 00:27:04.000
Okay.

00:27:04.000 --> 00:27:05.000
Okay, not just India. I mean, they need it because I see the dates are very moving, right?

00:27:05.000 --> 00:27:07.000
So we're waiting on confirmation, sir. I don't have any information for that. L Okay, please.

00:27:07.000 --> 00:27:15.000
For, the, the many, just paying in China, it's just one month. That's true.

00:27:15.000 --> 00:27:33.000
The topics for the event in Spain are the finalized at the moment. And, China.

00:27:33.000 --> 00:27:38.000
So CFP for India is actually opening on that question.

00:27:38.000 --> 00:27:43.000
Good. I'm sorry, what was that?

00:27:43.000 --> 00:27:49.000
I'm sincerely for China. India has had to open in that case, right?

00:27:49.000 --> 00:27:59.000
The calls for people.

00:27:59.000 --> 00:28:00.000
.

00:28:00.000 --> 00:28:08.000
There is Because we form confirmation.

00:28:08.000 --> 00:28:13.000
I didn't hear you, sorry, can you can you just repeat what you' and ask?

00:28:13.000 --> 00:28:23.000
So for That event, it's basically look at it as we save the date.

00:28:23.000 --> 00:28:44.000
Don't have any more specifics than that. Terms of CFP or anything like that. Yeah.

00:28:44.000 --> 00:28:49.000
Okay, and I found another. Link. So I dropped that in for, the China one.

00:28:49.000 --> 00:28:55.000
I don't, I haven't visited the page yet, so I don't think that it gives you a lot of information, but.

00:28:55.000 --> 00:29:05.000
Just in case anyone have any questions, but the other events. Like Kenny said, the information is forthcoming.

00:29:05.000 --> 00:29:10.000
Any other questions?

00:29:10.000 --> 00:29:22.000
All right, well, if there's nothing else, you all get back a lot of time today.

00:29:22.000 --> 00:29:23.000
Thank you.

00:29:23.000 --> 00:29:24.000
Okay.

00:29:24.000 --> 00:29:25.000
Thanks.

00:29:25.000 --> 00:29:26.000
So, use it wisely and we'll see you same place, time next week. Oh, a reminder if you do have the old.

00:29:26.000 --> 00:29:34.000
Meeting invite on your calendar, get rid of that. You should have received the new invite last week and it's You need the link.

00:29:34.000 --> 00:29:42.000
Please let me know if you didn't receive it. Paying me and I will make sure that you get it.

00:29:42.000 --> 00:29:45.000
Thank you all. Have a good one.

00:29:45.000 --> 00:29:46.000
Thank you.

00:29:46.000 --> 00:29:47.000
You.

00:29:47.000 --> 00:29:49.000
Thank you.

00:29:49.000 --> 00:29:59.000
Thank you, bye.