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.

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log

06:57:59 From Kenny PAUL (LFN) to Everyone (in Waiting Room) : Please use your full name to be admitted.
06:58:29 From Kenny PAUL (LFN) to Everyone (in Waiting Room) : Please use your full name to be admitted.
06:58:59 From Kenny PAUL (LFN) to Everyone (in Waiting Room) : Please use your full name to be admitted.
06:59:16 From Alla Goldner to Everyone : #info Alla Goldner, Amdocs
07:01:02 From Amy Zwarico (AT&T) to Everyone : #info proxy Amy Zwarico, AT&T
07:01:20 From Andreas GEISSLER (DT) to Everyone : #info Andreas Geissler, DT
07:01:26 From Fred Oliveira to Everyone : #info Fred Oliveira, Verizon
07:01:36 From Magnus Buhrgard to Everyone : #info proxy Magnus Buhrgard, Ericsson
07:02:01 From Morgan Richomme to Everyone : #info proxy Morgan Richomme, Orange
07:02:09 From Yuanhong Deng (China Mobile) to Everyone : #info proxy Yuanhong, China Mobile
07:02:24 From Olivier Phénix (Bell Canada) to Everyone : #info Olivier Phenix, Bell Canada
07:02:28 From Dong Wang (China Telecom) to Everyone : #info Dong Wang, China Telecom
07:02:32 From Timo Perala (Nokia) to Everyone : #info Timo Perala, Nokia
07:02:38 From Jason Hunt to Everyone : #info Jason Hunt, IBM
07:03:00 From Ranny HAIBY (Samsung) to Everyone : #info Ranny Haiby, Samsung
07:04:24 From SaiSeshu (Huawei) to Everyone : #info Seshu, Huawei
07:04:27 From Srini Addepalli (Intel) to Everyone : #info Srini Addepalli, Intel
07:04:45 From Ciaran Johnston (Ericsson) to Everyone : #info Ciaran Johnston, Ericsson
07:11:23 From bin.yang@windriver.com to Everyone : #info Bin Yang , Wind River
07:11:29 From bin.yang@windriver.com to Everyone : sorry for being late
07:11:48 From Kenny PAUL (LFN) to Everyone : @bin thanks
07:15:05 From Sriram Rupanagunta to Everyone : https://docs.onap.org/en/latest/guides/onap-user/vfwcl-deployment-tutorial/index.html
07:33:04 From Kenny PAUL (LFN) to Everyone : #vote does the TSC approve the SonarCloud profile management model as described in the Proposal? +1, 0, -1
07:33:18 From Olivier Phénix (Bell Canada) to Everyone : #vote +1
07:33:18 From Andreas GEISSLER (DT) to Everyone : #vote +1
07:33:19 From Ciaran Johnston (Ericsson) to Everyone : #vote +1
07:33:20 From Fernando (Fred) Oliveira to Everyone : #vote +1
07:33:23 From Srini Addepalli (Intel) to Everyone : #vote +1
07:33:24 From Ranny HAIBY (Samsung) to Everyone : #vote +1
07:33:24 From Dong Wang (China Telecom) to Everyone : #vote +1
07:33:25 From Timo Perala (Nokia) to Everyone : #vote +1
07:33:26 From bin.yang@windriver.com to Everyone : #vote +1
07:33:26 From Yuanhong Deng (China Mobile) to Everyone : #vote + 1
07:33:26 From Morgan Richomme to Everyone : #vote +1
07:33:27 From Amy Zwarico (AT&T) to Everyone : #vote +1
07:33:32 From SaiSeshu (Huawei) to Everyone : #Vote +1
07:33:45 From Kenny PAUL (LFN) to Everyone : #endvote
07:35:34 From Olivier Phénix (Bell Canada) to Everyone : When we get to the PTL part, I believe Toine had a topic about new committers for CPS?
07:35:45 From Jason Hunt to Everyone : My apologies. Had phone issues. #vote +1
07:36:24 From Kenny PAUL (LFN) to Everyone : @olivier seen.
07:52:14 From Kenny PAUL (LFN) to Everyone : #AGREED:  the TSC approves the SonarCloud profile management model as described in the Proposal
07:55:50 From Alla Goldner to Everyone : sorry, also had issues
07:55:54 From Alla Goldner to Everyone : #vote +1
08:01:42 From Srini Addepalli (Intel) to Everyone : Sorry. I need to drop as I have an internal meeting.
08:05:04 From Chaker Al-Hakim to Everyone : the link to the ArchCom reviews dashboard https://safratech.net/onapdocs-dev/action_page.php?release=istanbul&doc_type=comp-review
08:06:07 From Kenny PAUL (LFN) to Everyone : https://lf-onap.atlassian.net/wiki/x/V9D3
08:27:55 From Kenny PAUL (LFN) to Everyone : #vote does the TSC agree that the regular elections of the TSC shall occur annually in September? +1, 0, -1
08:28:07 From Andreas GEISSLER (DT) to Everyone : #vote +1
08:28:08 From Morgan Richomme to Everyone : #vote +1
08:28:10 From Olivier Phénix (Bell Canada) to Everyone : #vote +1
08:28:11 From Jason Hunt to Kenny PAUL (LFN)(Direct Message) : #vote +1
08:28:14 From Alla Goldner to Everyone : #vote +1
08:28:21 From Timo Perala (Nokia) to Everyone : #vote +1
08:28:24 From SaiSeshu (Huawei) to Everyone : #vote 0
08:28:28 From Yuanhong Deng (China Mobile) to Everyone : # vote + 1
08:28:29 From Ciaran Johnston (Ericsson) to Everyone : #vote 0
08:28:37 From Jason Hunt to Everyone : #vote +1
08:28:42 From Amy Zwarico (AT&T) to Everyone : #vote +1
08:28:43 From Dong Wang (China Telecom) to Everyone : #vote +1
08:28:58 From Kenny PAUL (LFN) to Everyone : #endvote
08:33:35 From Kenny PAUL (LFN) to Everyone : https://www.surveymonkey.com/r/LFNDevForumJune21
08:34:53 From Kenny PAUL (LFN) to Everyone : #AGREED that the regular elections of the TSC shall occur annually in September

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:12 Okay folks, let's get rolling.
07:06:19 Nobody's muted when you come in, and the meeting is being recorded. Please keep yourself muted unless you're speaking.
07:06:27 You're coming in on phone line you can use star six to unmute yourself.
07:06:30 If you happen to send me a private chat messages.
07:06:35 Those will become part of the public record when I cut and paste them into the minutes.
07:06:40 And we will start by mentioning projects any trust policy. You can find this link from the lF and any other project websites. It's probably just as important where we have multiple companies such as yourselves, including potential industry competitors
07:07:05 in these meetings, please review if you have any questions please contact your company's legal counsel, members of the lF may also contact Andrew up to growth to firm up Grove LLP, which provides legal counsel, who the Linux Foundation.
07:07:09 Okay, can talk about
07:07:15 stumble and Honolulu maintenance, we're going to do the doc project update. If we have the folks on the line probably start with that.
07:07:29 I'm not sure that we have the folks on the line yet though.
07:07:33 We'll cover the solar proposal will do a vote on that
07:07:41 question of ppl stuff.
07:07:45 Discussion of liquid base. Want to talk about that. And Jim home be bringing that up shocker and give the update of the architecture reviews.
07:07:57 Any updates from any of the Mac SBC tak UAG
07:08:07 anyone would like to make.
07:08:13 Okay.
07:08:18 I'll say no updates.
07:08:22 That's course upcoming events, and then talk a little bit about the, what's going on with the to Dotto.
07:08:31 And then scan code IO Kristoff and Alexander I guess you want to have a quick chat there anything else.
07:08:46 Okay, so with that then.
07:08:51 Let's lead off with the update on the doc.
07:09:00 Sharing privileges.
07:09:07 Kk I can go ahead and kick that off. Okay.
07:09:12 Turn over to just be wrong. Okay, so.
07:09:17 So true. Yeah. Are you there you can you can go off mute as well to confirm.
07:09:26 Sam online.
07:09:30 Israel surround can hear us.
07:09:39 Just need to go off mute there.
07:09:46 We run.
07:09:51 Okay.
07:10:06 Why don't you start off with another agenda and come back to it.
07:09:58 Yeah. Oh, Robin, do you just let me give up.
07:10:04 All right, great. I'm glad you could make it strong.
07:10:06 Yeah so Kenny we have about, maybe 10 minutes total here.
07:10:11 Sounds about right.
07:10:13 Okay, sounds good. So, I'll just set this up and remind folks what the documentation improvement project. So this was all about. So little over a year ago, we were collecting some feedback from multiple and use your advisory group members that some parts
07:10:32 of the own app documentation that was required by their operations teams to get going with the project was was difficult, and it was, in fact, the date to adoption.
07:10:48 So, it looking at the best ways to address this feedback that we're getting and how we could try to quickly overcome that barrier.
07:10:59 We pulled together.
07:11:02 initiative in a statement of work.
07:11:06 In order to tackle the, what we identified as the. The main problem areas within the docks and the project was scoped out in close consultation with the do neck docs team.
07:11:18 Sophia Eric, and others were identified three prioritize priorities for fixing and one first one is around installation upgrade procedure. The second one was deep dive tutorials in SF DC and DC at the third was around backup upgrading your store procedure.
07:11:39 So after getting that scoped out and up and running a team, led by a large three round were able to tackle each one of these, and it's now been, I think, complete for a number of months.
07:11:58 There were a couple remaining issues that took a little longer to cycle through in terms of getting patches approved and accepted into, into the docks but now I do believe this.
07:12:12 So, as of a few months ago we had this this right up on a quick summary of what we're able to achieve in this project and apologize that it's taken several instances of being on the agenda before we had all the people here in place, but yeah, The idea
07:12:30 is to give a short summary here on what was achieved and see if y'all have any questions, so that I'll turn it over to zero.
07:12:40 give a short summary here on what was achieved and see if y'all have any questions, so that I'll turn it over to zero. Thanks. Thanks man. I'm telling you, pretty much, given the background.
07:12:46 So essentially we had presented this status, couple of months ago.
07:12:52 And we said, there are, there was one outstanding item that we were still working through.
07:12:58 So as of last month or six weeks ago we completed that. So that was the tutorial for the closed loop deployment. So that was the one that was spending.
07:13:11 So we completed that. So that's merged into the, into the master.
07:13:17 And it's, it's been there for the last six you know four to six weeks or so.
07:13:23 So with that be pretty much wrapped up whatever we had set out to do. Initially, so we will continue to monitor course. I think the real test of this, the effectiveness of this is as Brandon mentioned, people actually using it and finding that it's easier
07:13:41 to use the product or or now, with it with this documentation.
07:13:47 So, will will of course continue to monitor that on the under discussion groups and you know if people have issues, and using it. I know we will be jumping in and address the documentation part of it.
07:14:00 Obviously we're not looking at the product out of it and as part of this project, it was more on the documentation.
07:14:06 So we will continue to do that.
07:14:11 So, so that's that's pretty much all I wanted to give as a status. Is there any, are there any questions or comments, I can, I'll be happy to answer.
07:14:37 Okay.
07:14:39 Ron Thank you so much.
07:14:41 Brandon Thank you so much. Appreciate the patience.
07:14:46 I'm trying to get the update on the schedule so let's so that we can close things out.
07:14:55 It's been a kind of a hit and miss deal on on both sides of the equation there so no apologies for the delays and appreciate the work that's been done.
07:15:11 Sure, I'm just drop the link into the chat window for the guides bunk bed into the minutes.
07:15:23 The last one that got moist, which is the most low particular material.
07:15:28 but others which are already there in the, in the same time. So, yeah,
07:15:34 so that the link is just for the, for the last commit.
07:15:38 For the last one which was pending from the previous.
07:15:42 That's.
07:15:48 Hi, thanks so thanks everyone so much.
07:15:58 Okay, I'm
07:16:01 being no questions.
07:16:03 Let's go ahead and up to assemble.
07:16:10 We have em two scheduled for. Let me check my calendar today.
07:16:22 All right, thanks Kenny, um, It's I'm getting a notice of says hostess disabled screen sharing okay you did for some reason you didn't come in as a co host.
07:16:31 Okay.
07:16:41 All right. Alright, so as.
07:17:01 Here you can see we're at em to specification phrase here on June 17 next milestone is m three way out that August 26.
07:17:20 So where are we.
07:17:23 So it's changed quite a bit, the milestone status has changed quite a bit in the last, I don't know, 36 hours or so.
07:17:31 It was looking pretty grim earlier in the week to the percentages were pretty low but it's improved
07:17:43 quite a lot since yesterday, so I just updated this this morning so currently we're at 84% for the projects, and then 86% for the requirements.
07:17:57 So let's look at that a little more detail.
07:18:09 Let's refresh this. Okay. So, starting with the projects.
07:18:16 You can see that we have, what 24 issues remaining. I went through most of these yesterday and I noted that that many of the ones that are in the submitted are delivered status, are
07:18:40 the task for completing the architectural review. And in these cases the architectural review it's been scheduled, but has not yet yet occurred.
07:18:56 So that might be an area where we're willing to make some exceptions yeah you can see most of these are related to the architectural subcommittee review.
07:19:10 However, we do have a handful, particularly related to merge requests I was looking at that yesterday and there.
07:19:17 There are several that that still need to be completed.
07:19:27 And then looking at the project status, you can see that we're down to just two remaining tasks.
07:19:40 And let's see those are related to dual stack support.
07:19:51 You know nap and STC multi models support.
07:19:54 Do we have anyone associated with those requirements on the call.
07:20:11 Like,
07:20:18 democracy Dominus is here so I will follow up with him.
07:20:16 Okay.
07:20:18 Yeah, that would be helpful I sent an email out to all of the requirement owners that were
07:20:28 that have not started progress on their tasks yesterday and got some response but as you can see where we're still lacking.
07:20:43 For a couple of these would but Morris. Yeah, yeah, David, I can follow up with my colleagues Karen. Karen Johnson.
07:20:51 Okay, that would be helpful. Thank you,
07:21:00 David in your mail I didn't see that STC thing is it come up recently.
07:21:12 Can you be a little more explicit yeah the SEC multimodal support. I didn't see that in the mail you sent that that was outstanding.
07:21:23 Okay.
07:21:24 It's possible I may have missed one when I, when I sent my, my email yesterday I can go back and look at that. No, no, it's okay.
07:21:34 So we'll do like you're on set, check on that. Okay. All right, thank you.
07:21:40 Okay, there
07:21:45 in the email that I sent.
07:21:48 I think it's it's they're not on the on the text that you wrote yesterday but but down there.
07:22:06 Part of the requirements.
07:21:59 Yeah, yeah i i think what he said was that in the email that I sent yesterday. It may have been missing from that email, so that's that's possible I could have missed one.
07:22:13 Alright, and the table but it doesn't matter. I wasn't wasn't my intention to nitpick.
07:22:21 Yeah, No, no problem.
07:22:25 Okay. Any, any other questions about milestone status.
07:22:36 All right.
07:22:43 Actually, David, it took me a second to get off of off of mute, I'm sure, are the global requirements listed in the milestone somewhere in the milestone status I think that all we were all that SATCOM was looking for for our global requirements, is that
07:22:58 the projects that indicated, whether or not they were going to be able to meet those global, that they had the resources to work on the global requirements, right, and so let's, let's go ahead and take a look at that, that's on the impact view PR component.
07:23:18 So, so this page is improved quite a lot in the last week or so so thanks to the PTS and requirement owners for getting this updated,
07:23:30 and then going down to the
07:23:38 best practices and general or global requirements.
07:23:42 You can see that we still have a number of these axes are still not colored per this code up here, in terms of representing the support by the ptl.
07:24:04 So, looks like the map homes MSP modeling multi cloud CLIOMOFUUI sec so VFCVNSDK and bvp all need to.
07:24:27 Still, the PTS need to indicate whether they're going to support these are not.
07:24:34 I noticed you know with the specifications and the features and the use cases, we got a pretty good response in terms of getting these updated there's a couple of exceptions here the features you you I know that you have responded, but much less for best
07:24:59 practices and global requirements is there a specific reason for that or is there some, some difficulty here versus the use cases and features.
07:25:15 I wonder if that was just assumed that these would have to be done so
07:25:22 folks just didn't think about updating.
07:25:25 Yeah, that that could be.
07:25:29 But as far as I know we are looking.
07:25:35 I mean, in some cases, projects are just simply blocked for because of dependencies outside that control or whatever.
07:25:45 So I think we do still need to have an indication of whether these can be supported or not.
07:25:53 Can this please be brought up at the BTL call on Monday.
07:25:57 Of course. Thanks.
07:26:01 All right, because I think, you know, SATCOM has been the ones gone through the, the process of getting things as best practices and global requirements but I think it is more of an overarching project so David Will you take that are you going to bring
07:26:18 that up.
07:26:20 Yeah, I just said we would bring it up on the PDL maybe not Monday, okay, I just wanted to make sure that that wasn't going to fault possible and I so thanks.
07:26:28 Okay.
07:26:30 All right.
07:26:34 Okay, Any other questions about
07:26:39 the impact view PR component.
07:26:47 All right.
07:26:51 The only other things here of interest, I'm just tracking how many open issues. And these are when I say open issues I'm referring to. These are not release management tasks.
07:27:04 So these are issues that.
07:27:11 Typically,
07:27:11 you know, technical issues that the projects have created and assigned to the release. So I'm just keeping a running total of that.
07:27:25 One other thing, and we don't need to go into the too much detail here, but I am going to bring it up, but the PTO meeting on Monday and that is that we decided to add an additional milestone.
07:27:40 To release planning.
07:27:44 Following the Honolulu release.
07:27:47 But we didn't decide specifically what what tasks would get assigned between them three and then four. And so, I just want to get some feedback from the community about how we should set that up so that we can you know meet the intention of setting up
07:28:09 a new milestone.
07:28:11 So we'll be talking about that on Monday.
07:28:14 All right. So, in terms of meeting the milestone requirements.
07:28:29 And
07:28:29 we don't have Catherine here to get her input, unfortunately, and I didn't see a note from Catherine about not being available today. Did you see anything Kenny.
07:28:44 Well, Amy's proxy so oh Amy's proxy okay yes, I think she sent some, um, let me see because she sent me something, asking to proxy but she did say, here it is.
07:28:50 She did send you an email this morning, She sent it out to the whole TSA and said she was running late and I would be her proxy until she could join.
07:29:06 Okay.
07:29:07 All right.
07:29:11 So, so she is expected to join.
07:29:16 Later this hour or two but she's run it, but she's tied up in an enemy management and internal management meeting, meeting. Okay. All right.
07:29:26 So, um, so rather than me, saying, you know,
07:29:35 how to handle into specifically because I'm sure. Catherine has some opinions about that.
07:29:43 Let's. What I suggest Kenny, is we bring up the status of empty again. Toward the end of the meeting or once Catherine joins in terms of how we're going to move forward.
07:30:03 Given the current status.
07:30:07 And it shouldn't take more than five or 10 minutes, but if we could reserve some time for that at the end of the meeting, or once Catherine joins, that would be great.
07:30:22 will be an issue.
07:30:23 Okay.
07:30:24 All right.
07:30:33 Okay, next up we've got the discussion about
07:30:43 Sony I guess I should share my screen here, like Windows window there it is.
07:31:06 Okay. Um, so a couple weeks ago we had
07:31:02 this proposal that was shared at the
07:31:08 May 27 to see meeting by.
07:31:13 Yes.
07:31:19 On sonar cloud.
07:31:23 Thanks to put in place for for Jakarta.
07:31:26 They basically the requirements and how these things should be managed.
07:31:32 The
07:31:35 main, main questions that came up from the TASC were, you know, what is the what to the PDL to have to say about it.
07:31:46 And
07:31:45 we presented to the details on the 14th was viewed as something that would be good.
07:31:54 So we're just going to put this to a vote to
07:32:02 make this or approval at this point.
07:32:08 As stated previously reviewed by the TLC.
07:32:12 There weren't any specific questions or action items that that resulted from that.
07:32:22 Other than going to the PDL call.
07:32:29 And the details were on board with it. So, just like to go ahead and put this up for, or a vote on the City FC approve the sonar cloud profile management model, as described in the proposal.
07:32:44 Or I drop that into the chat window, are there any questions.
07:33:02 Okay.
07:33:05 There you go, folks.
07:33:07 Yes, the members please vote.
07:33:32 Okay, give it 10 more seconds.
07:33:47 Mandy that passes.
07:33:51 So, pts, you can go ahead and start submitting tickets to send an email to with, With the next steps that they need to do.
07:34:03 But yes, if they want to get ahead.
07:34:07 The videos can start submitting the idea requests to look at their permissions for managing and administrating issues on their projects, and it turns out that I am on support this week so.
07:34:25 Yes. I'll be taking care of them.
07:34:33 Thank you very much.
07:34:41 What do you do doke.
07:34:46 I should have actually I should probably bounced to chalk our first about the
07:34:53 status of the architecture reviews.
07:34:58 Do you want to share or do you just want to talk to each chakra, like to share.
07:35:03 I'd like to share. Okay, let's see, are you in twice. I am in twice. Sorry.
07:35:08 Well no, not to apologize for Let's run a work around the
07:35:18 record Grammy issues okay so I think it's
07:35:23 this one that you need to be co hosted. You can
07:35:33 let me, let me give it a try
07:35:41 not to try the other one.
07:35:44 Okay, sorry.
07:35:57 Thank you.
07:36:00 Okay.
07:36:06 Okay, so just
07:36:11 to bring everybody up to speed on where we are. But before I go ahead and do that.
07:36:17 I'll spend a few minutes.
07:36:21 Going over the status report that I sent out every week.
07:36:27 So this is the report from this week.
07:36:34 So the report has a quick links. So you could take a look at it at your leisure.
07:36:41 So if you scroll through you could look at the main topics within the report because the reports can wait to be big, so I thought we put anchor
07:36:54 anchors within the page so you could easily navigate the page.
07:37:02 The one thing that you want to look at that I that we just added, is this
07:37:10 the component reviews dashboard This is brand new, that I added in. And I think it's useful so hopefully everybody thinks the same.
07:37:21 It's useful as well. So if you click on it, it should take you to this page, and this page.
07:37:29 The go over the color coding over here briefly.
07:37:33 But this is the latest and greatest on App architecture diagram, what we did is we repurpose the diagram to actually use it as a dashboard for the architecture reviews, and the color codes are such that the bluish, the normal own app component colors
07:37:58 indicate that the component is not participate in the release and this is based on the project management report.
07:38:10 The brownish color boxes or components are the components that are scheduled.
07:38:18 And the green boxes are the boxes where the component reviews have been conducted, and the reviews have been approved, so I'll give you an idea of just take one example.
07:38:35 And again, I'll let you access the page the pages can be accessible.
07:38:41 Like I mentioned earlier from the, the agenda or the meeting minutes and then I could always drop the page in the chat room but let me give you an example and let me pick on service designing creation, and if you click on it, it will take you to the JIRA
07:38:59 ticket associated with the, with the review the review was conducted yesterday.
07:39:05 Sorry, on Tuesday on June 15.
07:39:08 It was approved. And when a JIRA gets approved, we tag it with the or nine or the specific release that was approved in.
07:39:21 We highlight the sponsors, as well as the presenter Andre did nice very nice job yesterday presenting as DC.
07:39:28 And then we include all the documentation that were reviewed during the, the review session. And then we label, or we tagged.
07:39:40 We add the committee decision.
07:39:42 And in this case it was approved on June 15, so.
07:39:48 So this is the, the component that was approved yesterday. Let me take a component that is scheduled for review and it's uui.
07:40:01 As you could see you You I scheduled for the 29th.
07:40:06 The sponsor is Sharon, and it's working progress. As soon as the documentation is for the review have been completed, then they will be added over here so this dashboard gives us an idea as to where we are in terms of the architectural reviews.
07:40:23 The number of architectural reviews that have been conducted, and the outstanding reviews that we still have to go through and as you could see over here we still have a probably a dozen or so reviews.
07:40:40 Four of them are scheduled for next week, and two additional ones are edited or will be reviewed on the 29th. Now, ao some people in apology because I, for example, the SDN controller Dan has sent me a request for review about three weeks ago, and so
07:41:00 did the use case you I.
07:41:04 However, I had a filter in my mailbox.
07:41:08 For the own app arc emails and that filter was something was wrong with the filter so I missed some of the requests that came in. Early on, so my apologies to the PDF files but we added new session on the 29th.
07:41:26 Just to address the, the, the oversight on my part, I just want to make sure the reason I'm saying this is I want to make sure that everybody understands that the details were not late, it was a an oversight on my part that basically delayed their reviews
07:41:42 so I expect all the reviews to be done by the 29th.
07:41:47 Again, this is a, this is the me this is a good dashboard. I'll invite you all take a look at it, and it gets updated on regular basis. So, You always looking at the latest.
07:42:00 The latest version.
07:42:08 One last thing, if you click on the boxes that are in the traditional own app colors, you'll go to page that says no changes our plan for this symbol release.
07:42:14 So with that, I just want to make sure that if you have a chance.
07:42:21 If you are.
07:42:24 If you either are responsible for a function or a box or sub component that somehow someway, I overlooked, please reach out to me directly, and will correct it if you see any anything that is not consistent with what you think the status of your component
07:42:48 is just let me know.
07:42:49 But moving forward, we will be using this dashboard to track the, the rest of the symbol releases, or reviews, and for the all the future releases and reduce any questions comments from anyone else.
07:43:11 Thanks.
07:43:13 Sorry, go ahead.
07:43:15 Yeah, I was just gonna ask real quick shocker nice process here, I was curious, are the projects that are in maintenance mode or and maintain are those are the ones that are listed here is deprecate it.
07:43:28 Yes.
07:43:30 Okay. So, for example, the one that I just clicked that right which is the logging, right, this is a, this has been a dedicated function.
07:43:43 I do flag it and I want to go back, sorry let me go back.
07:43:47 I do flag let's say for example login or upon boy if I click on login takes me to a page that says it's been duplicated, but I also added over here.
07:43:59 A link to the most recent documentation is of login so at least we could go back and take a look at it. And if there's an inconsistency.
07:44:11 We'll, we'll just address it as such.
07:44:15 But that's the intent The intent is the for the gray boxes and I hope I captured it in the legend yes it over here, but know if you could see my cursor.
07:44:28 The grayish areas are areas that have been or components that have been dedicated.
07:44:35 Great.
07:44:36 I believe I did the same thing with Pump, pump has been duplicated and you could click on the latest documentation is and I guess somebody or a must have their own link.
07:44:50 I'll take a look at it offline, a shocker what what is the difference between participating and duplicated.
07:45:06 Well dedicated, let's say for example we have two functions that have been replicated or as far as I know, two functions that we collectively decided they should be dedicated and logging and and Pompa.
07:45:14 Those are functions that are no longer maintained moving forward.
07:45:21 So, So we're not, we're not.
07:45:26 There is no BTL, we're not in any features, and so on so forth, where, if I click on the map and it says no changes are planned for this simple replay release, which means they're the PDL or the PTS have decided that they're not changing any code.
07:45:47 Not features, but then not changing any code. As far as the component is concerned from, from the component architecture perspective. And therefore, it doesn't require a architectural review.
07:46:02 And I thought there was a distinction between unmaintained and dedicated because Don't we have more than two projects that don't have a PTO.
07:46:11 Yeah, we've got projects that are currently unmaintained.
07:46:17 I have not flagged those on this, on, on this diagram.
07:46:23 I only flagged those projects or components that have been duplicated on
07:46:34 and maintain project does it make sense to keep them on the map because he said, is it not confusing to to to mix them, or do we have do shall we say that after to release of and maintain status should be deleted from from SIGGRAPH because it's a bit
07:46:51 confusing.
07:46:56 Yeah, so
07:46:55 sorry to jump in before you can answer shocker. So currently, projects that are officially in unmaintained. We've got a FFC logging music and portal, or officially in unmaintained status.
07:47:17 Could you repeat that list logging music portal and AFFFC logging music portal and video as well.
07:47:29 Yeah hadn't we voted for good then. Yeah, yeah, yeah.
07:47:35 I didn't move those who
07:47:51 I mean this is good information right so I'll get the list from Kenny, and from David. And then I'll make sure I color code them differently so this way we could, we could flag them on on this diagram and Kenny also in the they're also in the documentation
07:48:04 list already mentioned, as, as I mentioned, yep.
07:48:09 So I want to go back to the point that Morgan was, was making.
07:48:18 I contemplated Morgan about taking out the logging and the audit, but if I do, then we lose a track or the opportunity to actually find the old documentation, from my perspective, it doesn't really matter.
07:48:33 I could you know I could go either way is just what the game, you know it's up to the community to decide as to whether we should leave them here or we should take them out completely.
07:48:45 It's a bit. I mean if it would have been the official documentation we are managing the different versions so we could have a matter of, you know, look at our map for innovations and as its vision.
07:48:56 We have branch provisions we can have the map is a graph reflecting the real architecture production so we don't have one graph for older versions.
07:49:06 And I think documentation is doing that, and on everything that is in official docs that are not at work is managing that so I think it would be from a perspective, easier to understand if we have really something really matching the release.
07:49:23 One, I understand that it's important to keep their history, but that's why we have branches in the in get an addition is there's also one additional elements, which is not easy to track on your site is that we have unmaintained element, but that are
07:49:38 mandatory that we're still deploying because it will prevent to, for example, if is and maintained for quite a long time but we still deploy somebody found some element of if because we cannot to the way.
07:49:53 And so sometimes it's unmaintained bit still there, sometimes it's and maintain and then we can remove them on we start removing some some components.
07:50:03 So that's also something that easy to track, because we have to deal with it.
07:50:18 But definitely the visioning, and part of the official documentation will fix the issue of saying, okay, you want to keep all the story but you cannot tell if we would use official Doc, for sure it will be easier to manage.
07:50:32 not gone back to the back to the distinction. I think that is the distinction between deprecating and unmaintained so AF is unmaintained. So, it is still included in the release but you know it's kind of buyer beware, as opposed to logging to deprecate
07:50:55 it which are actually removed they're no longer part of the release, I believe that that's the way we work it doesn't. Yeah, yeah. And I think that's it that's a good feedback right it's good feedback I think you know at this point in time moving forward
07:51:00 logging and audit.
07:51:04 Probably should probably probably be removed.
07:51:08 We should, but logging shows as being, but Kenny said logging was unmaintained versus being an IT same with a as opposed to being deprecate it is that true.
07:51:22 That is what we have, we haven't.
07:51:26 Like, retired them or move them has we deprecate it anything though so it really is truly no longer part of the architecture.
07:51:35 Have we deprecate it anything though so it really is truly no longer part of the architecture. Well, we don't deprecate anything at least when it comes to the life cycle states of the projects that we have so that's a bit confusing so we have archived.
07:51:46 Yeah. Okay, so I've does oppose market. Okay. We archived some, maybe, also on this. Here the re one should be archived rather than we have the same vocabulary throughout.
07:52:06 So, so, yeah, I work offline with, with the, with Kenyan and David like I said earlier, and then we'll try to color coded in such a way where, you know, we can tell by looking at this diagram which components have been under in on main things they versus
07:52:28 archive state, but the the takeaway point from this, this diagram, though, is that we're going to use it to, to track the state or the status of all the architectural reviews.
07:52:45 And at this point in time we're on track to complete the all the architectural reviews by the, the 29th of this month.
07:52:57 I have one more question, I placing anywhere. Is it because it is not a separate block.
07:53:04 Slicing is a use case, I have a i, or at least it's considered a use case, right. So it's part of the use case block, if you will, or cluster that is maintained somewhere else.
07:53:19 This one over here, unless I give you my intent and then we could discuss as to whether we should include more information into this diagram. My intent over here was to focus to use this dashboard to focus on only on the component architectural reviews.
07:53:40 But if you go back to the report.
07:53:44 The weekly report, they in the tables there is, there is a set of tables they've created that basically highlight all the use cases that have been reviewed all the functional and non functional requirements that have been reviewed as well.
07:54:12 What this is what this diagram is focusing on is the architectural reviews for only the components.
07:54:12 Ok.
07:54:21 Ok.
07:54:21 Ok.
07:54:25 Wendy one feedback I have is that since the slicing is one.
07:54:31 It has quite a bit of code in some of these components, I mean especially. So at some point of time can think of renaming. So beyond service, also quality the slicing orchestration.
07:54:49 Yeah, I mean we could certainly do that let's, I mean, if we want to brainstorm and trying to see and collectively decide that slicing should be shown on this diagram.
07:55:04 I think it would be a good idea, let's let that but we would need to all decide how we want to depict it, I want to show it in relation to all the other components.
07:55:13 Yeah, I think if, if, if we try and start overlaying use cases.
07:55:18 Because we have many use cases I think if we start trying to overlay use cases on this.
07:55:26 I'm no that's not what I'm suggesting, but I'm just saying renaming so something more than just service orchestration.
07:55:34 Yeah.
07:55:39 While you just answered the question about use cases nothin is on.
07:55:46 But then did a really nice job on the use cases or just type thing.
07:55:52 just give me a second I showed you
07:55:57 did a really nice job on the use cases.
07:56:03 And now 13 second.
07:56:08 So if.
07:56:13 So, so this is a list of all the use cases.
07:56:20 Ben took the initiative and put together the this diagram.
07:56:26 And basically came up with the initial link to all the use cases that we have done so far.
07:56:32 So I took, I took what he put together and incorporate incorporated into this so you have basically a way.
07:56:43 On this diagram to list.
07:56:46 So it created like buckets you know five use cases be enough use cases so on so forth.
07:56:51 But as you could see training to your point right you have a list of all the use cases that are associated with the 5g use case. And they point, they should point to the latest documentation of these use cases.
07:57:07 So hopefully that I think that's helpful. I'm not sure if it answers your question.
07:57:12 But I think we kind of address that in a roundabout way.
07:57:17 But at least you have a dashboard over here, or you have a launch pad that allows you to access all the, all the use cases, since the inception of the creation of own app so if you go go.
07:57:30 If you go back to general use cases I think we then went back all the way back to the virtual CPE and the broadband, use cases so on so forth.
07:57:40 So, this will give you at least a way to access all the use cases, even though that some of these cases may or may not, or should or should not be included in the main page or the main diagram, but at least this will give you a really good, good way to
07:58:01 review all the use cases that have been created since day one.
07:58:09 And my only comment was that slicing is such a important piece in the recent past right which we have to look at architecture diagram. It settles the slicing name any way that could be maybe a disservice to ourselves.
07:58:24 When I agree with you, I'm agreeing with you. I know exactly what you're talking about. I kind of agree with you, right. So let's think of a creative way selection is is a critical piece of the architecture, and it should be highlighted, right.
07:58:38 So let's agree on, where it should be. I mean I could certainly come up with some draft versions and share it with the team and see what we think but if you have any ideas or if you have any options that you'd like to propose.
07:58:57 Please feel free and then, then we'll give it a shot.
07:59:01 We'll add it to this page, and as a draft version, and get an agreement from the rest of the community as to whether we should move forward with it or not, but I do agree with you that slicing is critical and should be highlighted.
07:59:18 Okay, yeah, let them. If you have any ideas I let him.
07:59:22 Yeah, I'm going to take a look at a Comment Tracker. Sure, sure.
07:59:28 This is nk Shanker.
07:59:28 Yeah, we should really get input. Besides, besides the pitch just steady Sure, Ben was also tracking how different use cases have an impact on different components and that's also captured in some other requirements, kind of tables, but it also done something
07:59:46 on contents and so
07:59:50 I guess I mean we should do this, probably to cover other use cases as well.
07:59:55 But yeah, the point is well taken. People should be able to really see how besides the components, the use cases are covered in different releases and dependencies the everything.
08:00:10 Thanks.
08:00:14 Good feedback.
08:00:19 Any other questions or comments.
08:00:23 Okay.
08:00:25 Thank you. Back to you, Kenny, David.
08:00:31 Thanks shocker.
08:00:37 And I will
08:00:40 put down and they grabbed an action item for
08:00:48 for you and I to sync up on status and maintain an archive projects. I did do a quick cursory check I mean I haven't really done a lot of digging.
08:01:03 Yet I didn't find anything listed in 2021.
08:01:08 I did that open in a new window.
08:01:11 But I did find
08:01:15 the 2020 that we moved those projects to maintenance.
08:01:26 So and and since then we have changed the word maintenance to unmaintained.
08:01:32 So I don't see where we've actually moved anything into our fully archive state yet, But I just did a cursory review or a cursory search. I'll be a little bit more digging down to see what I can find in that.
08:01:50 So that's just a note for the PSC in general.
08:01:55 Okay, um, let's
08:02:01 move them to the
08:02:06 EPL topics
08:02:13 bottles and Alexander have been promoted to from contributors who integration converters Congratulations Thank you so much.
08:02:27 That's really good wanted to discuss a little bit about what the backup plan is for given more gun. Moving on to other other aspects of hanging off on that for a moment.
08:02:44 One Are you online.
08:02:49 Yes Yeah Kenny I'm here.
08:02:51 Okay. Let me give you permissions, and I will stop sharing
08:03:00 you'll have a chance to quiz promotional question.
08:03:03 Yes.
08:03:05 Okay, well seconds.
08:03:09 Right, yeah share screen.
08:03:15 So yeah, basically, in conflation persistence. So as we have quite a few changes as a new project lately, anything yet.
08:03:25 I always forget you have to double the double click, always gets me.
08:03:33 Can you see my screen now. Yes, sir.
08:03:36 Okay.
08:03:37 So as I mentioned CPS team has grown quite substantially. We now have 14 people actively contributed to the code.
08:03:47 And one of our competitors.
08:03:50 Actually, left the company, as of yesterday. So we took an action, two weeks ago to start this process of looking at getting more people to commit our rights, and we propose this to the people we had.
08:04:04 We followed. First, this was the first time as well before the process as it was documented so the PTS have have folders and all these to be request, staff, and all these three have been approved and now we weren't quite sure about the next step and that's
08:04:22 why we're here, I suppose.
08:04:26 Water TC committee, and those are the, we do this correctly but basically.
08:04:32 These three are bolted on have been approved internally in the team by by the current competitors.
08:04:42 Okay, and I don't I'm pulling up the information right now. I know it's under repo management.
08:04:55 So we've made this commits in our own Yama files I think to to to activate this but depending on this approval basically now.
08:05:18 think that
08:05:22 Australian accent okay just one.
08:05:24 One second.
08:05:31 What's I don't remember off the top of my head.
08:05:44 Okay. Um, so, for I'll go ahead and share my screen again.
08:05:54 So adding a computer.
08:05:57 This is in the repository management I'll drop this in if any DSC members or anyone has a
08:06:06 question on this
08:06:10 in the chat window.
08:06:12 So one of the things that that happened a while back, was that this was moved to be pretty much community driven. So adding a competitor.
08:06:27 The PDL fills it out.
08:06:31 Once all the documentation has been provided which you have done
08:06:36 under your projects hierarchy.
08:06:38 If you just follow the, the technical process.
08:06:44 Then you should be good to go.
08:06:49 Without any specific approvals required by the DSC.
08:06:57 So I think you're good to go, sir.
08:06:59 Okay.
08:07:00 That's great, thanks for that Kenny.
08:07:07 Yep, so.
08:07:11 Sounds good. Congratulations.
08:07:12 Yeah, I'll pass it on to the newcomers. Thank you very much.
08:07:23 Okay, Well, has we gotten Catherine yet.
08:07:27 No. Okay, I don't see her on, I'm certainly, we do, we do have, I think, Christoph joined so I think since he's the architect of our new process he would, it would be good to have his input on this as well.
08:07:44 Whenever you're ready Kenny.
08:07:47 Well I mean primarily primarily I will just summarize the conversation without going into a lot of detail right at the moment. I know Catherine has been having conversations with a number of folks on the TASC about how we can
08:08:08 address the needs of integrate of the integration team and provide for that.
08:08:16 So work is, and discussions are taking place in the background in terms of trying to align resources that will do this.
08:08:26 I know she's been a great deal of time on it.
08:08:28 So, I don't want to dive into the details, because she has most of those but from the sounds of it we have a number of our member companies that will be stepping up to the plate.
08:08:49 To help to help distribute the workload. That was all being performed by Morgan,
08:08:57 which, you know, was was, was a superhuman effort.
08:09:11 Okay. So moving on a bit.
08:09:17 Jim you want to talk about liquid base.
08:09:23 Sure.
08:09:25 So we were looking at using liquid base for doing database installation and upgrades and downgrades of tables and such.
08:09:35 And I understand that CPS was already using it and running into some legal issues because apparently the jar includes both stuff that's covered under a patchy as well as stuff that's proprietary.
08:09:49 So I was wondering what the status of that is can we use it or not.
08:10:03 And also, was anybody else, looking at, perhaps some pulling jars from the other jars from Maven central because it looks like somebody may have unpacking some of the components and those are all Apache to license.
08:10:13 So I didn't know if pulling those would be sufficient. Haven't investigated that yet.
08:10:27 Well, personally I believe that you should put the jar into some kind of analyzes to, and then get the content of the jar and check the licenses.
08:10:40 If there are licenses which are incompatible with Apache, then you probably should not use it within on up.
08:10:50 There are some in the existing jar the one that's the whole package includes stuff that is not Apache to license that stuff. However, it won't run.
08:11:05 Unless you have a license key so it's only going to let you run the stuff that you're licensed for an Apache to.
08:11:13 Even though it includes all the other stuff.
08:11:18 We've actually mentioned Jim. We've been looking into this for a while now with CPS because we are using, depending on us.
08:11:27 It's the website to liquidate websites clarifies as they say to have only one delivery the same delivery for basic commercial and non commercial use. And what they state is that the Dr.
08:11:39 Yes, are included with the commercial features, but a simply not activated, unless you have the license key and they simply don't have a separate delivery so that's how it works.
08:11:51 So Steve Winslow was has looked at this for us and I think he was kind of take that with it some other licensing issues that are pending.
08:12:00 Is it a legal team that he is part of are not quite sure that that's my understanding of this of the status. But I think it's good that you bring it up here and get some people's opinion on this, because a bit of a funny one
08:12:18 extra
08:12:18 And and yes Steve Winslow is a member of the Linux Foundation legal team me is the individual that does our license scanning and things like that.
08:12:31 So, there, they, they provide whether it's on an a, an open license or proprietary code there's only one.
08:12:47 One distribution of the software. And the only way to enable the proprietary aspects of it are to have the license keys.
08:12:57 So, and we do not need the proprietary aspects, is my understanding.
08:13:04 Correct. We don't need a need or not, you build a jar from the liquid best source code does that content proprietary code as well.
08:13:14 We haven't considered that option I know that's been talked about for two PPS, but you know we we haven't looked into that option stuff too much at the moment we're just like any other dependency we were using the GIS as they provided by by the distributor.
08:13:34 Well, but personally for me, this is kind of freaky wall.
08:13:42 mostly because he the project is open source, then it means that they're probably the repo, probably does not contain the proprietary code.
08:13:51 And then, what kind of Eve, the jar contains something else.
08:13:57 It means that we do not have the ability to fully revealed on up, and all these dependencies from the source, which is kind of really bad thing in the open source environment.
08:14:10 And then in the end, you lose the control over what you are really shipping, because you're including some binary properties, some, you know, buying a piece of code and yes they're probably elegy to my people and they are not including any kind of back
08:14:32 doors or stuff like that. But man, who knows, supply chains attacks are happening right so how do we know that the binary data we have the jar that we have is a legitimate.
08:14:45 If by design.
08:14:46 We agreed that hey there is some piece of proprietary code that will behave differently provide the license key or not, is that yeah i mean that's a good point is there a.
08:14:59 But, but is there a way of testing that in fact the code that that requires a license key would not be executed in a normal, in the case of Bona, because then Christoph essentially the stuff that's a license key in the context of our own app itself becomes
08:15:15 similar to a comment.
08:15:17 It's not executable.
08:15:20 The question comes up, if somebody is using an app, and they have the license key so this comes down to an operator who decides to use it, then that the capability becomes available.
08:15:34 But is that capability going to be executed. I think that's, you know, how would own app, how would own app itself, execute the the liquid base proprietary code if it wasn't written into own app I think that's the, The question to ask.
08:15:50 So there's kind of two things. One, are we 100% sure that the stuff that requires a license is never executed in the context of an app without a without a license key.
08:16:01 Second, if a license key enables it, if a license key enables it will that affect will existence of that license key affect the behavior of own app as it comes out of the box.
08:16:15 And the other thing is, what's really inside, right, it doesn't jar that that's package. Okay, we may try to the compile it if it is not obfuscated.
08:16:28 But still, how does it is it, you know.
08:16:35 Allow permitted by the license or not. If it is not, then how do we check what's really inside that jar that we are including, we cannot rebuild it, because we do not have the peace of proprietary code that is included in there.
08:16:47 So how do we know that there, there is no boundaries, how are we going to check that how are we going to,
08:16:56 you know, ensure the operator that we are really shifting. He is a good piece of open source code not some, you know, proprietary backdoor from company, X or Z.
08:17:09 Is there a way of telling, is there a way of running this through something like this on our cloud with the code coverage. I'm just throwing ideas out there, but it's, you know, it is a, it's a concern that I share with you, Chris stuff but I also, if
08:17:30 if we build our own container or our own our own copy of it. Without the licensed parts.
08:17:35 What happens. Who's going to continue maintaining that that's my other side of it from a security standpoint we somebody's going to have to commit to maintaining the on App liquid base, but I assume that we are not making any changes the source code,
08:17:53 because we are using jar I know but you they're gonna have to download and create you know when they're new it new releases of liquid base. I'm just, I, ideally, that would be the thing to do, I think, but the question is Will someone take that on as
08:18:10 a task that they do per release.
08:18:15 Right, so I would say that the main question is to assess how much work that is, is, you know, a container because I understood that it's not the container it's just a Maven dependent dependent dependency.
08:18:30 So, if that's just a Maven dependency then it's just a matter of building a jar from the source cool. That's my understanding, at least.
08:18:40 Right.
08:18:43 If that would be true. I'm maybe I'm not sure but I expect that Maven has the ability to include a project by the source code so you may always the module or, you know, do anything which you want to point to a specific version of liquid base.
08:19:07 My other concern about doing that is that if we take if we create an app specific liquid base jar.
08:19:14 Do we lose some of the capabilities to do software composition analysis on it that because software composition analysis isn't all that intelligent a process, it's actually looking at the signature or the hash of of a kind of a given component and comparing
08:19:30 that against the database of CV as if we have an own app specific one do we lose that traceability back to see the is that or is in the actual liquid base jar.
08:19:44 As opposed to the liquid base jar, third party jars we don't always have access to the source code anyway so, at most, I would envision this would take the existing jar extract out various class files and other components, and then just repackage them
08:20:00 and another jar.
08:20:04 So signature shouldn't change on those class files and such. Okay, it would just depend then Jim on how we do the on how the how the CV ease are tracked at what look at what level, I think yes be what it can and that's what I'm concerned with that if
08:20:20 we if we've created our own.
08:20:24 Do we lose, do we lose the traceability back to non CVS and liquid base,
08:20:31 one other option we're looking at currently is.
08:20:36 Like I mentioned, Maven central has a number of these liquid base components which are just Apache to.
08:20:44 So, if one or more of those are sufficient to do the functionality we're after, then we'll use that instead and then the issue will go away.
08:20:53 But I don't know yet on that one.
08:21:06 So you're asking if Maven central has these different version, or you're seeing them came out with a coach Coach said, I have seen it has a liquid base core liquid base parent a number of other liquid base components.
08:21:20 All Apache to license.
08:21:23 Okay, so one or more of those is sufficient. and we are okay but I don't know until we investigated that further.
08:21:32 Yeah, no, I would have to look, I'm not a homestead clear I thought it was only one version I thought Steve did look a little bit further and of course his conclusion was.
08:21:42 There's only one package that has all this functionality and it does include those components, but I'm not sure on that.
08:21:49 Okay.
08:21:50 Yeah, there was definitely a liquid base stash distribution that it.
08:21:56 Yeah, I had had everything. I know we don't want that one.
08:22:00 If we can avoid it.
08:22:06 Yeah.
08:22:12 Yeah, so.
08:22:14 Thanks Jim so CPS is has currently been making use of it.
08:22:24 Well, we can all bring Steve and see where we are, there's any more work to do, or if, if you consider his evaluation to be complete.
08:22:42 Just a short question have you compared the jar that is in Maven with the jar, that is provided in the top around the talk was the recent release.
08:22:55 Is it the same or maybe jars that they're providing going layer.
08:23:00 github page are simply not containing the proper third stuff.
08:23:05 I didn't know I'm, you know, especially that for every release, I see that you have a jar and next to it you have a source code.
08:23:14 So if people are releasing it this way, I expect that if you don't know the source code, you may recreate the jar, that's at least the, you know, best practice.
08:23:36 Now we haven't looked into that so these are options we can consider.
08:23:44 Okay. Anything else on this topic.
08:23:58 moving on.
08:23:59 The next enterprise call is the 23rd of the folks are interested in that, please join.
08:24:09 Lots of work going on in the CNF Task Force, as well, with various committees and, and
08:24:25 things like the Mac, helping to work on to talk about our own app is evolving into the CNF world.
08:24:40 Okay KFC to Dotto don't have a lot of time on this. I have discovered that much to my dismay.
08:24:51 That, trying to update.
08:24:54 Long numbered list.
08:24:57 In the wiki is second only in difficulty and pain to calendar management.
08:25:04 So what I've actually been working on is.
08:25:10 I don't things into.
08:25:24 I've. This is my fifth attempt at fixing this.
08:25:17 So I've dumped everything into Google Docs I'm still doing the, the edits needed
08:25:26 done a remembering effort here.
08:25:29 What I will do is when I am done I will make this available in Google Docs, I know that some people will not be able to get to it in that case I'll print out a PDF and send it.
08:25:43 But once we looked at it there.
08:25:49 Then,
08:25:52 we will will will put the vote forward, an email vote forward on that. Now, knowing that we've got many, many people that are about to go on PTO for the summer.
08:26:12 One of the things that I have. I am suggesting.
08:26:18 I'm originally I had said that the elections were going sorry for the scrolling,
08:26:31 that the elections.
08:26:35 Were going to be in May.
08:26:39 I am suggesting this be moved to being annually in September.
08:26:48 This will allow us to get the document approved since it has taken me far more time to fix it than I thought.
08:26:58 And it won't. We won't start launching the cycle. Well, people are on holiday.
08:27:08 I would like to put that forward as a vote of the TASC.
08:27:20 Are there any questions around, around my thought process there.
08:27:33 Okay, so give me a second to type this in as a vote.
08:27:56 Okay, I am dropping dead in to the chat window is a vote.
08:28:02 The TLC agrees that the regular elections of the TLC show occur, annually in September.
08:28:24 Day some that went direct to me.
08:28:24 Yes, sir.
08:28:48 Okay, give it another 10 seconds.
08:29:01 Okay. That is approved, thank you everyone, and thank you so much for your patience on this.
08:29:11 This has been much more painful than I ever could have imagined it trying to get things updated with all these changes so appreciate the patience there
08:29:27 any can we finalized empty.
08:29:36 If we are ready to, if you think we're ready to finalize it too. Yeah, I just, we said we would defer the, you know, how we were going forward until the end of the meeting, and so I just, I know we're almost out of time so.
08:29:52 So what I'd like to suggest is that, so that the requirement owners were contacted and the remaining two open issues have been resolved so we're 100% on the requirement tasks.
08:30:09 And we're I think approximately 90% complete on the project release management tasks, and I've looked through the open issues and the relatively minor.
08:30:23 So, what I would like to do is to suggest recommend to the TASC that we approve em to with with exceptions. As noted in the, the milestone tracking milestone status page for projects with the understanding that those exceptions will be completed by a
08:30:52 week from today.
08:31:01 Um.
08:31:01 The. Okay, is there the link to the exceptions where it says milestone status, sir.
08:31:11 Thank you.
08:31:24 So the one thing is is is this page being dynamic.
08:31:36 Right, I can put together a list of the specific exceptions.
08:31:49 So, if we need to have that specific list and we might yeah we need to have.
08:31:53 We need. So it will. Yeah, so I can't do that here since we're basically out of time so I guess we'll have to defer the the vote, to an email vote.
08:32:05 And I'll put together that list.
08:32:07 Okay, cool. Any objections to doing that, from the DSC.
08:32:15 Any questions about what I said regarding status.
08:32:24 Okay, I'll provide that list to Kenny, and then Kenny can send out the boat.
08:32:34 Thank you, David.
08:32:39 Okay.
08:32:40 We are a couple minutes over.
08:32:44 And I need to drop the agreement on the
08:32:58 on the on the election in September, into the chat window is there anything else anyone. Oh, very important, folks, please if you attended the event, please take the developer survey.
08:33:15 I will drop that link into the chat window right now that's highly important to us.
08:33:25 It's actually there in the agenda.
08:33:29 I just want to paste because a lot of times.
08:33:32 Okay.
08:33:40 If you haven't done it.
08:33:42 Please take the survey link for us it's it's it's very, very important to us.
08:33:48 The scan code I oh we will move to next week.