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 

05:58:31 From  Sai Seshu  to  Everyone:
    #info Seshu, huawei
05:59:25 From  Fernando (Fred) Oliveira  to  Everyone:
    #info Fred Oliveira, Verizon
05:59:41 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #info Yuanhong Deng, China Mobile
06:00:21 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
06:00:27 From  Ranny HAIBY (Samsung)  to  Everyone:
    #info Ranny Haiby, Samsung
06:01:10 From  Magnus Buhrgard (representing ONAP)  to  Everyone:
    #info Magnus Buhrgard, Ericsson
06:01:18 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT
06:01:20 From  Alla Goldner  to  Everyone:
    #info Alla Goldner, Amdocs
06:01:44 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
06:02:01 From  N.K. Shankaranarayanan  to  Everyone:
    #info N.K. Shankar, STL
06:02:07 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang,Wind River
06:02:16 From  Catherine Lefevre  to  Everyone:
    #info, c. Lefevre att
06:02:59 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
06:03:19 From  Sylvain Desbureaux (Orange)  to  Everyone:
    #indo proxy Sylvain Desbureaux, Orange
06:03:30 From  Sylvain Desbureaux (Orange)  to  Everyone:
    #info proxy Sylvain Desbureaux, Orange
06:03:35 From  Sylvain Desbureaux (Orange)  to  Everyone:
    Without typo...
06:07:47 From  Bengt  to  Everyone:
    congratulations Chaterine
06:08:26 From  Catherine Lefevre  to  Everyone:
    Thank you Bengt
06:08:39 From  Sai Seshu  to  Everyone:
    Congratulations Catherine!!!
06:08:57 From  Catherine Lefevre  to  Everyone:
    Thank you Seshu !
06:09:40 From  Paweł Pawlak  to  Everyone:
    congrats Catherine!
06:10:48 From  Catherine Lefevre  to  Everyone:
    Thank You Paweł !
06:17:08 From  Kenny PAUL (LFN)  to  Everyone:
    #vote does the TSC approve the Jakarta release as having met the M1 milestone with the condition that the M1 tasks for the E2E Network slicing use case are to be closed by M2? +1, 0, -1
06:17:13 From  Ranny HAIBY (Samsung)  to  Everyone:
    #vote +1
06:17:13 From  Andreas GEISSLER (DT)  to  Everyone:
    #vote +1
06:17:17 From  bin.yang@windriver.com  to  Everyone:
    #vote +1
06:17:19 From  Magnus Buhrgard (representing ONAP)  to  Everyone:
    #vote +1
06:17:20 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #vote +1
06:17:20 From  Timo Perala (Nokia)  to  Everyone:
    #vote +1
06:17:21 From  N.K. Shankaranarayanan  to  Everyone:
    #vote +1
06:17:23 From  Sylvain Desbureaux (Orange)  to  Everyone:
    #vote +1
06:17:25 From  Bruno Sakoto  to  Everyone:
    #vote +1
06:17:47 From  Catherine Lefevre  to  Everyone:
    #vote +1 - Nice kick-off as Christmas gift
06:18:13 From  Dong Wang (China Telecom)  to  Everyone:
    #vote +1
06:18:27 From  Kenny PAUL (LFN)  to  Everyone:
    #endvote
06:18:50 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED the TSC approves the Jakarta release as having met the M1 milestone with the condition that the M1 tasks for the E2E Network slicing use case are to be closed by M2.
06:34:26 From  Alla Goldner  to  Everyone:
    #vote +1
06:44:35 From  Catherine Lefevre  to  Everyone:
    Thank you so much Deng Hui and Andy !!!
06:44:40 From  Sai Seshu  to  Everyone:
    Thanks Denghui and Andrew, it was a great experience to work with you both
06:44:48 From  Kenny PAUL (LFN)  to  Everyone:
    #vote does the TSC accept the results of the Modeling Subcommittee nominations as sufficient to certify Xu Yang and Chuyi Guo as new ONAP Modeling Subcommittee Co-Chairs? +1, 0, -1
06:44:50 From  Andreas GEISSLER (DT)  to  Everyone:
    #vote +1
06:44:51 From  Magnus Buhrgard (representing ONAP)  to  Everyone:
    #vote +1
06:44:55 From  Timo Perala (Nokia)  to  Everyone:
    #vote +1
06:44:55 From  Ranny HAIBY (Samsung)  to  Everyone:
    #vote +1
06:45:00 From  Sylvain Desbureaux (Orange)  to  Everyone:
    #vote +1
06:45:01 From  Bruno Sakoto  to  Everyone:
    #vote +1
06:45:02 From  Sai Seshu  to  Everyone:
    #vote +1
06:45:02 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #vote +1
06:45:10 From  Fernando (Fred) Oliveira  to  Everyone:
    #vote +1
06:45:23 From  Dong Wang (China Telecom)  to  Everyone:
    #vote +1
06:45:24 From  Catherine Lefevre  to  Everyone:
    #vote +1 and congrats - we look forward to hearing from you both soon !
06:45:28 From  Alla Goldner  to  Everyone:
    #vote +1
06:45:39 From  Kenny PAUL (LFN)  to  Everyone:
    #endvote
06:45:41 From  N.K. Shankaranarayanan  to  Everyone:
    #vote +1
06:45:59 From  Xu Yang  to  Everyone:
    Thanks Deng Hui and Andy for the hard work!
06:47:04 From  Sai Seshu  to  Everyone:
    Congratulations Xuyang...
06:47:25 From  Xu Yang  to  Everyone:
    Thanks :-)
06:47:54 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED the TSC accepts the results of the Modeling Subcommittee nominations as sufficient to certify Xu Yang and Chuyi Guo as new ONAP Modeling Subcommittee Co-Chairs.
06:48:05 From  Chuyi Guo  to  Everyone:
    Thanks the community, thanks Hui and Andy, it is happy to work with you.
06:55:43 From  Kenny PAUL (LFN)  to  Everyone:
    example of that was Fiachra's request to archive the dmaap/mirroragent repo as being no longer maintained.
06:57:27 From  Kenny PAUL (LFN)  to  Everyone:
    DMaaP is still an active project but the repository isn't being maintained any longer.
07:28:06 From  Kenny PAUL (LFN)  to  Everyone:
    time check
07:34:00 From  Amy Zwarico  to  Everyone:
    Chaker - THANK YOU!!!!!!!!!!
07:34:24 From  Ranny HAIBY (Samsung)  to  Everyone:
    Have to drop now. I assume the MAC update will be pushed to next week?
07:34:37 From  Chaker Al-Hakim - (Data only)  to  Everyone:
    Of Course, YW
07:35:44 From  Amy Zwarico  to  Everyone:
    so great that it builds on existing process

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. 

06:03:11 Hey, transcripts on Thank you.
06:03:15 Mo.
06:03:21 And as always, I need to move that out of the way, otherwise I can't see.
06:03:28 So on Thank you.
06:03:40 If I could get a volunteer to run the.
06:03:44 They keeping.
06:04:02 wake up this morning, I go, I'll do it. Can you hear me Thank you.
06:04:12 Okay, there you go, sir.
06:04:16 And as always, we will start off the meeting with our administrator via
06:04:28 recording, you're muted when you come in please stay muted unless you're talking.
06:04:33 If you're on a phone you can use star six if you happen to send me a private chat message, that's great, but it will become part of the public minutes when I cut and paste them into the wiki.
06:04:45 And as always, we'll start off by mentioning our anti trust policy notice this policies important or we've got multiple projects, multiple companies participating in these project meetings.
06:04:55 Please review it. If you have any questions, your contact your company's legal counsel and members of the lF may also contact Andrew up to grow the firm gives her up to Grove LLP which provides legal counsel to the Linux Foundation.
06:05:12 Stop share and share this.
06:05:19 Okay, I'm
06:05:23 run through a few things here.
06:05:26 First, we've got information on CSC elections, got released status information.
06:05:48 We have a request for
06:05:54 confirmation of election for the subcommittee modeling subcommittee.
06:06:01 Marketing update from rainy and Brandon, and then talk about awards and upcoming stuff so we got a number of different things on the agenda today anything needs to be added.
06:06:22 He can he could wanted to shocker so if we have a few minutes I could give some update on where we are with the architectural reviews for the art and release.
06:06:33 Right.
06:06:35 Thank you.
06:06:58 Artist. How about status.
06:07:02 So first things first.
06:07:04 Congratulations can Catherine's been reelected as Chair for this upcoming year. Congratulations.
06:07:17 So thank you, Kimmy and thank you for the DNC members for the test of confidence and really energized to kick off next year, with RTC priority that we define and I've set up a slot by request to slug during the PDF event, no depth to the assets that we
06:07:42 wants to move forward with the new elected DSC with a priority which was defined on this year for 2022 so again thank you for your vote of confidence and are really looking for what to kick off the new years with the priority that we will leave you and
06:08:01 I'll be fine. Thank you so much.
06:08:06 We'll be kicking off, Vice Chair election.
06:08:12 Now, since we are rapidly rolling into the holiday season for a good chunk of the world. We will wait until after the first of the year to actually finalize that so I will give it several, Several weeks
06:08:32 for input there for out of fairness.
06:08:38 So be looking for that.
06:08:42 And next thing is, Fred you had send a mail, indicating that you are going to be retiring from Verizon at the end of the year.
06:08:56 Is this outright retirement.
06:08:59 Or are you on to other challenges.
06:09:03 Go yeah thank you yes I am retiring from Brighton, it's a least a first retirement, no current plans to be somewhere else but I actually even in retirement hope to do some contributions to own happen so I plan to at least the semi active in the community
06:09:27 and actually maybe more active and since I won't have any other pressing costs at work.
06:09:44 Okay.
06:09:37 There is no requirement for you to step down as long as you retain your statuses and active community member. That is totally up to you.
06:10:02 Thank you. Also, at least, continue for the nearer term and I'll advises.
06:10:01 If my statuses is changing.
06:10:02 Okay.
06:10:05 Just use your body to do whatever you decide, Fred we are really happy to have you on board, because you have been significantly, helping us to focus on the C word alignment with the owner community, and even beyond so I hope you can still stay with us.
06:10:23 Let us know. You're still double that. But we definitely eager to keep you as part of the community if you can. Thank you so much.
06:10:34 All right, Thank you very much.
06:10:56 Okay.
06:10:59 Next up, then release status.
06:11:04 David, I will turn it over to you.
06:11:06 Okay.
06:11:08 Thanks Kenny.
06:11:15 So let's just start off by refreshing our memory about the Jakarta schedule.
06:11:26 So we kicked off back in October.
06:11:31 And one it was originally scheduled for December 2, and we go the TASC agreed to push the milestone out one week to today.
06:11:45 The remaining milestones stayed the same. So, I'm to through sign off are still what the TLC originally approved sign off. In May, as originally plan so those have not changed.
06:12:01 But here we are on December night.
06:12:05 So let's take a look at status. So, the, we still had quite a few unresolved release management tasks. A week ago. But those have come together very nicely this week fact I think as early as, maybe late Monday or Tuesday.
06:12:30 All of the project, release management tasks were completed so we're 100% there with the requirements.
06:12:43 We, we have this odd situation with our requirements and release management task for requirements. And I'm planning to bring this up in the retrospective that we do at the developer and test forum.
06:13:03 In January, so you might put some thought into this and and bring your ideas to that session.
06:13:12 But what happens is that, because we continue to accept requirements for the release up through him to.
06:13:19 But we still have release management tasks for requirement owners for em one, what can happen is that I go through and publish the tasks. And then we have some new requirements that come on board and then I have to go back and add the tasks for those
06:13:35 requirements.
06:13:37 And in fact that that happened.
06:13:40 We had about five of those. This week, and
06:13:47 you know credit to to Henry, you and Oscar mom for, even though I just assign those tasks at the start of the week they they got this done.
06:14:03 However, we do still have one requirement, and this is a continuation of the end to end network slicing requirements requirement.
06:14:18 And as you're probably aware, the leadership of that use case is, is changing. And, In fact, we're still looking for a new lead.
06:14:32 But
06:14:36 we were told that the team that's working on the use case does want to provide some, some more add ons for Jakarta, release, even though they're, they're currently without a lead.
06:14:53 So, just yesterday as a matter of fact I created a new requirement for Jakarta for the
06:15:01 network slicing use case and as a result, we do still have to tasks.
06:15:10 Outstanding I actually this is more like one because I sent mail to Shukor and already received a.
06:15:23 a.
06:15:25 That will, or, sorry.
06:15:39 We're, we're more or less complete.
06:15:43 In my opinion, with am one. And so what I'd like to suggest is that I'd recommend that the TASC go ahead and approve am one with the condition that the MR tasks, or the end to end network slicing use case be resolved by him to.
06:16:07 So that's, that's my recommendation. Any questions, comments.
06:16:19 All right, can you do we want to do a vote for him one that I'm typing it up right now. Okay.
06:16:42 Okay. Does the TSA approved the Jakarta release as having met the M one milestone with the condition that the M one tasks for end to end network slicing use case are to be closed by him to.
06:17:00 Okay, and copy and
06:17:07 paste away boat is in the chat.
06:17:50 And that's all I have for release update unless there are any questions.
06:17:48 The vote, another
06:17:52 couple of seconds here.
06:18:05 Okay, I'm going to close this.
06:18:08 Maybe just a reminder, so the next milestone for the team will be on 28th of January, maybe you said, I missed it sorry.
06:18:19 Yeah, we talked about that right at the start. It's actually the think it's the 27th.
06:18:27 Yeah, January 27
06:18:32 specification freeze, so that will be our next milestone and chucker will be working around the clock to complete all of the reviews for me to, no doubt.
06:18:53 I don't know if I'll be working around the clock. Of course you will.
06:19:02 All right. Any other questions.
06:19:08 All right, thank you.
06:19:15 Thank you, David.
06:19:19 On the share screen pop back over to that.
06:19:27 Okay, so we've got that is having been done as Catherine says nice Christmas gift.
06:19:38 Phone. Next up, we've got our
06:19:44 range information.
06:19:50 Any, any upcoming migrations or, or tickets or anything waiting for
06:20:00 status, other than the one we hear from for car for bellinge banked just know my gracious plan, however that I was looking at that need to see approval ticket.
06:20:31 As far as I understood I believe PDFs are approved already to to manage their code right that, that is, that includes also the abbreviation of branches.
06:20:34 So I just wanted to make sure this this ticket is good to go.
06:20:43 Yeah, so this is a,
06:20:49 this is for the mirror agent repo is going to be made read only repo being made read only means that there is will be no other updates being made to it.
06:21:05 So anything that is dependent upon that will not be maintained going forward so that is the.
06:21:14 That's the topic there so
06:21:20 just need the TLC is awareness and.
06:21:24 Okay.
06:21:28 I can, I can let me know.
06:21:31 Other than that, there's no, there's no other upcoming migrations.
06:21:38 No one has an objection I'm going to mark that as agreed.
06:21:51 Okay.
06:21:58 Next up, Umh lab.
06:22:03 This is where we are setting up the hardware that's donated by Intel
06:22:12 folks might be aware of this kind of minor issue we have around the globe about supply chain.
06:22:21 That's been impacting us so that's the ship date is scheduled for December 17.
06:22:29 This means that the hardware will be set up shortly after the first of the year because we don't expect anyone other to be doing anything other than receiving the hardware and taking it off the loading dock.
06:22:43 Between now and then.
06:22:45 So shortly after the first of the year will be set up with the help of rent Wind River and.
06:22:53 Once that is done, we will start migrating sources, off of the Intel Wind River lab, as quickly as possible after the first of the year so this is something for the community to be aware of.
06:23:13 I'll drop a note, the same note into the, into the that PTO meeting for Monday.
06:23:20 Yes Give me and I was wondering, maybe it's too early.
06:23:23 But when we have details about the plan because I don't know if it is like shifted back set up all the lab, and then commissioning the formula, it will be a straight cut to smooth transition.
06:23:41 So any information we can share with the PDL about the plan, so they can assess and the impact on their ongoing really nice.
06:23:54 Yeah.
06:23:56 The.
06:23:59 We do not anticipate a red switch cut over we anticipate moving resources, one by one.
06:24:08 So, that much I can pretty much assure you, but beyond that.
06:24:13 No, we haven't really fleshed it out I would say, okay, and it's I it's there's no possibility that you keep learning, even if you migrate stuff to the new lab.
06:24:25 So there is no intention of services.
06:24:32 That is very much a possibility.
06:24:35 Intel is impacted by the
06:24:44 Intel's impacted by the exact same supply chain issues that we are with getting the new hardware so they don't have anything.
06:24:55 Currently, on deck to backfill.
06:25:01 The space that's being vacated by our own app, which is one of the key things that that they want to do so, we do anticipate there being some level of running these in parallel.
06:25:13 Okay, understood. I understand.
06:25:20 Thank you so just keep us informed the best you can. So the feature can assess the impact on their activities. Thank you. Yep.
06:25:28 Okay. Anything else real Andrew infrastructure related.
06:25:38 Okay. Um, so going on to community updates wanted to point out this nice
06:25:50 this nice blog post on lF networking by Nicholas creamy who was the intern that was helping us out, do some of the work related to mapping the
06:26:09 mapping the architecture navigator, and read the docs.
06:26:16 And that so I wanted to point that out Nicholas, I know that you've been, I saw you joined the call earlier so I want to thank you for for that I think this is a nice, nice representation here for the own app community in the in the mentorship Prague
06:26:50 program, did you want to say a couple words.
06:26:52 And I think I don't know much, just express my gratitude for the opportunity to enter me the community. I'm really grateful.
06:27:03 You're welcome.
06:27:06 So thank you for that,
06:27:13 thank thank you Nicholas because I didn't have a chance to look at your blog but I will definitely do it, and I really appreciate the fact that you took the time to express your experience because it can benefit for future mentees so thank you so much
06:27:33 for also all your contribution this year to do in our community.
06:27:49 Um. So a couple things here that we've got, which is going to of course be relevant when we start talking about on a main came projects immediately next.
06:27:59 Steve Stark who has been providing us, who is stepping down as the ppl for vvp appreciate his work there. There have been no nominations to backfill.
06:28:15 So, We have a gap there with vvp travel love it in a similar situation is stepping down from being the ppl for Vf requirements.
06:28:29 There are no nominations from the committee base to backfill that PTO position so we have a gap there for Vienna requirements.
06:28:41 The question then becomes where do we, where do we either move or or how do we otherwise handle
06:28:50 vest best, the best certifications. If we do not have someone kind of leading that area.
06:29:07 Also we've had a change in India in which slicing leadership.
06:29:14 That was previously announced.
06:29:19 And this is an area that's obviously have some concern to a great number of us.
06:29:29 Since end to end network slicing is one of the key elements that things like five g super blueprint is is looking at, and some of the things that we've got in the in the enterprise space and in that so I know we spent some time talking about it yesterday
06:29:47 Catherine.
06:29:51 What would you like to say here.
06:29:54 Yes we do so.
06:29:59 Yes, we did. And there I fully aligned with what you said and we might also cover the two other items as well but since you asked me the question about this one.
06:30:08 I totally agree. I think this use case is from them on done for the money decision of own up because remember we are not only using on up today for network automation.
06:30:20 We are also a positioning own up as part of the service management and orchestrator for all them, and I know I've seen it in action on it, I'm working on it.
06:30:31 And finally for the enterprise business, it's crucial to have network slicing to define the bandwidth, and even more so having no lead in this position is really a major concern that I want to go to all of you, we absolutely need to have a lead that before
06:30:51 the M to have jack after. So, I hope the Christmas time the new year will help you to think deeply about that, because that's really fundamental from my perspective.
06:31:04 In the interim period, I want to thank you in advance ala Shakur, and also David to keep the whole, the ball rolling.
06:31:14 Because we have already submitted the requirement because we have people wants to contribute.
06:31:21 But who do, who does not have the bandwidth to lead. So it's the continuous issue that we're facing.
06:31:28 And definitely for the contribute yesterday's lead that will become one of the topics I want to discuss when we talk about the priority next year with the TLC, but back on this particular topic.
06:31:44 I will launch a call, again, via TLC. This call is to discuss for her leader, somebody who have already expertise, but we need to find a solution. Otherwise, I will need to escalate that to the board, because as you remember the boat was really keen that
06:32:03 we keep going on of Enterprise Services strategy as well.
06:32:09 So, have some song during the Christmas time, or do I really want you to enjoy the time with your family, and then early January, we really need to have a decision so we can have everything in place for the two.
06:32:25 And since, David. Remember, twice today the date of the two is January 27, so does the deadline to conclude on that.
06:32:37 Any particular feedback from the DNC at this stage or anybody else, any interest so far.
06:32:43 Yeah, I think every time we look for ppl volunteers I feel I have to remind the soul that we had an initiative to make the PTO role more lightweight and just to be honest, I'm not sure where we stand and I'm not sure if there's a new definition and if
06:33:00 everybody's aware of before we call out for volunteers.
06:33:04 Maybe people think that job requires more than it actually does so.
06:33:12 I mean how can we make it clear to potential volunteers. What is the scope of what we're asking them to do.
06:33:20 I think, in the context of the energy and i i think it's a topic that we also discuss with Kenny and David, but we think, probably a task force need to be set up to also explore, because if we compare what we did for the Amsterdam really is up to the
06:33:41 movies a lot of processing improvement, a lot of workload has been removed from the ATL as best as we could, but it doesn't means we didn't explore all the possibility.
06:33:56 So I don't know if somebody took the action to, I had the action to pull up the old list and I started going and looking for it.
06:34:06 Last week, and got distracted and didn't get back to it so I do know that that information is out there I just need to go find it.
06:34:18 Yes So doing the DDS on me. It's possible to review. I would like that we don't define your lead to the hive, this review, if people do not know today what it means.
06:34:30 It means that they can look at the milestone definition as a CD to use case lead. Because what we are looking for the moment it's a use case lead, but it's, I recognize its startup, to understand the whole, it might not cover the fact that the use case
06:34:51 lead me probably to set up a call per week with the impacted BTL to understand where we are.
06:35:14 One was to give you the 2020 to not necessarily tackle that one in particular, but at least try to notify somebody was willing to move us to the next steps to look at everything, do a concrete definition, in addition to what David stuff to implement an
06:35:38 answer to your question really a hottie.
06:35:41 So it's not forgotten, either.
06:35:50 It's in the list, but I don't think anybody have stepped up yet to the live to a new definition.
06:35:55 Yeah, I'm volunteering to take part in this.
06:35:59 I've never been a PTO, but I've heard horror stories from other ppl so I'm now to take part in documenting it I think OpenStack had are still has a good kind of somewhere in the wiki definition of what are the roles and responsibilities of a BTR and what's
06:36:16 what's expected so I think we should have the same.
06:36:20 You always think we have so far it's in the DC chest but honestly might be light, right, it's a high level definition so we're the TASC Jeff can be announced.
06:36:32 With additional headphones and but the goal is not only the definition itself, I believe, is to understand what this that we have not yet though can ease the life of the pitch and can we for example we speak about one PTO.
06:36:48 Can we for example we speak about one PTO. Some of you bring about previously, maybe we can ever be to be the purity of all we split the tasks between multiple people.
06:36:59 So we split the workload. So there are a lot of option but until we have a concrete plan.
06:37:03 I totally agree.
06:37:05 We cannot move forward so that's something first of 2022 object
06:37:13 shocker So, back to the point that ronnie just made right so cold lead or vice chair
06:37:24 or whatever you want to call it. Right. Copy deals. Yep. Maybe an option, a viable option and the reason I say this is the modeling subcommittee has had to co chairs since its inception.
06:37:41 Right, so would be helpful to solicit their feedback from Dunkley as well as Andy in trying to see whether this model is something that can be applied to the PDL positions.
06:37:58 And I would like, even to extend the shackles to use case lead as well because today we are discussing about the use case lead but anybody who is in a leadership position.
06:38:09 If they can have a single person working with the person coaches who lead whatever that might mean at as well. So everything is open. I mean, you know, for openness in this community.
06:38:24 What we need to establish was the best for people. And I'm sure we will find a solution.
06:38:32 Coding culture, yeah.
06:38:47 Any other feedback regarding that. Otherwise I really invite you to join us at the Ddf event for the TC, we might not have an answer, but at least we will determine who can work.
06:38:56 And on this division and also composer.
06:38:58 To facilitate the picture so I really invite a bj to join us as well at one point in this task force.
06:39:21 And maybe they pitted tonight's terms we should also share with the, the PDL on Monday, and the use case so t mo and Allah, please start to also collect feedback from the V Kaufman subcommittee because the use case read somehow belong to this community
06:39:33 subcommittee.
06:39:45 Yes gone Katrina.
06:39:48 Thank you all.
06:39:53 So
06:39:56 I know that this next topics and for already kind of diving into it.
06:40:02 And I hate to shift gears a little bit.
06:40:05 We do have some business to take care of that I want to make sure it gets done.
06:40:13 If that's okay Catherine, and that's to
06:40:17 the discussion of the CO chairs for the subcommittee to make sure that that we get that taken care of and then, and then we can perhaps go back to the topic of London maintain projects.
06:40:32 Sure.
06:40:33 Because I know what we should have started because the team is in China.
06:40:38 We should have started with this topics, because it's already late for that. Sorry.
06:40:44 Well, for the
06:40:48 modeling subcommittee.
06:40:53 The call for elections went out there were two nominations only. And as Shakur just noted the subcommittee for modeling is me his leadership is a co chair position so there are two candidates for two seats.
06:41:13 They are requesting that the TLC certify the results of the nominations as being definitive, and except Zhuang in three go as the CO chairs of the subcommittee we've done this before, with other some of the other subcommittees where there have been no,
06:41:42 there's only been a single or two nominees for two seats.
06:41:46 So that's there I will
06:41:51 open it up for a brief discussion. If not, I will dump it into the chat window for a vote.
06:42:00 The only thing that I want to add it. Thank you soo. Thank you, Julie. I hope I see your first name correctly, just to step up and continue to energize the motherly instinct committee.
06:42:14 And in addition, I want to seize the opportunity to Thanks Dan we and on the mayor.
06:42:19 They have been driving the subcommittee, the motoring subcommittee since the inception, and the also helping us in different domain. So thank you again for them we and on the for all the work they did over the last four years, four years plus now.
06:42:39 So maybe we could add a notable them as well.
06:42:45 Okay, thank you, Catherine.
06:42:49 I think yeah we have been, I have been working here for four years.
06:42:54 I think I was still to help the modern subcommittee.
06:43:00 And I'm still working on our modeling topics in the standard and, together with open source I try to contribute for the telecom, and to move into a Unified Modeling and together with open source.
06:43:17 I think that is a bright future. So I hope the young generations, they can, they have the opportunities to to catch this opportunity to help on that, and to grow together I'm also Thanks, Andy, and we're honored to work with him.
06:43:36 He gave us many past experience. I learned a lot, so thanks Tanya sphere.
06:43:38 Six able to
06:43:41 Thanks able to say the same thing we thank you so much. It's been an honor to work with you and a pleasure to work with you. And I believe that we're leaving the subcommittee in the best hands possible.
06:43:51 Both Sue and Julie have had extensive experience and, but a number of the specific modeling activities. So I think they'll, they'll do an outstanding job going forward as well.
06:44:03 Thanks again.
06:44:05 The ending dunk we thank you both. But there are other openings if you're if you're interested,
06:44:20 under consideration.
06:44:23 Yeah, thank you both. It's been a pleasure working with you guys.
06:44:32 Thanks.
06:44:30 Me too. Thank you for today, I'm going to go ahead and drop them into the chat window.
06:44:38 The tsp.
06:44:38 Except the results of the modeling subcommittee nominations is sufficient to certify. She wing and chewy.
06:44:50 As a new own app modeling subcommittee co chairs vote is in play.
06:45:30 giving another 10 seconds.
06:45:41 And congratulations.
06:45:46 We have new co chairs of the modeling subcommittee.
06:45:55 So that business done.
06:45:58 Catherine assume you'd like to turn our attention back here.
06:46:03 I'm your skinny is.
06:46:20 And I have been a couple of meetings, set up to move in the right direction so I look forward to hearing what other conclusion of the team to the TLC
06:46:22 everything. So I was looking for tomorrow
06:46:26 on call I do not see him on still on sickly still out okay.
06:46:38 I can address some of these topics, Kenny. Okay.
06:46:45 I'm going to skip the first two because those are primarily Thomas, and hopefully we can pick those up that later date.
06:47:01 And actually I did want to mention, since I can never get Shakur to respond to my email I'm going to just ask him in the scene is this meeting, if there was a request from our group that's looking at a maintain components to have you attend our meeting
06:47:25 on December 13. If you're available, which which meaning meeting is that this is the ad hoc meeting that we set up to talk about dependencies on unmaintained projects.
06:47:41 And I say, it's 8am Pacific on Monday and I can, I can send you an invitation.
06:47:47 If you could do that unless you might have missed your earlier email sorry. Yeah, yeah, we'll do.
06:47:55 I'm just giving you a bad time.
06:47:58 And that's okay. I'll talk to Santa Claus.
06:48:03 And then, so our group has met twice now to talk about managing a maintained projects. The situation is that, you know, we've done some work around Lifecycle Management.
06:48:25 So, in other words, we created this life cycle state called him and maintain project. And we've defined, how a project moves from being active to unmaintained and, and even if we want to revive a project, bringing it back from unmaintained to active.
06:48:44 But what we haven't really talked about which is an ongoing concern is the dependency, that are active projects have on a maintained projects.
06:49:03 And
06:49:03 in discussing that in, you know how to resolve it. One of the conclusions that we came to is that we really need to have a better understanding of what the dependency relationships are
06:49:21 not just at the project level but actually down at the repository level. And so I was asked to, to share a proposal with you, and can he can I share.
06:49:43 If I had, I had stopped sharing thinking that you're going to pick it up and when you did I just went back sorry. No, no problem.
06:49:53 So, so the proposal to the TASC is that don't have project, develop an own app repository dependency graph.
06:50:07 So as I mentioned, We believe that in order to work effectively and efficiently on this issue of dependencies on maintain projects, we need to really have an overall an overview of the dependency relationships across all now.
06:50:30 And again, as I said earlier that is not just at the project level but actually at the repository level.
06:50:39 And we believe that this would provide a number of benefits
06:50:45 to the point that we're discussing it would allow us to understand the, the impact on active projects when we have projects that move to a maintain state.
06:50:59 It would also allow us to track dependencies from release to release.
06:51:05 So as we identify dependencies on that maintain components. And then those get resolved by maintaining a graph of dependency relationships, we would be able to track those changes from release to release.
06:51:27 We also think that this would be helpful to end users to understand what the dependency relationships are, and so it would provide greater transparency there.
06:51:41 And then in general, it would also provide a greater insight for the community into own app architecture at the repository level. And this is something, obviously, in order to be effective would not be a one time, effort, but it would be something that
06:52:00 would need to be updated for each release.
06:52:07 And I just want to check.
06:52:10 Amy.
06:52:13 Did I cover that pretty well Do you have any additional comments, thoughts about that. Yeah, just, you did a great job. Thank you so much.
06:52:22 We really, we really don't understand the impact of these unmaintained projects. So, what we, what we would also like to do is for the the Jakarta release, get an audit of this we do need long term this dependency graph, but right now for Jakarta, we
06:52:42 need to just understand the impact of the currently unmaintained project so kind of a smaller scope for Jakarta as we try to solve the bigger problem, because right now we do have on maintain project, we know that some of those specifically portal are
06:52:58 actually are required in order for the applicant for an app to run correctly. So we do want to do that.
06:53:07 scoped down audit based on the currently unmaintained projects for Jakarta.
06:53:15 And we need help from the TSA to get this moving forward.
06:53:24 Yeah. Maybe one, one question related to da which is just really clear to me the, the level for the dependency. I mean, what is the difference between reference level or project level two, I mean maybe if one component as a dependency on the other.
06:53:46 If, if one project goes and maintain maybe it can be it can have an impact with.
06:54:08 Would it be more at the component level or project level and maybe there is no dependency as the repository level, what is the dependency at that request to switch to a level that.
06:54:04 Certainly, that's a good question. What we have discovered is there, there actually are just repositories within a project that essentially go dormant, oftentimes what happens is they they have been the project has been refactor or that feature has been
06:54:21 determined by the project team to not be not be necessary anymore.
06:54:27 And that's why we do need to ultimately we need to know to know the dependencies at the rate at the component level, so that we, so that we can understand when a project team does refactoring, how does that impact other project to other projects who may
06:54:46 have had a dependency
06:54:53 layer.
06:54:53 It could be a team that you what the impact could be really at the component level right. Correct.
06:55:00 And, and then should it be more at this level that the the dependency should be made.
06:55:10 Instead of at the repository level, that's, that's a good question. I don't know the answer to that probably something that we need to look at more.
06:55:21 Certainly, you know the, what we've started with, is that we, we really believe that it's got to be at least at the repository level, if not lower, but it's probably not sufficient for to be only at the project level.
06:55:39 Yeah. Very good.
06:55:56 Very good. That's my been good yeah maybe after positive or maybe give an overview but in the detail when, When a component is refactor it more, maybe you're at this level that we could see the impact on other component.
06:56:01 Yeah.
06:56:01 Can I put a comment in the chat other other good examples, can you could you could you elaborate on that please because it is a very good example. yeah I was still typing there.
06:56:13 So, we had the request earlier in the meeting today, where for Kira was asking to archive the de map mirror agent repo.
06:56:25 So this is no longer being maintained by the team.
06:56:29 The map is in extremely active project is as folks know.
06:56:34 But that repo and the components in that repo we're no longer going to be maintained.
06:56:40 So if there are dependencies that other projects may have on components in that repo.
06:56:48 That needs to be highlighted, either someone needs to pick up the responsibility for me, maintaining that.
06:56:56 Or, it needs to be refactor two out of whoever the code from whoever is consuming that.
06:57:09 At least I could also imagine if you have a component, let's say kind of client libraries which might have might be used by other components.
06:57:20 Therefore, of course, that would be a dependency.
06:57:25 But on the other hand, of course it did come, let's say the complete component will be wiped off or let's say put to maintenance state, then usually all the dependent components should not use or do not need to use the client library anymore but this
06:57:40 is exactly I mean, the complication in that way of dependencies that's right now.
06:57:46 But that's definitely you have runtime dependencies that's clear. I mean if you ever use then whatever, for example now.
06:57:55 Ms B's or maybe a good candidate who has really a dependency on MSP.
06:58:02 It's not absolutely not clear to me so maybe some are pushing their their interfaces to MSP but who is actually using MSP Can this be, let's say changed and to the dependency can be removed all the stuff in my opinion is, let's say more kind of runtime
06:58:19 relationship, but as you said so there could be also on repository level dependencies like libraries like agents or something like that. That's right.
06:58:30 And maybe your toys, we have, because I went back to the different repository and looking at them maybe we have open I think we have one repo PR component if I'm looking at AI or maybe ups that.
06:58:46 And, and then I think it. Yeah, with this.
06:59:05 So, yeah, yeah so brand now the reality is that if you go out and look at if you go out and look at as we're building things.
06:59:14 We have about it, we wind up with about 180 things in the Jenkins jobs that are built.
06:59:22 And I don't think that that's just at the repo level I think it's, it's, I don't think that the repo level is just at the project level, I think it's, it's much finer grained on that.
06:59:34 We do have a practical problem that we need to address Barrett we need to address in Jakarta.
06:59:41 And that's what we're trying to bring to the community, the practical problem is we have read those that are no longer maintained.
06:59:50 You know we have components of of projects that are no longer maintained by the end full project. We also have. We also know that some of those actually have to be included in a build in order for them to even work.
07:00:04 And we need a path forward, and the first part of this is to actually figure out from it is to have is to get help from the TSA and figuring out for the things that are currently marked on maintained.
07:00:19 What is the dependency.
07:00:21 So what doesn't need to be included in a release, and what does need to be included in a way because that is no that is really not clear. And it's not clear in our documentation and it impacts.
07:00:33 What we can say about the maturity level of the on App code, we shouldn't be included we shouldn't have dependencies in it on on maintained code.
07:00:49 Know make make sense, I think it's fair to add to
07:00:54 the adding the dependency to be able to answer this question, and talking on the political level
07:01:02 could tell, I think I don't know what. Yeah. What do, what do we think also thinking.
07:01:21 Right. Thank you.
07:01:23 Any additional questions, comments about this topic.
07:01:30 Yes. So what are the next steps.
07:01:41 I'm sorry, go ahead.
07:01:56 And next steps here is we need to guessing we need to take the next steps because a concern has been raised initial analysis has been made.
07:01:54 And it would be nice to talk to next steps.
07:02:00 Okay, you started to talk about the next steps.
07:02:04 Yeah, so I had already reached out to release engineering to find out if there's an easy way to get a report port for
07:02:16 things like there's, there's a couple aspects of this one. One is, is that we can we can probably get the dependency tree we get that built from the s bomb list in some fashion.
07:02:30 So that needs to be done the other.
07:02:35 I started to jump ahead on on other aspects of the whole unmaintained project management, but let's, let's keep it limited to the topic at hand, which is, we need to do some, some manner of audit here and get that out so figuring out how best to extract
07:02:57 the information is what needs to be done.
07:03:05 I'm going to kind of put banked on the spot here a little bit.
07:03:12 Is there a way to easily build a dependency tree or should we be looking.
07:03:21 Should we be looking towards the S bomb and and trying to build it from there.
07:03:32 came to my mind. So I will just have to delay answering this one.
07:03:40 Brenda.
07:03:42 Yes. Something else that came to my mind about. So I don't know which is the tool that you are planning to use for these that for a dependency perspective, is it also more at the Jenkins level maybe if there is a refactoring in.
07:03:57 In one repo what how it could impact other repo but more for Jenkins will build perspective. Are we also looking at dependency more functional dependency I mean, component that need to use an another component and this component is duplicated it could
07:04:15 have been also a functional impact with it, both kind of dependency or on the in the old one.
07:04:26 Yeah, it is. It is both dependencies, and when I said well I started to jump ahead a little bit. When I was jumping ahead to was actually.
07:04:36 And then we need to look at the build dependencies with regards to Jenkins. The first of all, the first the first, and primary concern is where the functional dependencies.
07:04:50 Obviously, then cleaning up the Jenkins jobs and things like that are are an area where we would need to do work. I, and I had reached out to rail inch to find out if there's an easy way to get a report of the Jenkins jobs that are still trying to run
07:05:08 that have been failing for a period of time.
07:05:13 And there isn't an easy way to do that.
07:05:17 There's been a couple of requests to do some capturing of that, that have been that have been, not by us but but kind of a in a general sense that have been backburner due to other priorities so I'm already in conversations with regards to the.
07:05:41 The Jenkins piece of that being a process gap.
07:05:46 Okay. Yeah, so it's both. Bill and also running, running the pennant to so that we are interesting and maybe the running one also will be quite challenging to maybe to have to list all of them Yes, the running one.
07:06:02 Yeah, but maybe, maybe, maybe it was to be the question but if there is no change and do good for, let's say six months is, what is the point to run the Jenkins jobs, maybe it's easiest is to to list.
07:06:21 Also, he posed that. No, no changes in the lag staff expenses and see what does a Jake and jobs for named every day or I will weaken the sleepers and to let them know.
07:06:31 So so so van, one of the reasons what the, if nothing has changed in six months.
07:06:37 Things like Nexus IQ, the reports actually will change as new vulnerabilities are found in existing packages and new versions come out of, of things that they include so there will be changes in in some of the reporting.
07:06:53 Even for even for a stat, even for something that doesn't change.
07:06:59 Code wise, so that that would be the difference.
07:07:02 Maybe I'm
07:07:12 Maybe I'm, I'm too busy misty but they give it to us as be no changes in the last six months or when you, even if there is something that is next you say series three during a new vulnerability, there won't be maybe anybody was looking at it so well.
07:07:22 A true.
07:07:25 But, Yes, I would agree on that.
07:07:29 Partially.
07:07:32 So, I'm saying that if the code is being if Jenkins is running against code which is not being modified, and that code exists in an active repo, and an active project.
07:07:49 Why wouldn't we continue to run the Jenkins job for the build.
07:07:53 That's what I understand, with way which, if, if something, if, if a repo has been archive.
07:08:00 Okay for repose been archived, we aren't going to be doing anything to that period.
07:08:05 So from that perspective I can understand. We should just, you know, get rid of the Jenkins job, but for another one that's building dependencies that may be a use case may be dependent upon
07:08:21 it to Amy's point. If there's a new CV that gets raised.
07:08:28 And that should be flagged. It is it possible that there is no one within that project that would be looking at that code. Absolutely.
07:08:38 But if it's an active project, and an active repo.
07:08:45 My personal feeling and obviously I'm not, I don't have any skin in the game here but my personal feeling is that that that should be run, just to protect against regressions.
07:08:58 I agree with you, Kenny, and typically and because of the way we do JIRA tickets for for upgrading vulnerable packages, we get the, the, the truly active projects are very good about providing feedback and saying hey I don't use this repo anymore.
07:09:15 Hey this is no longer part of the repo.
07:09:19 But it's or no longer part of my project at deprecating it or yes I still use this. So we do get feedback we.
07:09:29 Let's just say, 80% of the projects are really good about doing that.
07:09:34 So I think we need to read appreciate all the feedback and all, all the discussion here. and I've tried to put some words concerning the next step based on what has been discussed, and you can define the proposition, but I think what it is fundamentally
07:09:53 still some repository which is Mark still open one day should be archived because nobody used up.
07:10:04 And then from a functional perspective, we can use this case, but from a functional perspective, I would like to invite of Master, meaning by that the architecture team will have a good taste of the overhaul of owner, and the requirements should committee
07:10:20 in committee to work together, and to establish with the impacted project, right, but kind of Proposition. So the proposition could be.
07:10:31 We need to move to an adaptive, and I just sees sees an example crossing my mind so as we know it's an authentic project. We had the service mesh as a pass.
07:10:47 It's something we need to push at one point right so. So, it means doing either that deal.
07:10:57 Or can we leave with all that, and then instead of having it maintain its to shoot two guys. So that's the tribe of first analyzes that I would like to suggest to you as a next step so I don't know can if you can still share your screen, because we lost
07:11:14 your screen.
07:11:18 So an ideal not diff of music was at that point etc so you see that's what I mean.
07:11:25 So, the proposal, we need to find an ideal motive.
07:11:31 Fine,
07:11:36 or need to move on and mentoring, guys.
07:11:47 I don't know, there may be other opposition.
07:11:52 Right. But, but I think we need to do an assessment with some pre work.
07:11:58 Johnny made by architectural e commerce of committees. When we have the list of impacted projects. Right.
07:12:07 Right. So the first step though Catherine is we have to get the impacted project, we have got to go through and do that audit every project has to raise their hand and say, whether they do or don't use anything in the unmaintained projects.
07:12:24 And that's the that's the absolute first step we need and we need to get the projects to cooperate with that and figure out how to get that done. Yeah.
07:12:34 Yeah. So, I know when we sit back for the audit we might need. It's not only a Ben, Ben, we look at the repository we might need in fact it's.
07:12:43 And I know I giving a bolt on mission to the subcommittee.
07:12:50 But I think we need the help.
07:12:54 And that would be the architecture subcommittee, Catherine I would agree.
07:13:00 I don't.
07:13:03 Okay.
07:13:03 Well, we didn't know if you think it's the second right but not.
07:13:10 Yeah, well, I already raised my hand and said it hit me up for a second I think these, these are issues that there was talking about, many issues over here.
07:13:18 Right.
07:13:20 The, the first issue is
07:13:26 the component dependencies which component depends on other components. And I think that list should be readily available.
07:13:39 Right.
07:13:41 I think that is a access list within the system that says this component can talk to another component. Right.
07:13:48 So that pairwise
07:13:53 security, if you will, or access list should indicate the dependency from one component to the other so we should be able to go in.
07:14:04 I think used to be a fit. I don't know if there is another way to do it.
07:14:10 Or, if we're using sidecar or a different access list that that list of dependencies between two components should be readily available so should we should be able to pull that and make sure that the details can verify that the dependency dependencies
07:14:31 still exist. Right.
07:14:33 The second issue is, these repos that have been quiet for some time and we don't know what to do with them.
07:14:44 Right.
07:14:45 So I think this is this is totally different.
07:14:50 This is totally different issue they may be related but I think the order of business should be, let's identify the dependencies at the component level, then let's bring it down to the repo level, and then find out what what is common across these two
07:15:08 items and what's unique and address them as such.
07:15:14 And when when and a few minutes if I get the chance to share with you the architecture diagram, We track.
07:15:27 At least I track all the components that have been replicated, as well as the components that don't have any details assigned to them at this point in time.
07:15:44 And when we're doing architectural review. I make sure we note in the middle minutes.
07:15:46 If there are any dependencies to a deprecate the components or components that don't have details, just to make sure that the sponsors, understand that the, if there is a dependency or if there are any dependencies that there is a risk to the feature
07:16:05 old features that are sponsoring because of the song may not get they may not get get the support that they looking for from other components.
07:16:19 So, I was getting before when I said no, it's the sitcom, but something that the architecture subcommittee can look at from a component perspective. So when we doing the component architecture review.
07:16:33 There are forums that we follow. and we ask for every PDF to fill out to tell us, you know, to give us details about their component and the interfaces that they use, right, we could certainly add yet another section that says list all the component dependencies
07:16:53 on all the other components we could do that. No question about it. But that is separate from addressing the source code repose that, you know, the second issue that was discussed.
07:17:12 So I think we should sexualize the issue. First one is can we create, can we from an architecture receptivity perspective, can we address the dependencies between components and we certainly can do that, right, we could update the forms that we have to
07:17:26 actually ask each and every sponsor or ppl to list the dependencies of their components on other components.
07:17:36 Now, the repos like I mentioned earlier, or something that we need that would need to be addressed separately.
07:17:43 Yes.
07:17:45 Is it, I spent it on that point. Sorry cutting just wanting on that point we had started this activity as a part of.
07:17:54 Initially displayed we made a dependency graph between these components.
07:17:58 Perhaps we can revisit it and update it. I totally agree that we need to have this matrix where we completely have the complete dependencies across the components.
07:18:07 And this was something which we started initially but I think it didn't got upgraded after that maybe we can just revisit that and I'm pretty sure that that there there was a graph.
07:18:20 And yes, we talked about that the other day in the meeting, but I don't think that it was maintained after Michael O'Brien left. Exactly. So what I'm saying is another big actually having this a picture of your meetings right maybe one clause that we
07:18:45 emphasize on is the dependencies across projects. As a part of our culture we do have this project with us right.
07:18:43 Perhaps that is a place where we can actually put one more clause which is to manage that project has to depend has to give the dependencies.
07:18:50 It is the dependencies which it actually depends on the price but it depends on so that we can have them at explain later on, right.
07:18:57 So I think that sounds like a good idea and also sounds like it's a global requirements. So that's just something the projects do free treat for each release and then so then I guess it was potentially false to you that if you're not if you'd, if it depends
07:19:12 if something, if, if it's not if a dependence. So, if a component is not in that graph for that release, it doesn't get put into the build.
07:19:23 And that's a good way of testing whether the projects have actually updated and I think their dependencies and understanding, you know will not build correctly.
07:19:38 Exactly. So, we can make it doesn't make a difference. All right.
07:19:38 That's a global requirement.
07:19:41 So should we make that should we decide right now to make that a global requirement for the Jakarta release.
07:19:48 Is it is it feasible.
07:19:50 Well, I would need to. So, it's the process for that is first has to be proposed as a, as a better.
07:20:07 But here's but ok so then what we if that is the case, then we're going to be exception to the process that's right because if we follow process as his own release, not need we don't require to editors new process we already have something called as artists
07:20:32 review, which is agreed upon lol practice right.
07:20:31 We've already had things that have been through the architecture.
07:20:37 Not meaning right.
07:20:38 How many of you have already completed.
07:20:41 I mean, we first again, I want to go back to, to the point I made earlier I think there are two points that are being made. One is the, the, the state of the software repos versus component dependencies.
07:21:01 And to me, one is, is that high level, the other one is at the detail level.
07:21:06 The detail level can be derived from the high level view as to whether you know what components, a specific component depends on, let's say for example take so right, you come in and you say so depends on a, go ahead and share.
07:21:28 Yeah, sorry. I'm giving your data account. Yeah, thank you, thank you yes thank thank you.
07:21:33 Just give me one second.
07:21:41 Why do we why you are doing this island, yeah need Hayes mindset issue.
07:21:46 The project deposit dependent, sigma become fast of the architectural review, because I don't feel it's a blow by a requirement it's not, it's small architecture.
07:22:01 Yeah.
07:22:02 So, exactly.
07:22:20 To that point, what I'm saying is we don't require to revisit a new requirement, all that be required to list individual projects when they're going for us we can just put this clause in there will be much easier.
07:22:11 Right.
07:22:12 Yeah, I need to, I need to we need to update the form.
07:22:18 I expect updates to make sure that we include it and I could go back. I could go back to the details that have done the reviews already, and we only did two or three, and then we could ask them to retro actively update their forums to reflect the dependencies
07:22:34 that's not the issue. But what I'm displaying over here, and this is good segue into the architecture reviews that we have started to basically perform.
07:22:46 For the past week or so. So, the. You have a lot of vivid colors over here but there's a reason for it. Right. so if you take a look at the legend.
07:22:56 Anything that is in lavender color, are the components that don't have details associated with them and the reason what.
07:23:07 At least I do this, is that when the component that is a for an architecture review in a here that there could be, or there is a, an impact on other components.
07:23:20 The very first thing I do is look at the we look at this diagram and find out whether the component that, that there is a dependency on has a big deal or not and that's where we flag.
07:23:35 Excuse me, these items in, and during the architecture review. Right. So, there are quite a few components that don't have pts.
07:23:49 Excuse me.
07:23:49 So, and I let you take a look at them at your leisure, two components that have been replicated login and music.
07:23:58 This is a comment or feedback that Silva, gave us on Monday.
07:24:04 And what that means, when the components are in gray boxes, it means that oh I'm no longer.
07:24:14 They're not part of the om startup scripts so they're, they're no longer up and running, and they're not included in the, In the current release or the subsequent release.
07:24:26 The way we do this is we grandfathered these components for one release. And then in the next release unless something changes in the next release will remove these components from the diagram, or the other components that you see the orange is indicates
07:24:41 that a
07:24:45 new architectural review has been requested However, a date has not been assigned and I will pick on Liam and you'll see what I mean. So, this is a policy framework
07:24:59 JIRA ticket.
07:25:01 Everything is has been created, waiting on Liam to come back and tell me when he would like to, to give me a date, so we could assign assign it to an agenda for specific date.
07:25:16 If I go to for example a an ai, ai is scheduled as you can see over here is scheduled for January 11, all the documentation is associated with the review or include over here.
07:25:34 This would be also I could certainly edit field over here that says dependencies and we could click on it and go to the proper form to show all the dependencies on the other components, somebody was asking, saying something.
07:25:50 I was wondering where does that is it worries me is that seems to be a good idea, like we can accelerate as a template and I think once we have attempted and complete metrics will be will be based on it right, but that sounds like a plan.
07:26:12 the green indicates that the, the review has been concluded. I'll pick on that for a minute. so we did the SDN controller review yesterday.
07:26:17 The documentation that were reviewed or included over here. And then the committee decision, we always basically timestamp when it was reviewed and when it was approved.
07:26:31 So that's basically, this is a living document. So we update it on weekly basis or on daily basis, I just updated PvP and BNF SDK, based on what David just reported to indicate that the details.
07:26:47 We don't have. We lost the details for these two components, just as a reference point for for the architecture subcommittee.
07:26:59 Now, I'll spend another 30 seconds, I'll take you to
07:27:06 the.
07:27:11 The architectural review meetings.
07:27:15 This is the upcoming meeting for next week. Next week would be the last week for this year and then we'll resume, on January 4 I added the gentleman January 4 into the schedule just to make sure that we finished everything before January 27.
07:27:33 What you see over here is you don't have to scroll through all the pages, there's a lot of information there so you could use this reference.
07:27:42 For example, the component reviews, you click on it and you should be able to see all the JIRA tickets associated with the component reviews, including those that have been reviewed.
07:27:54 You click back on the quick reference and you go to use cases.
07:28:00 And David This is the use case JIRA ticket that was created yesterday for you guys.
07:28:09 And again, it's schedule I'll tell you when I had scheduled for I think it's on the 11th.
07:28:17 If we go to the functional requirements, and you have a list of all the functional requirements JIRA tickets that were created.
07:28:28 Now, instead of going back and forth to all the this is the section Scott look ahead so if you want to look ahead on what's on deck for January 4, you click on it, and you see that we have Henry scheduled we have the entire session, dedicated to Henry
07:28:46 and dawn to present their, their functional requirements, I still have one slide over available if anybody wants to use that we could certainly do that.
07:29:03 Comment short January 11, you'll probably have to cancel it due to the developer forum.
07:29:09 Yeah, Thank you very much. Yes, Yes.
07:29:12 Yes, thank you.
07:29:14 Okay, I'll do that So assume that this is a reschedule January, 11.
07:29:21 So if you click on, click on it and you go to, you see that we have quite a few.
07:29:27 Yes, the slicing is scheduled for the 11th.
07:29:32 For now, but then I and I need to do a reshuffle and push everything out by one week and then again I mean, just you click on for every, every agenda has the look ahead and it shows all everything that is scheduled in the future so you could basically
07:29:50 walk through it and and see what the agenda looks like.
07:29:56 If there are any available option or slots, and then send us an email and we'll schedule we're you review based on availability. So, again, thanks, Renee will go ahead and and make the changes in move everything back by one week.
07:30:19 So that's what I wanted to share with you today I plan to give you quick updates for the next few weeks. Next week and then in January, keep you posted as to what's going on, and will update you with the status, and then we'll think about how we want
07:30:38 to create the dependency list and included in the.
07:30:44 As part of the JIRA ticket.
07:30:47 And we'll make sure that we'll go back in and ask the reviews that have been conducted or the PDF files that have conduct conducted the reviews to go back in and update their JIRA tickets as well.
07:31:06 Okay, um, last point that few ppl and new.
07:31:13 Your component is impacted, please send me an email. I do miss some a, I tried to address them as fast as we can.
07:31:18 And then we'll create a JIRA ticket for you and it will add you to the one of the agendas and the next four weeks or so.
07:31:32 Any questions or comments, No just thank you shocker, and then if we can communicate to the PDL what we have just discussed so David sorry again on you.
07:31:44 I think it's important based on what we have been discussing to notify the teams that they should also prepare and maybe shocker You said you have a template.
07:31:55 They should prepare also kind of dependency half we don't need to go too deep, deep level I'm just thinking about VG with 60 repository for policy. I mean, just not if I think what it is important is just not defined the impact, right.
07:32:13 Don't tell us that you are still in us, we know that tell us repository that you want to ask I tell us how you are impacted because music is not there, whatever, right.
07:32:28 So, let's focus on what does not exist to aid us again, the workload of the PTS so check out if you have a template ready, that would be great. But I think it's important David on Monday.
07:32:41 And again, I'm giving you the action, because we have a set of ppl here, but we also set of people who are not there, and we need to communicate, a little early.
07:33:00 Because for half the members who are located in APAC, we might not be able to join the call on time as well. Is it okay.
07:33:05 It is right I don't think we're going to get it right from the first time I think we'll take will take a shot at it.
07:33:12 We'll take a shot at it. I'll discuss it with the architecture Subcommittee on Tuesday, we'll come up with the proposal, and then we could refine the proposal as we as we move forward with it.
07:33:22 Yeah, it's.
07:33:25 Exactly. Yep.
07:33:27 Yep.
07:33:28 And then, when the team at this time I tried to add additional items.
07:33:34 I know we are running out of time. So is there anything important that we need to communicate, especially considering the DD a fever, which will happen we have still a one to see call, so it's lot of last one today.
07:33:49 I know a lot of you might disappear but we we have still one call next week, and after that we will not have any calls until the second of January something like this.
07:34:04 The sixth of January, so we can keep going. Some of the topics. But the topics we did not address that require emergency like the elephant marketing, we can still spend some few minutes.
07:34:18 Otherwise I suggest, let's look lush and let's have the numbers of the topics as part of the next week agenda.
07:34:30 Yeah. Yes, honey, we will do it next week.
07:34:34 Okay. Anything else before we close this session.
07:34:57 And I need approval from TLC for that. Then you did that earlier. It was on the agenda.
07:34:55 It's on this page. Okay. Thank you.