TSC 2021-09-02
BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09
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.
Attended | Proxy (w/ @name) | Gov. Holiday | Did Not Attend |
---|
AMDOCS | IBM | |||
DT | Lingli Deng proxy Yuanhong Deng | China Mobile | ||
WindRiver | Turk Telecom | |||
cl664y@att.com - proxy: Amy Zwarico | AT&T | Reliance Jio | ||
Ericsson | Bell Canada | |||
Vodafone | Samsung | |||
China Telecom | Huawei | |||
Orange | Intel | |||
Verizon | Nokia |
Agenda Items | Presented By | Presos/Notes/Links/ |
---|---|---|
Release Status | Istanbul Release
Jakarta
Honolulu Maintenance
| |
RelEng/Infrastructure |
| |
PTL Updates(Integration, AAI, Policy) | Integration PTL Michał Jagiełło #AGREED the TSC confirms Michal Jagiello as the new Integration PTL Congratulations to AAI - Robby Maharajh, our new AAI Committer. Thank you Steve Blimkie for all his contributions (AAI Committer) Thank you Jim Hahn for his leadership, serving as Policy PTL | |
Subcommittee UpdatesArch, Ctrl-Loop, Lab, Modeling, Seccom, Requirements | ||
LFN Cross-Organization UpdatesMAC, SPC, TAC, EUAG, LFN Board | Kenny Paul |
|
TCC / ONAP Liaison Updates | Magnus Buhrgard (Unlicensed) | AN Multi-SDO initiative from TM Forum I have participated in exploratory meetings, on behalf of ONAP, regarding the AN Multi-SDO initiative from TM Forum. #AGREED the TSC wishes to pursue this agreement with TM Forum
|
Task Force Updates | ||
TSC Activities and Deadlines | Sent for review on https://lists.onap.org/g/onap-tsc/message/8039
#AGREED TSC approves the Technical Community Document in the form attached hereto as Technical Community Document v2.0.pdf with the above agreed upon change to 4.2.1.6.2 as being hereby confirmed, approved, and adopted? | |
Upcoming Events & Housekeeping | ONAP Community Awards: Honolulu Release
PTL meeting on Sept 6 is canceled due to the Labor Day holiday in the U.S.
|
Zoom Chat Log
07:03:16 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
07:03:33 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
07:03:35 From Martin Vezeau (Bell Canada) to Everyone:
#info Martin Vezeau, Bell Canada
07:03:46 From Amy Zwarico to Everyone:
#info Amy Zwarico, AT&T - proxy for Catherine Lefevre
07:03:59 From Magnus Buhrgard (Ericsson) to Everyone:
#info proxy Magnus Buhrgard (Ericsson)
07:04:28 From Shashikanth v.h. to Everyone:
#info proxy Seshu, Huawei
07:04:30 From Magnus Buhrgard (Ericsson) to Everyone:
Proxy for Ciaran during the first part of the meeting
07:06:57 From Catherine Lefevre to Everyone:
Dear All, Amy Zwarico will be the AT&T representative for today
07:09:01 From Yuanhong Deng (China Mobile) to Everyone:
#info proxy Yuanhong Deng, China Mobile
07:17:03 From Kenny PAUL (LFN) to Everyone:
#vote does the TSC approve the Istanbul release as passing the M3 milestone with the condition that the following items are to be closed by M4 on 16 Sep 2021 : CCSDK-3355 DMAAP-1633 MSB-608 MULTICLOUD-1368 INT-1937 INT-1935 SDNC-1578 SO-3683 SO-3687 USECASEUI-591 VFC-1874 VNFSDK-791
07:17:13 From bin.yang@windriver.com to Everyone:
#vote +1
07:17:13 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:17:16 From Jason Hunt to Everyone:
#vote +1
07:17:18 From Srini Addepalli (Intel) to Everyone:
#vote +1
07:17:21 From Martin Vezeau (Bell Canada) to Everyone:
#vote +1
07:17:21 From Amy Zwarico to Everyone:
#vote +1
07:17:21 From Ranny HAIBY (Samsung) to Everyone:
#vote +1
07:17:22 From Magnus Buhrgard (Ericsson) to Everyone:
#vote +1
07:17:22 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:17:23 From Timo Perala (Nokia) to Everyone:
#vote +1
07:17:24 From Eric Debeau to Everyone:
#vote +1
07:17:26 From Yuanhong Deng (China Mobile) to Everyone:
#vote + 1
07:17:26 From Alla Goldner to Everyone:
#vote +1
07:17:46 From Kenny PAUL (LFN) to Everyone:
#endvote
07:18:34 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the Istanbul release as passing the M3 milestone with the condition that the following items are to be closed by M4 on 16 Sep 2021 : CCSDK-3355 DMAAP-1633 MSB-608 MULTICLOUD-1368 INT-1937 INT-1935 SDNC-1578 SO-3683 SO-3687 USECASEUI-591 VFC-1874 VNFSDK-791
07:33:31 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC confirms Michal Jagiello as the new Integration PTL
07:42:46 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC wishes to pursue this agreement with TM Forum
07:46:20 From Ciaran Johnston (Ericsson) to Everyone:
#info Ciaran Johnston, Ericsson
07:46:28 From Ciaran Johnston (Ericsson) to Everyone:
Taking over from Magnus, thanks
07:52:14 From Kenny PAUL (LFN) to Everyone:
#vote Does the TSC approve the Technical Community Document in the form attached hereto as Technical Community Document v2.0.pdf with the above agreed upon change to 4.2.1.6.2 as being hereby confirmed, approved, and adopted?
07:52:19 From Eric Debeau to Everyone:
#vote +1
07:52:21 From bin.yang@windriver.com to Everyone:
#vote +1
07:52:21 From Ranny HAIBY (Samsung) to Everyone:
#vote +1
07:52:21 From Jason Hunt to Everyone:
#vote +1
07:52:22 From Timo Perala (Nokia) to Everyone:
#vote +1
07:52:23 From Martin Vezeau (Bell Canada) to Everyone:
#vote +1
07:52:28 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:52:32 From Ciaran Johnston (Ericsson) to Everyone:
#vote +1
07:52:34 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:52:35 From Amy Zwarico to Everyone:
#vote +1
07:53:05 From Kenny PAUL (LFN) to Everyone:
#endvote
07:55:39 From Kenny PAUL (LFN) to Everyone:
#AGREED TSC approves the Technical Community Document in the form attached hereto as Technical Community Document v2.0.pdf with the above agreed upon change to 4.2.1.6.2 as being hereby confirmed, approved, and adopted?
07:56:07 From Yuanhong Deng (China Mobile) to Everyone:
#vote +1
07:56:13 From Kenny PAUL (LFN) to Everyone:
Honolulu awards https://lf-onap.atlassian.net/wiki/x/3X37
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.
07:06:00 Transcript just started.
07:06:03 Here we go.
07:06:14 reason it won't advance the slides.
07:06:18 So I'll just scroll
07:06:21 member you're muted star six if you're on a phone keep yourself muted if you send me a private chat message, it will become part of the public record and oriented trust policy
07:06:35 And our anti trust policy will find this link from both the lF and all the project websites as policies important we've got multiple companies, including potential industry competitors participating in these meetings.
07:06:46 Please review. If you have any questions please contact your company's legal counsel, members of the lF may also contact Andrew up to grow the firm up the grove LLP, which provides legal counsel to the Linux Foundation.
07:07:05 And we'll work on fixing the colors here.
07:07:12 figure that out.
07:07:23 Good morning, Kenny I don't know if you can hear me here is getting. I can't hear you Catherine you're on vacation. No, that's correct but I was so I want to confirm that Amy, will be the at&t representative for today.
07:07:32 The reason why is because I wanted just to discuss about the TC two those two because I had so that the changes were related to the TASC membership.
07:07:50 And I want to apologize because I realized that the changes were broader to that.
07:07:55 And therefore I send the notes with my comments with the bubbles why I joined the call knows because if the TLC agree for the section related to the DSD member, an election.
07:08:11 I would suggest that keep going, we can fix the other section later.
07:08:16 I just wanted to be sure, I do not do apologize. What was planned today, because the focus was really on the membership election and all around that. And my comments are add to the order section that I've seen.
07:08:34 And then a little bit so that's, that's why I decided to join because my email, my job is the mindset of some key members and that was not the intent.
07:08:48 Let's try some clear.
07:08:52 If I come to furthermore the people.
07:08:59 Hi Joe Do you know your audio is still there. Yeah.
07:09:08 I was just joining two minutes to see if there's any question otherwise.
07:09:13 I wanted to clarify my email from this morning.
07:09:19 Unfortunately, my apologies I had not seen
07:09:25 your email yet so I'm trying to say it looks.
07:09:30 So just to be clear, Catherine the potential changes to the life cycle membership at hand. And those separately that you had a specific moment.
07:09:49 You've got you got the design because honestly I, I know the focus was really on what we have been discussing and on the TASC websites, there was a link to the whip.
07:09:53 Right. And, from my perspective, and Amy will will also confirm, it's aligned, that the new document shared by by Kenny is aligned with what has been discussed.
07:10:08 But when I review because I see other aided.
07:10:12 I also provide comments so, but these are new, you got my point I wanted to really to be sure that I was not you're prioritizing the discussion of today so that's why, because I feel guilty.
07:10:25 I joined this goal to make sure that the intention is keep going, accepted. If you all decide differently, but at one point, of course, we need to clean up the auto section to be aligned with with how we have evolved over the past year.
07:10:42 Is it okay Jason and team.
07:10:47 So, so Catherine to to restate what I think I heard you saying, is the comments that you have made in your email today, point out other changes that need to be made, but they don't need to be made in the context of today's vote is that, yeah.
07:11:12 Okay, so hot, but yeah I just reacted because I was not expecting the changes in the document as audio sections so so that so that's why Suki are provide collectively my commands.
07:11:24 But you are right, good.
07:11:26 Yeah, there, there were a number of things that that I did see that we probably needed to fix or a couple of typos I fixed but some of the other changes,
07:11:43 like the ones that you are highlighting.
07:11:49 That was my exact thought is, Let's, let's attack that as a, as a subsequent update, rather than mix that in with with what we're trying to do with the TASC changes.
07:12:07 So both skinny and good on you got it. And again, my apologize, I was really concerned to create confusion so that's why I decided to join to explain what I had in mind when I wrote this email and Amy also is aware of that.
07:12:26 But at least if there was any question, I wanted to clear that up. So, really sorry.
07:12:31 You find unity identical fusion but at least for what has to be accomplished today. I think we are on the same page. All right.
07:12:51 I'm sorry that you had to join on your vacation.
07:12:45 It's okay that I should have provided my feedback before.
07:12:50 But the cool things happen and could not do as I want it.
07:12:54 So, I, I did it before the call and.
07:13:00 No problem. So, I let you enjoy the TC. Thank you for giving me the last few minutes to explain my, my intent.
07:13:11 And I hope everything will go well, and I will see a great news. When I will be back. Thank you so much everybody. Have a nice day.
07:13:21 Thank you, Catherine.
07:13:33 Okay.
07:13:38 So why don't we go ahead and
07:13:45 get the.
07:13:52 David, your turn.
07:13:55 Released, that's the word I'm looking for, I'm reading it and I can't say it release.
07:14:00 Okay. All right, thanks Kenny.
07:14:11 Alright, so just refresh everyone's memory.
07:14:15 Last week we reviewed the status of em three and determined that we hadn't made sufficient progress.
07:14:28 And so the decision was made to slip the schedule one week.
07:14:35 And
07:14:39 so that, that made the new date for am three, as it today. September 2.
07:14:47 And so if we look at the milestone status for him three.
07:14:55 You can see that we've made a lot of progress.
07:14:58 So we have about almost 90% of the issues are closed.
07:15:07 The remaining issues are related to some, some tough.
07:15:15 Important Nigeria shoes with particular projects that you know have higher highest priority, and.
07:15:27 And I know that those teams are are actively working on those issues and so what I would like to propose to the TASC.
07:15:37 The, given that we are nearly 90%.
07:15:46 And I don't think that there's anything to be gained by delaying him three and any further. So what I'd like to suggest is that basically we we collapse these remaining issues into em for.
07:16:03 And so I'm recommending that the PSC approve em three on the condition that the the remaining open items, be closed by M for on the 16th of September, and there's a list of the, of the open issues.
07:16:25 Is anyone have any questions about that concerns.
07:16:36 All right, I'm not hearing anything.
07:16:40 Are we ready to go ahead and move to a vote on that proposal. Does anyone want to discuss it any further.
07:16:50 It's fairly clear.
07:16:56 Okay, I'll go ahead and drop that in as a vote.
07:17:07 Vote is in the chat.
07:17:11 We respond with a plus one, zero or minus one.
07:17:30 Thank you and another 10 seconds.
07:17:40 Whoa, what was that
07:17:45 that was bad typing on my part.
07:17:47 Okay.
07:17:49 It is agreed.
07:17:55 All right, thanks Kenny.
07:17:57 Thank you, to see members.
07:18:00 The last thing that I wanted to mention is, as I said to him for is coming up on 16 sep tember.
07:18:10 We did not move any of the other milestones when we slip them for a.
07:18:19 So, we have and for coming up, but two weeks from today and recall that's when we want to get our containers delivered.
07:18:29 I did publish the milestone tasks for em for last Friday. And so those, those are available. And note that, unlike in three we do have
07:18:49 milestone tasks for our requirements, owners. I sent email, an email out to the requirement owners they also asked Allah to review those in the requirements subcommittee meeting.
07:19:08 Allah did the word Were there any questions that came up or anything I should know about from that discussion.
07:19:23 No basically so be briefly look into that and also I've sent them again through the requirements subcommittee list and asked all the requirements owners to pay attention to them for that last more additional questions were raised.
07:19:31 Okay, all right.
07:19:33 In the 15 people on the call so that was quite a good attendance for this.
07:19:44 So, okay. Terrific.
07:19:47 Just Just a moment. Just one more thing. During the requirements subcommittee meeting, actually I was asked when we are supposed to start looking into Chicago requirements and also you know I was asked specifically by one representative but also you know
07:20:03 I need to understand this well you know for requirements have committed to start reviewing those, and that typically starts has been no before m zero and before dawn.
07:20:17 So just some rough date when they probably should start it would be good for us to start reviewing those so I would really like to get some, you know, hint, or systems is that, this, this is really needed.
07:20:29 Yeah, I don't see any reason why you couldn't start reviewing those. Now you know the way. Chris stuff has explained the new processes that is that it's continuous.
07:20:46 You know submitting and reviewing requirements, and then, you know, it would be a requirement subcommittee determination then to figure out which
07:20:59 release they would be assigned to, but I don't see any reason someone, you know, correct me if I'm wrong here but I don't see any reason why you couldn't start revealing Jakarta requirements.
07:21:13 Now, that's fine thank you but one more question about that. When do you think we will start discussing check out the timelines I think it will help companies to kind of, you know, start to get prepared with requirements, it is not that someone is has
07:21:28 already prepared material, people are kind of, you know, waiting to understand what and check out the timelines.
07:21:36 Yeah.
07:21:38 Yeah.
07:21:39 So I well all you know I'll, I'll confirm this with with Catherine as she gets back, but I imagine that she would like to see a timeline proposal.
07:22:01 Probably like an October timeframe, and give the TASC some time to review that and and approve it.
07:22:09 And I imagine that would place, probably, m zero would be probably somewhere around late November, something like that.
07:22:23 Okay, so that basically gives us quite a lot of times.
07:22:28 I think so, yeah, yeah.
07:22:29 Thank you. this is what I wanted to thank you.
07:22:35 Okay, Jamie. If I, if I may say so, my personal opinion is that we should have the schedule for Jakarta, at least the proposal for the schedule presented to this TASC as soon as possible.
07:22:50 Because as the work is supposed to be continues. So, as soon as we freeze requirements for Istanbul, then we should already give people the opportunity to work on your character requirements.
07:23:01 And, you know, they should have at least some vision how that release is going to look like. And the reason for that is that we want to have the development and working on the requirements as much in parallel, as possible and give people as much time
07:23:17 to work on those as much as possible.
07:23:22 Because if we hold that, and then we kind of surprise people with the schedule and surprise people for example of some tight deadlines, we may get, we may have some pushback that they have not enough time to work on that, that there's too much stress
07:23:38 when we are finishing their release, and people are supposed to work on the requirements so the window that we should give to people should be as big as possible.
07:23:49 Okay. All right. Fair enough.
07:23:52 So I will.
07:23:55 I'd like to have a chance to review that with with Catherine they get her input. She's out right now so
07:24:06 what I propose is that either two weeks from today or three weeks from today, I can present a proposed schedule to the TASC.
07:24:27 So that would put it toward toward the end of sep tember sounds does that work. Okay. All right. I will, I will get busy with that, thank you for making the point.
07:24:38 Okay, any other, I wasn't really expecting to get into a discussion about Jakarta today, but that's all right.
07:24:46 Any other questions about the
07:24:53 either the assemble or the Jakarta release.
07:25:02 All right. Thank you.
07:25:10 Okay. Anything else release related from anyone.
07:25:20 Okay.
07:25:24 Is there anything about the maintenance release I mean we are still waiting I think for the patch from from his own CDs on the on the maintenance release right for have a little.
07:25:35 Yeah, yeah, I wasn't going to bring up the maintenance release, okay because we haven't gotten to a point where we even got a garden you know daily test feedback.
07:25:50 So I think, as I recall, Morgan's waiting for om to wrap up there, changes for for the maintenance release and then he was going to initiate daily testing, and I don't believe that has began yet.
07:26:13 It's not done because I think, then was still asking us all whether they can cherry pick the, the so patch, which contains two CDs change and the, the changes of the new versions of GSO to Honolulu I think that was in the one and this was not clarified
07:26:33 yet therefore it is not. It is not started any, let's say, a web changed yet so and therefore Of course no test could be taught. Right, It's like that have.
07:26:43 Yeah, okay. Yeah.
07:26:46 Yeah. Daddy what we as a team are waiting for. OK, so the party's marching the master but not yet.
07:26:57 Exactly. Yeah.
07:27:14 Wait, I'm also asking because I wanted to prepare at least the maintenance release notes for next week already so that it's containing and I hope to then Okay, I see you already in the picture that it's hopefully that we get this patch of course in maintenance
07:27:16 because we all as DT are also waiting for that.
07:27:20 Yeah.
07:27:22 dan Do you have any updates for us on.
07:27:27 Yeah, there's any part of it is ready. The doctor is ready. The only thing I need to know what our solution goes with that.
07:27:33 Yeah.
07:27:35 So let's let's we know that we can push the changes though I'm done.
07:27:41 I see you, I saw your comment in the in your in your JIRA ticket so and I think you're waiting for confirmation right.
07:27:51 Yep.
07:27:53 And where does that come from.
07:27:57 I was checking with Joseph, who's kind of running point on how they're responded yet, but I'll get him on
07:28:07 here.
07:28:08 Yeah.
07:28:09 Does anyone work with Joseph that can tap him on the shoulder and say we need to move this forward.
07:28:26 Yeah, I mean I've been, I've been talking counter
07:28:35 Sure.
07:28:40 So, unless there are more questions related to release, I think I've done.
07:28:49 Okay.
07:28:54 Come back to
07:28:58 varying varying is carrying
07:29:04 any anything for real inch
07:29:11 from my side, I'm I son Christopher, the invitation for the good love for good luck slideshow now.
07:29:22 So, let me know if you receive the crystal, and I believe also bank was trying to reach out to you regarding that.
07:29:30 Yep, I got the invitation I spoke with bank today. Okay. Excellent. Thank you.
07:29:36 Thank you. Okay, so that's tracking.
07:29:41 Yes.
07:29:41 Tracking. Okay.
07:29:51 Okay, um,
07:29:57 want to touch your on PTO updates.
07:30:03 My cowl has not nominated for the integration ptl position.
07:30:13 There was no one that
07:30:19 went up against him. And I'm sorry folks, not clear to me because I'm behind, whether there was an actual vote, or
07:30:34 what took place there.
07:30:43 Can you, I believe there was no vote but because the hall was the only candidate position.
07:30:54 Do we need a former football that we had talked about, okay, thank you for the clarification I thought that was the case, we had talked about
07:31:09 putting in a
07:31:13 aspect where if there are no.
07:31:17 If there are no challengers to a.
07:31:25 One of the leadership positions within oh now that it be accepted that I don't think that when I went back and I looked through previous decisions and such, I don't see that that was ever.
07:31:44 That was ever made a decision or a policy.
07:31:48 Unless I, I missed it. So I guess the question is, does the TSP want to confirm my kill as the ppl.
07:32:20 tokenized.
07:32:20 You accepted to to present. So, I don't see any programmed.
07:32:26 Is there anyone from the TLC that
07:32:31 disagrees with the confirmation.
07:32:38 Ok, I will mark that as agreed.
07:32:49 Mike, I don't know if you are on the call, but if so congratulations.
07:32:55 And I will go through and get you set up.
07:33:00 And we just sent him congratulations from you, our internal chat.
07:33:25 No, I'm sorry I'm having
07:33:32 more problems this morning typing than usual so agreements in the chat.
07:33:40 That is fabulous.
07:33:44 I'll drop that in there.
07:33:56 Okay. Um, so, we've got Robbie who was a new AI committed Congratulations.
07:34:07 Thank you Steve for everything you've done and Jim, thank you for all the work you did is the policy ptl Liam's in that role now so thank you very much.
07:34:22 My pleasure.
07:34:31 Okay, so looking at the time.
07:34:41 I have attached here.
07:34:44 The
07:34:47 slides at the governing board wants there's the PDF for it.
07:34:52 And then the actual PowerPoint is there.
07:34:58 And there's also the aspect of the 2022 budget planning, if everyone's okay with that, rather than taking the time here right now, because we got so much other stuff to cover.
07:35:13 I can take that offline with you is that ok.
07:35:21 We will do that.
07:35:38 on.
07:35:54 Okay, I'm Magnus you want to.
07:36:02 I'll stop sharing your presentation.
07:36:06 Thanks, Kenny, actually you can help me maybe with, with the show, keep sharing. If you, If you don't mind.
07:36:18 And so you can go up a bit.
07:36:22 Okay, so this is about the autonomous network multi sto initiative from Team forum.
07:36:32 So, I have participated in the exploratory meetings on behalf of own app as a as a technical coordinator.
07:36:42 Regarding this initiative.
07:36:44 And so far it's been mostly sort of discuss discussions and, and not not as stringent, but now there is a concrete proposal to set up a meeting between legal representatives of the participants to discuss the copyright licensing approach for a jointly
07:37:02 developed document within under the umbrella of the in both you guys do initiative.
07:37:09 So I think it would be beneficial for grown up to be part of this. We are the only open source
07:37:18 project that are in there otherwise it's just us. I think it could help us to promote own up and, and influence the contents to align with our architecture.
07:37:29 I've put down the material around the letter of intent that has been sent out by the forum. You can click on that.
07:37:40 And you can see that it's supposed to be around the autonomous networks, and you can go to the next slide.
07:37:51 So the the sort of the challenge here with with the autonomous networks is outlined. I think we would all agree on that with the siloed solutions the fragmentation like event and, and the lack of agreed metrics to measure by frame, the outcome of tunnel
07:38:12 systems, and the lack of efficient, effective industry ecosystem and adoption and efficiency, and we can go to the next slide.
07:38:27 I will go through this rather briefly and you can read on up on this if you're interested.
07:38:33 It's a standardization challenge, of course, also have to do this and I mean our input is that you cannot solve this just by standardization, you need to have open source initiatives as well.
07:38:49 They think it is important for us to be to to to emphasize that.
07:38:59 The next slide
07:38:59 is the opportunity. And it's pointed out there that the ways of working here would be information sharing covering basic concepts of terminology alignment alignment division common business targets, high level objectives and recommendations for standards
07:39:17 and best practice to extract benefits from multiple skill, collaboration, and Next slide please.
07:39:28 And again, since I'm conscious of time I go through this in, in any day detail.
07:39:35 And then there is a call for action building consensus in depth analysis and promote industry consensus and collaboration.
07:39:44 And it should be open to all parties, of course, and the last slide is pointing out the, the organization representatives of organizations that has been in this exploratory meetings, so far.
07:40:01 And then we can go back to look at the liaison statement.
07:40:07 And this is calling for a meeting on the 13th of September.
07:40:15 To for legal representatives for for IPR discussions. So my proposal to the TC is that that you sort of proof that we go ahead and take part, or I take part in in the continues meetings, and I get help in getting your legal representative for whom to
07:40:41 participate in this meeting.
07:40:49 So that's basically what I'm asking for.
07:40:59 If the TLC thinks this is a good approach, I will
07:41:09 bump this up to our pit.
07:41:13 So that he can
07:41:17 do whatever would need to be done in in coordinating some of the legal aspects of this.
07:41:26 This is something that the PST would like to pursue.
07:41:35 I think it looks like a good idea.
07:41:37 Since we already have somebody that's willing to do the work and participate. I think that's great, that's that's always a big help.
07:41:49 And the other feedback.
07:41:56 I agree.
07:42:05 So I'm gonna put
07:42:12 agreed the TLC wishes to pursue
07:42:22 this agreement
07:42:27 with tm forum.
07:42:45 dogs objecting
07:42:50 to TC member.
07:42:53 Otherwise we can get this free going yet.
07:42:56 Not yet, but maybe after we do that will be
07:43:02 just Magnus, Just a question. So, we write the content to
07:43:10 use these
07:43:13 Will you be the
07:43:21 contact guide to describes it on App content or will you reuse. What is existing today under the cover I will, I will try to reuse some and take sort of artifacts from the architecture and what has been done, and I will also reach out to see if I can
07:43:30 get help when I know what what subjects are up.
07:43:35 Okay, great.
07:43:38 Okay. Thanks.
07:43:47 Okay.
07:43:54 Okay, moving on then to TLC two dot o
07:44:05 floor is open.
07:44:09 Questions, comments, thoughts.
07:44:13 I have two minor, but one minor comment one minor observation.
07:44:19 So, first of all thank you Kenny from other work on this.
07:44:24 It's, you know it's like a lawyer being a lawyer right and the sort of thing so thank you.
07:44:30 So one observation, I just want to make sure everybody's clear on it you know we've got the,
07:44:34 the language in there around.
07:44:38 Sure I get this right around contributions contributions.
07:44:47 Community Leadership.
07:44:50 Right.
07:44:50 And I think that's great, and I think it's worded well you know just the the observation is that there's no enforcement of that other than a, you know, if you don't think you're going to be able to do this.
07:45:03 Don't run. And I think that's fine I'm just pointing that out as an observation.
07:45:09 And then my other comment is a very minor one in that is on proxies and it's the languages around, informing the TSP about proxies via the email list and my only recommendation was going to be to add language or via the proxy wiki page, just so we don't
07:45:31 have to clog up the TASC mailing list with proxy announcements.
07:45:43 Why can't I do search on this page.
07:45:47 And let me see if I can type.
07:46:08 We're not to that to that one that too I don't know which I'm you know the trash. Yeah. Forgot to.
07:46:08 That's the attendance
07:46:12 for that to that 16242162, so that line you know maybe adding something like, or the email that the mailing list or via an update to the proxy wiki page.
07:46:38 If people are okay with that. That's what I've always done and just to feel like spamming the whole Tsu best proxy,
07:46:50 or, or do we make the.
07:46:59 Well, I think leaving both, because there are situations where somebody may not be able to get in and edit but they can send an email from there from from their phone.
07:47:12 So I believe an edit.
07:47:17 Okay so,
07:47:22 So there was no enforcement.
07:47:30 Regarding the expectations or community leadership or.
07:47:49 And is there any disagreement with
07:47:56 updating that section
07:48:06 with the following language, or the, the key SC
07:48:19 proxy web page
07:48:32 to the wiki page.
07:48:42 Okay so that
07:48:47 there would be a proposed change
07:48:52 to the document as
07:48:58 written.
07:49:02 Anyone disagree with that recommendation.
07:49:11 Okay well mark that isn't as as agreed.
07:49:31 Okay, so that's one.
07:49:36 Okay.
07:49:37 Other comments.
07:49:41 Can Have you got Catherine's comments correct.
07:49:46 She sent out an email, and I know she brought it up earlier in the meeting.
07:49:54 Let me look at when her email was sent.
07:49:57 She sent it this morning.
07:50:01 She had some comments on section three dot three dot three, up to go to that.
07:50:11 And let me put in the chat.
07:50:14 I believe that she.
07:50:20 I believe she added the four reviews to the project life cycle.
07:50:24 Or actually, she said, shouldn't it be right now it says the state winners in order.
07:50:29 Sorry I thought that's what she said at the beginning of the call is that, yeah, we we aren't going to be touching this. Okay, great. All right, that's perfect.
07:50:37 Thank you so much. Yeah changes needed but not in the context of today's work. Okay, good. I just wanted to make double check. Thank you.
07:51:04 Okay, any other.
07:51:12 Any other changes.
07:51:20 Okay, so here's the vote that I'm putting forward.
07:51:23 Does the TSP approve the technical community document in the form attached here to as technical community document the to Dotto PDF with the above agreed upon change.
07:51:39 I should probably put the section
07:51:50 two four.to dot one dot six start to
07:51:56 as being here by
07:52:01 proved confirmed and adopted.
07:52:03 I'm going to drop that in to the chat window everybody okay.
07:52:10 Going once, going twice
07:52:16 boat is in play, please respond with a plus one, a zero or a minus one.
07:52:46 Give it a 10 more seconds.
07:52:59 54321
07:53:04 ending the vote,
07:53:08 and it carries 1-234-567-8910, that gets us there, folks. Thank you so much. I cannot tell you how greatly.
07:53:28 I appreciate that.
07:53:32 I'm almost seemed too easy Kenny.
07:53:35 Yeah I keep waiting for the other shoe to drop.
07:53:40 That's a big change so kudos to them.
07:53:50 really important.
07:53:52 This is something that I'm actually, including
07:53:58 that I will include in the quarterly update to not the LFN board but to the lF governing board, the elf Board of Directors, as a major milestone for the community so everyone thank you so much.
07:54:19 Well mark that as agreed.
07:54:31 I will mark that as agreed.
07:54:32 Okay, um, so next steps. Obviously there's the updates that Catherine talked about that we can bring up to align the aspects of the life cycle correctly.
07:54:48 So we can get work on that.
07:54:52 And I will get started on the process for the election so that we can get that going.
07:55:03 Again, I cannot express my gratitude to the TASC I cannot express my gratitude enough to the, to the community for hitting this milestone this is this is a major deal in the maturity and growth of own app as an open source project.
07:55:31 So, thank you.
07:55:31 I guess I should put that in the chat too huh.
07:55:44 Okay, I'm coming up.
07:55:47 We've got the Honolulu awards.
07:55:51 The link is there.
07:55:55 I will drop that long, let me just follow that.
07:56:03 And then drop the link into the chat window.
07:56:16 So that's going
07:56:20 ends next week, the PTO meeting on Monday, we've got a holiday here in the US, so that's going to be cancelled.
07:56:29 One summit folks should have gotten the information on that, that it is now and all virtual event.
07:56:41 So, that will be taking place in the Pacific Time Zone.
07:56:48 but the results of the
07:56:52 many travel restrictions and lm lF in being such a massively global community with lots of international participation decision was that that will be virtual.
07:57:11 So that's the update there, and then we've got the list of
07:57:19 other
07:57:23 events coming up, that you can see
07:57:29 it's.