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 

...

Zoom Chat Log 

06:58:28 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
06:58:52 From  Byung-Woo Jun  to  Everyone:
    #info proxy Byung-Woo Jun, Ericsson
06:59:06 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #info Yuanhong Deng, China Mobile
07:00:00 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
07:00:01 From  Sai Seshu  to  Everyone:
    #info Seshu, huawei
07:00:09 From  Ranny Haiby (Linux Foundation)  to  Everyone:
    #info Ranny Haiby, Linux Foundation
07:00:14 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #info N.K.Shankar, STL
07:00:27 From  Sai Seshu  to  Kenny PAUL (LFN)(Direct Message):
    I will be dropping early today
07:00:35 From  Kenny PAUL (LFN)  to  Sai Seshu(Direct Message):
    ok
07:01:12 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang, Wind River
07:01:48 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT
07:01:54 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
07:04:25 From  Fred Oliveira  to  Everyone:
    #info Fred Oliveira, Self
07:05:50 From  Catherine Lefevre  to  Everyone:
    #info, catherine lefevre, att
07:05:50 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
07:07:58 From  Fiachra CORCORAN (EST)  to  Everyone:
    https://lf-onap.atlassian.net/wiki/display/DW/Istanbul+Release+Key+Updates
07:11:41 From  Sai Seshu  to  Kenny PAUL (LFN)(Direct Message):
    Im in a hospital and need to drop early and So had to jump on the topic, you can please consider my inputs, thanks
07:14:19 From  Thomas KULIK (DT)  to  Everyone:
    Pending documentation changes for the "Jakarta" release: https://gerrit.onap.org/r/q/owner:cedric.ollivier%2540orange.com+-status:merged+-status:abandoned
07:17:12 From  Catherine Lefevre  to  Everyone:
    https://lf-onap.atlassian.net/wiki/display/DW/2%3A+Jakarta+Release+Integration+Testing+Status
07:25:10 From  Toine SIEBELINK (EST)  to  Everyone:
    CPS has just now updated the expectations. WE are waiting on a small fi by Michal J. Reduce expectation to 1 day... Apologies for not updating this earlier
07:25:49 From  Kenny PAUL (LFN)  to  Everyone:
    #vote Does the TSC approve moving both the RC milestone to May 12th and the Sign-off milestone out to June 2nd?  +1, 0, -1
07:25:56 From  Ranny Haiby (Linux Foundation)  to  Everyone:
    #vote +1
07:25:58 From  Eric Debeau  to  Everyone:
    #vote +1
07:25:58 From  Fred Oliveira  to  Everyone:
    #vote +1
07:25:58 From  bin.yang@windriver.com  to  Everyone:
    #vote +1
07:26:01 From  Timo Perala (Nokia)  to  Everyone:
    #vote +1
07:26:04 From  Byung-Woo Jun (Ericsson)  to  Everyone:
    #vote +1
07:26:04 From  Andreas GEISSLER (DT)  to  Everyone:
    #vote +1
07:26:04 From  Dong Wang (China Telecom)  to  Everyone:
    #vote +1
07:26:04 From  Bruno Sakoto  to  Everyone:
    #vote +1
07:26:12 From  Catherine Lefevre  to  Everyone:
    #vote +1
07:26:23 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #vote +1
07:26:33 From  Kenny PAUL (LFN)  to  Everyone:
    #endvote
07:27:00 From  Kenny PAUL (LFN)  to  Everyone:
    #AGREED the TSC approves moving both the RC milestone to May 12th and the Sign-off milestone out to June 2nd
07:27:09 From  Catherine Lefevre  to  Everyone:
    keep going team - very great progress but we can not compromise the quality of our release
07:32:20 From  Fiachra CORCORAN (EST)  to  Everyone:
    https://lf-onap.atlassian.net/wiki/display/DW/Istanbul+Release+Key+Updates
07:41:49 From  Catherine Lefevre  to  Everyone:
    here is the definition of Global requirement - https://lf-onap.atlassian.net/wiki/display/DW/Requirement+Types
07:50:40 From  Kenny PAUL (LFN)  to  Everyone:
    BP/GR Policy: https://lf-onap.atlassian.net/wiki/x/cR37
07:56:54 From  Kenny PAUL (LFN)  to  Everyone:
    list of unmaintained projects: https://lf-onap.atlassian.net/wiki/x/-xL7
08:00:42 From  Catherine Lefevre  to  Everyone:
    sounds like a lot of steps have been added by Muddasar recently to address this - https://lf-onap.atlassian.net/wiki/display/DW/Project+State%3A+Unmaintained
08:05:05 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Security+Exception+Process
08:05:17 From  Fiachra CORCORAN (EST)  to  Everyone:
    https://lf-onap.atlassian.net/wiki/display/DW/Jakarta+Milestone+and+Requirements+Exception+Requests
08:21:53 From  Kenny PAUL (LFN)  to  Everyone:
    ]intern process: Program details
08:22:11 From  Kenny PAUL (LFN)  to  Everyone:
    https://wiki.lfnetworking.org/x/PgAF
08:23:21 From  Kenny PAUL (LFN)  to  Everyone:
    https://wiki.lfnetworking.org/x/vACkAQ
08:27:25 From  Eric Debeau  to  Everyone:
    Congrats to Morgan and the team !
08:27:36 From  Andreas GEISSLER (DT)  to  Everyone: <thumbs-up>
08:27:59 From  Catherine Lefevre  to  Everyone:
    Top Achievement Award (1 nomination) – Jack Lucas     Citizen Award (1 nomination) – Lukasz Rajewski     S3P Award (1 nomination) – DCAE project     ONAP Demonstration (1 nomination) – E2E Network Slicing Use case
08:28:04 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    Congratulations to all the award winners!!
08:28:13 From  Eric Debeau  to  Everyone:
    Congrats to Lukasz, Jack !
08:28:15 From  Catherine Lefevre  to  Everyone:
    Code Development Award          Jim Hahn     Liam Fallon     Ram Krishna Verma                Automation and test coverage” Award          Morgan Richomme (Integration)     Stanislav Marszalek     Krystian Kedron     Maciej Wereski     Michal Jagiello
08:32:46 From  Catherine Lefevre  to  Everyone:
    Congratulations to our Istanbul winners and thank you to the whole ONAP community members who have supported them !

...

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:02:29 Okay, let's get the ball rolling
07:02:38 As you've all seen meetings, being recorded everybody's muted. When you come in, please keep yourself muted unless you're speaking, coming in on a phone line, you can use star 6 to unmute yourself Send me a private chat
07:02:49 message i'll happily cut and paste that into the meeting and it's when everything is done and we will start by mentioning our projects.
07:02:59 Antitrust policy. you can find this link from both.
07:03:02 The own app and all of the Lf. Project Websites policy is important. When we have multiple companies, including potential industry competitors participating in meetings, please review it.
07:03:14 You have any questions please contact your Company's legal council members of the Lf.
07:03:19 May contact Andrew up to grab the firm, gives more upgrow the Llp.
07:03:22 Which provides legal council to the Lf. This policy is, in effect, whether there is a member of staff attending a meeting or not,
07:03:43 Today. We will be spending some time on Jakarta talking about that, because today is a milestone date.
07:03:58 Exception request for global requirements dave will go into that wanna check on the webin waver from last week.
07:04:10 We'll do our normal discussion of relange topics. that one will probably need to be deferred, Kenny.
07:04:23 I I got a note from me cal just for the beating he's going to be unavailable today, so we'll probably need to defer that to next week.
07:04:32 The one I've got highlighted right here ,
07:04:52 Hmm. Hmm. Okay, xd api super committer, and then normal administration and business
07:05:08 Anything else anyone needs to add, Fred. Thank you. Yeah, hi!
07:05:17 Can you see you here? I said, , Michigan had a discussion on this along with the hill on last Monday, so I have a quick solution for the pseudonym how to proceed for such cases see one thing
07:05:29 is right now. we don't Have any papers for to be owned by that's one of the issues.
07:05:35 So I have a solution. The baby have done it for non-functional comments for the projects like.
07:05:41 For example, take an example of a so the condition which we I have put forward Was anyone who wants to contribute any code or get a new image, have to also take care of at least one non-function requirement.
07:05:53 When I put that forward I could see that there was a creative permit in in our stake office.
07:05:58 So , be security beat code coverage be any other non function we're talking about.
07:06:03 We had a great improvement. Perhaps we can actually hold the same thing here, too, that any stakeholders of any requirement, any use, case or any function requirement not talking about if they want a new image of X may pay they should own it is
07:06:16 one non-functional comment, and and improve that on the new image.
07:06:20 With Darsh, we can surely see some improvement coming in.
07:06:23 And i'm i'm i'm sure that's the only way we can actually finding it because other than that anyone who will be taking ownership i'm sure will not be understand the company functionally first of
07:06:33 all, and cannot actually keep guarantee because they're not being a contributor.
07:06:37 Spite he cannot get contributors from his own company, or from any other from which he's actually working, for.
07:06:44 So he cannot guarantee that whether he'll be the right on the fight, or he can contribute to that other aspects of the of the image.
07:06:48 It sounds just releasing image on oem alone, right? We have to also take off security.
07:06:52 We have a ticket of code coverage. We have to take care of all those.
07:06:55 You know the the top level task which we have for every release.
07:06:59 Yeah, it just took comment that's issue. session. yeah, this is on the agenda, and in the last week you said we were trying to work this issue, And and so I did.
07:07:11 Reached out to s issue didn't want to talk about it explicitly, without talking to him.
07:07:18 But since he's with so and as he knows about this whole problem.
07:07:21 So that's what? yeah, it's.
07:07:28 , Yeah, yeah, i'm talking it because I think Kenny has taken that as a topic.
07:07:29 Right, , No, I agree. But yeah, you yeah you got it you're just you're just connecting the dots.
07:07:37 I got . i'm just telling letting people so I have put this over to Tse I was talking about all this.
07:07:47 So if you are going, this is actually way out. Maybe we can think of it all.
07:07:52 If you have an nations, maybe we can also discuss about it and take it forward
07:08:01 So we kind of jumped ahead here. Yeah, I mean, especially you just.
07:08:06 He. He was asking about what? what is the agenda?
07:08:09 And we went . i'm sorry i'm so Sorry i'm so sorry i'm on traffic right now. So I I just saw the topic and I just jumped in. Yeah, Maybe we can we can talk about that first
07:08:21 if depending on timing But I do I do want to should to be to be there because i'm sorry for that, because i'm not talking right now. So I just saw the topic, and agenda in 20 that's the case
07:08:31 Okay, Okay, I I I know session that you need to drop early.
07:08:40 So let's I think the the the big thing here is is the is the release.
07:08:53 So because we've got the rc milestone today, so
07:08:59 David, i'll stop sharing and you can jump into that.
07:09:14 Okay, Thanks. Kenny
07:09:14 Okay, So today is our our c milestone So let's just take a quick look to remind ourselves where we're at.
07:09:31 So here we have the release candidate on today.
07:09:37 April 20 eighth. with plan sign off on May twelfth.
07:09:45 Okay, So the milestone status is summarized here 56% complete for the requirement owners and about 78% completed for the project teams.
07:10:02 I've sent reminder emails to the projects and requirement owners. and so there's there's been some activity there in in closing the gap.
07:10:14 But you can see that it's there's still quite a few open items i'll see you got this here.
07:10:24 Yeah. So you can see for the projects and we have 95 closed.
07:10:34 So about 25 that are in in some process leading up to being completed requirement owners roughly
07:10:53 Yeah, we have about 10 that are not yet done. so Still, quite a bit of work here to do.
07:11:06 One complicating factor. that I learned about on Monday was that there was an issue with
07:11:15 Maria Db. and to pay attention to a new version of Maria Db.
07:11:24 For for the Jakarta release, and
07:11:30 So that that blocked some of the projects last week Now, what I've heard since then is that it has been resolved.
07:11:39 It was resolved by rolling back the version of
07:11:43 Maria Db. to the version that we used with the Istanbul release, and apparently that resolved the issue.
07:11:50 But it did causal delay and I think that's part of the problem that we're we're seeing in the the incomplete tasks does anyone have any additional comments on the maria
07:12:05 Db. issue
07:12:12 Okay, mikhail had a medical appointment. So he wasn't able to join us today.
07:12:21 But he did send out an email talking about the status of integration.
07:12:32 In particularly. he he called out that to the home's health check is failing, and he cited this Jira issue, which I think that's assigned to guang wrong, if I remember right, there are root some
07:12:49 rupods that that need to be fixed there's a non ssl node port issue the basic Vm.
07:13:00 Is failing because of an is sorry. Okay, perfect. I think this is the patch for the homes as well.
07:13:10 Okay, yeah, I I checked this issue. looked like there was one Garrett.
07:13:18 Request, still outstanding that it looked like a lot of progress had been made.
07:13:27 As I mentioned, basic Vm. is failing because of an Sdc issue.
07:13:33 Although Mikal mentioned that he didn't think this that this was that serious Mikal ran the stability tasks, which I guess, take a few days to complete.
07:13:48 Unfortunately, there was a configuration issue. so Mikhail needs to rerun that that test.
07:13:55 So That's in process so to sum it up I I don't think we're we're quite there for for Rc.
07:14:11 For the reasons that I just described. So the question is, what to what do we do?
07:14:18 So the what seems to make the most sense probably is simply to push Rc.
07:14:24 And sign off out one week and check where we're at next week.
07:14:32 Comments. And does anyone object to that plan? So that seems sufficient
07:14:42 Okay, So, Kenny. do we need to have a vote or down degree?
07:14:55 Let me in the schedule vote on this i'm typing it up.
07:15:04 So both both both schedules right for the Rc.
07:15:05 And for the of course, any other one as well. Then for this sign up, Yeah. sign off, then also for one week.
07:15:10 Correct. Yeah. And since we're pushing out sign-up we probably should have a vote.
07:15:17 Just one question before we, that David is a live here in Phoenix.
07:15:24 It is when we can off yeah that's that's part of what my question was earlier, you know, because it's you know it's where we're always in the in the mode of
07:15:36 thinking, you know. Are we pushing it out too, far but you know we don't want to keep you know pushing it out over and over again.
07:15:45 So that's that's a legitimate question is if if we don't think one week is enough, maybe it should be 2 weeks.
07:15:55 I mean for me, for for me, or for the people in policy.
07:16:00 One week should do, we should be okay for one week providing everything goes well, you know.
07:16:09 It. It could be tight that's what I think it should be okay.
07:16:11 Okay. and then Monday is a holiday too in Ireland and I don't know if it might be another European country soon.
07:16:19 It's kind of me may day or round day first to me is sometimes holiday.
07:16:24 Oh, okay, right. I have a common David. this this issue the external Api issue that that we have been discussing.
07:16:33 So are you like you're on the call Do we is it can the slicing use case complete?
07:16:39 If that issue is left in this current state, still not resolved right
07:16:50 Sorry to go. so we have other pro.
07:17:03 But no, I'm! asking is one week enough that's the question here, and I have the same question because I would like that.
07:17:12 We fine? Good morning. Good afternoon. Good evening, everybody. I think we should have a look at not only the project, which is important, but I think, for the use case.
07:17:22 It was already nice to see within the next 2 h we move from 56 to 74. but i'm a little bit concerned about the State is reflected on the wiki page that I have posted on the chat because a lot
07:17:36 of items are declared. These more than 2 weeks to finalize the testing, and I don't know it's because people did not update the page.
07:17:47 Oh, if it is indeed the reality yeah that's that's a good point.
07:17:53 I've i've sent out a few notes about updating this page.
07:18:00 But I i'm not sure if if people are are seeing those emails. because a number of these seem like they've been stuck at in this one to 2 week range for some time.
07:18:17 So if you are a requirement owner, if you could update this page that would be helpful.
07:18:25 Yeah, this is a Kevin 10 from the network slicing, I guess.
07:18:30 Yeah, I think we are updating this regularly.
07:18:33 So last time yeah it's it's up to date. Okay.
07:18:37 Good. Okay, to know, because both of the test case are in the network slide thing.
07:18:44 So if you still believe you need more than 2 weeks 15 one week will not fly.
07:18:56 I guess right
07:18:58 Oh, it's good
07:19:03 So how how we you shall I was like so we always left with some carry over test cases.
07:19:13 So we're giving the value of discusses to the next release. So we try to completed at the start of the , You can have carry over Alih.
07:19:29 But you see, you had a red carry over like the requirement.
07:19:32 1040 from Istanbul release. So oh, you need to define when you would be working on the key updates.
07:19:41 You need to define one you, have leave. you everything what will be available in Jacasa, and what will be available in Cone So we know, knowing that we, we we don't know what we can claim we have completed, and what
07:20:01 we still need to do you Understand? what i'm trying to say so it's not an issue, But we just need to be sure what we deliver is workable.
07:20:16 And people will use this release can do something with it. So you need clearly to document what it is.
07:20:22 What would be finished and what will not be finished. And, Kathy, I want.
07:20:29 Add one more point to this. Actually, there is a risk of recreation also.
07:20:31 With this last homogeneous currently the system stability you're getting, and all is actually taking the concentration. right?
07:20:40 Again. I know the team is pretty expert into that. but still we should also consider regretion like if you're modifying some part of the coordinate specific module or project the project can go into unstable state right because we are doing it
07:20:51 in hurting. So that also is something which we have to construct when we are having a one week at the time like this.
07:21:03 The week is not to do the blockman right. The development has been complete.
07:21:04 One month Ago, and the release of image i'm also talking to release of new image, not development, but , , , we are online systems
07:21:24 So the proposal on the table is to move Rc.
07:21:29 Out to May twelfth and off to may 20 sixth.
07:21:38 I don't know yet put 26 will not fly right. I think a lot of countries are sit down on the 26. so 26 it's not fly, for sure, as a sign of But we need
07:21:54 to first on service the first question before discussing about the timeline, we need to understand what we do, and then the timeline had to be in alignment with that as well.
07:22:07 So is the end. One network slicing team can review and there's what they can do to fit within the next 2 weeks to freeze.
07:22:23 And what will not be, or even that it's not possible. Yeah, I think we can do a reveal this and get back to you.
07:22:38 Let's give you if you have a good field
07:22:41 Let's give you if you have a good feeling that and again.
07:22:42 You have the opportunity to have some carry over. but keep in mind what you deliver in your Canada had to work right.
07:22:53 You cannot compromise the testing. So then, if if you can come back on Monday at the Ptl call, or whenever, then we can find the plan right?
07:23:10 Okay, Yeah, we will do that. The older team with currently more than 2 weeks.
07:23:18 So we's also valid for the fact we focus a lot now on the network slides thing.
07:23:24 But we have the same challenge for the book. Pm. Pm.
07:23:27 Control improvement. we have the Cc. VPN.
07:23:31 Also in that we have N Ncp. announcement as well. Right?
07:23:38 And I want to be sure that the orchestration team feel comfortable, although they are below 2 weeks, and the Tcos information is below 2 weeks, so we need to have a good feeling that 2 weeks a lot of things will be clear and
07:23:58 so back might be carried over, but it has to be documented.
07:24:05 And if we can do this, then it means, yeah, we can and have the airc on the twelfth.
07:24:09 But the sign of we never happen on the 26.
07:24:15 So the sign-off has to go to June second time
07:24:25 Who want you? The quote Well, the the other thing about may 26 is that that's actually m one for the cone release. Yeah.
07:24:35 But towards the 62 will not have your. You will not have your audience, I think.
07:24:43 , Okay, So maybe we need to talk about schedule for a cone at some point.
07:24:46 Also yup. Yeah, So that's as catherine said I'm. looking at the calendar, and it's a holiday, and there's quite a few countries that observe it, Yeah, I wonder how I missed that one
07:25:00 Okay. Okay. So that's going to whatever if I say Jones second June second
07:25:22 Okay. So what I am dropping into the chat? Does the Tsc.
07:25:27 Approve, moving both the Rcm. milestone to May twelfth, and sign off milestone out to June second.
07:25:38 That is what I am about to drop into the chat window for
07:25:53 There it is!
07:26:20 Okay. Give 10 more seconds
07:26:36 Plank. it passes,
07:28:20 I I think that's really the might tone is have to be postponed because of the testing definitively.
07:28:29 But when I had a quick loop, we also need to ensure the documentation is also aligned with what we deliver.
07:28:37 So. Some of the tickets I know have been reassigned to Thomas from.
07:28:44 He has all what he needs from the team. And I also want to insist.
07:28:50 Because I think David, you were sending a reminder.
07:28:56 So the suitcase to nearly everybody to ensure that they they look at the really ski of data as well.
07:29:06 Right? Yeah. And I know the timo did. add some updates for the requirement subcommittee.
07:29:14 A little while ago. But yeah, subcommittee chairs modeling requirements.
07:29:24 Architectural, etc. if you didn't see my email.
07:29:31 Please. take a look at that page it's linked in the agenda, and provide your updates for Jakarta
07:29:40 It won't before we move on from really status.
07:29:46 I I wanted to mention one other thing I have a note up above here about om status and earlier we hadn't had any progress on the release management tasks assigned to oam mostly because Oh, m no longer,
07:30:08 has a ptl, and this lost some committers.
07:30:11 Catherine did go in and review some of 2 of those tasks and went ahead and closed those I I had a chance to talk with Andreas earlier about this just before the Tsc meeting and andrea said that
07:30:32 he would take this issue up with the weekly oam meeting, which is continuing, I guess, and get back to me about the best way to manage the release management tasks for Om.
07:30:49 Yeah, I put it already on the agenda for next week.
07:30:51 So we are continuing as as usual, even without ptl and having and and and trying to get
07:31:02 Yeah, take care of the all the needed stuff here. Right?
07:31:06 Okay, great, Thank you. and so that's it for Jakarta status, unless there are any additional questions.
07:31:20 So I just I just want to Thanksgiving the Om.
07:31:23 Team to keep going, because, the fact that we need to have all the the active fact package.
07:31:33 Rely on this activity. So thank you so much. Andreas to will help on that with the team.
07:31:40 You would have to thank the team. Yeah,
07:31:53 My my bat. I don't know how the the heroes under oem. I should check that.
07:31:58 I know we have been obviously a couple of them like Jacques Dan and others.
07:32:05 So we should have the list of the heroes as possible awards for sure.
07:32:09 Thanks. and oh, you had a separate question, probably not part of this agenda, but in terms of the like.
07:32:20 I posted in the chat just posted again let's say, that's that's the the key updates for istanbul release, and similarly for to carter the ones that are marked as not part of the
07:32:32 release, but it makes sense, and and would people agree that we remove the relevant town charts from the Olm project, if they're not included as practical release, like, for like, for instance, app see bit et
07:32:48 cetera, and what we do in the past is the valid. So what? there?
07:32:56 I saw that the was already cleaning up a lot of fees before, so would
07:33:03 Is there an email that we can review with addition apps that you are not sure, and I don't think there's an email chain.
07:33:14 But the the charts still remain in the Om.
07:33:16 Project, and so I'm i'm just by raising a question should should we remove those if they're not to no longer pack to release It's linked to the one maintain projects, etc. but you know say for call and release portal is
07:33:35 to be removed. Application on maintained whatever so there's No point in keeping that chart in the olympics.
07:33:43 Repo: Yeah, the problem, for example, I think for some of the components we could do that like Fc.
07:33:50 For example, because it's there is no dependency but at the moment we have still the dependency on portal.
07:33:56 So unless we don't have to resolve that we have to be able to deploy portal for example.
07:34:04 Yeah. So we have to be, of course, a little bit careful with what to do to remove.
07:34:08 But I generally agree on you. have us proposal that we clean up a little bit than the charts.
07:34:17 And anyway, I I also would suggest that we have have a focus on in in the cone release to make some clean ups clean up actions generally.
07:34:32 I think that would make sense, so that we call that cone release.
07:34:37 Also a little bit of a cleanup. Yeah. agreed. Yeah. Yeah.
07:34:43 But just say, Okay, we ignore, ignore portal from that.
07:34:46 But say for apps, C and Fid: Yeah. you know they they have been not part of the Istanbul release.
07:34:52 So you know. Yeah, Yeah, maybe maybe it's it's a it's just in an effort to to remove some of the of its charts, because our our linting now is taken up to about 11 h.
07:35:07 So it's a that should be we can discuss it offline it.
07:35:27 Thanks,
07:35:28 But again, I guess it's kind of linked to the on maintained Project I agree,
07:35:43 Okay, Kenny, should I move on, or did you want to drop down to the external Api issue
07:35:54 I think. but she already dropped here, too. Okay, all right, , sort of trying very hard to call in from from somewhere I mean, okay. So So we can.
07:36:05 We can proceed the normal We can talk about it either way.
07:36:11 Like, if you want to well i'll just go into this next item.
07:36:16 I I brought this up to the the Tsc.
07:36:23 Last week, and was asked to review this with the the ptls first.
07:36:36 So I did that on Monday, and receive no, there were no objections.
07:36:44 The ptl seemed to think that this made sense but i'll i'll review it again here just to refresh your memory about what i'm talking about so what we've been talking about in the
07:37:00 unmainted project meeting is how to track unmaintained project dependencies.
07:37:11 And so the the idea that we discussed was using a global requirement for each unmaintained project that has dependencies.
07:37:24 And then attaching to that that global requirement tasks in each project that has a dependency on that unmaintained project.
07:37:41 I hope that makes sense so it's the it's the unmaintained project that is represented by the Raq.
07:37:52 Epic and then tasks, child tasks are attached to that for each dependent project.
07:38:04 Now, the the the reason I bring this up is that our no, our normal global requirement process is that we go through a best practice space.
07:38:19 And we don't believe that that makes sense in the this particular circumstance.
07:38:26 In other words, we're not expecting anyone to create new code that is dependent on an unmaintained project.
07:38:34 Or if someone did, that would be picked up in the Architectural Review.
07:38:40 And there would be pushback on on trying to do that so we don't expect that to happen.
07:38:48 Therefore we're suggesting that we make an exception to the normal global requirement process.
07:38:54 So that we can create a global requirement immediately for unmaintained projects that have dependencies rather than going through the best practice phase.
07:39:07 And so that's that's what i'm asking the Tsc.
07:39:11 To approve? Does that make sense that a Does anyone have any questions about that?
07:39:21 Some. So i'm a little bit confused So when we create a global requirement, it's the Google requirement concept was used to create requirements on project that they cannot normally miss during the release except when there is an
07:39:50 exception. So do we change the notion of global equipment based on what you have explained
07:40:04 Maybe i'm not following you but I I don't see where there's a contradiction, because you create a global requirement easily requirement that we apply to project.
07:40:22 We have committed to be part of the release. So here we create So hey?
07:40:32 These we are changing the concept and the definition of global requirement.
07:40:39 But our global requirements live on past re release They're not associated with the specific release
07:40:55 , I I think what Catherine is trying to say, and let me check my understanding.
07:41:04 Global requirements. Ours are things that are must have for a specific release.
07:41:16 This is for the generally the content that is going into the release and the projects that are participating in the release.
07:41:26 Global requirement for a project that is not participating in the release.
07:41:31 Fundamentally changes. Oh, our definition of global requirement Well, okay, I see what you're saying.
07:41:42 So so the the The The object of the global requirement, is, in fact, the unmaintained project
07:41:53 But the subject are the dependencies. So this is just a way of of organizing that the the dependencies and all the dependencies are with active projects.
07:42:10 But you know that before creating a global requirement, you need to create a best practice, and so on, and so on.
07:42:16 I think the global requirement statement is misleading because of the post that we have been established.
07:42:28 , that's That's why I i'm asking for an exception.
07:42:32 I'm asking for an exception to going through the best practice phase.
07:42:39 Yeah, the the the exception being requested is to not make it a best practice and go straight to a global requirement.
07:42:48 That's the except that's the actual exception request then what is being moved straight to a global requirement is what's written here
07:43:03 Maybe the wording which is French for a non English speaker, because you say we propose a global requirement for each unmenting project.
07:43:13 So what you want to say is each project, whoever Dependency with a non maintained project, we have a global requirement to.
07:43:30 What does that? The problem with that is I don't know If you have noticed the the nature of the and maintain projects, some of them, it will take you more than one release due to the architecture change to implement that so for me.
07:43:47 It's it's like killing the project before starting your release. But we have many global requirements that extend over multiple releases.
07:43:59 Yes, But but you need to have an architecture.
07:44:04 You need to have a solution. You need an identity. There is a lot of work upfront before you move to the code.
07:44:10 The global requirement that we have approved like the java right?
07:44:15 It's code, right? We need to upgrade to a software with here.
07:44:18 You ask the project to work independently to each other, and to find an alternative to something which was common.
07:44:29 I I don't think it makes sense I think this is global It'll be assigned first to a sip committee to establish an alternative for all the impacted projects working with the impacted projects but you cannot
07:44:43 pin a line, the project team, because maybe the project teams will fix the Eef issue as an example by solution.
07:44:52 8, and then project team with stick with the solution B. and then you will take consistency on your architecture on your solution.
07:45:07 So so so that the we cannot do that the the the point of the issue is not to be prescriptive.
07:45:17 It's just to track status don't use good equipment because global requests when wording is a statement for the project team to do something that's not fair for them.
07:45:33 Right they they were. they were not to one right. We wanted that.
07:45:37 Another project. stop, and you ask them to fix that. Now it has to be a collapse if effort to find the solution.
07:45:46 First . the dependency , that's not what This is asking . It's just simply tracking tracking the status of the of the issues. and I mean it could be phrase that in in such a way
07:46:02 that says that you know what once a a common sense, a common replacement for this functionality is determined, you know.
07:46:13 Please please implement that, and and we would track it using these these global requirements, , The intent is not to be prescriptive.
07:46:25 So So stepping back a a bit, what we're asking for is A is is less about a new global requirement and more about adding process steps to the release process.
07:46:55 Right, cause a global a global you know hearing what catherine's saying and and taking a step back and looking at it.
07:47:07 What this is is is mainly, we have a need for projects that have dependencies on Un.
07:47:18 Maintain projects to identify those right that's that that's a need we have.
07:47:27 We want to track that tracking that doesn't require anything other than the release manager.
07:47:36 Making sure that it's tracked and and it and However, that , so, maybe I don't see this as a release management task.
07:47:45 But in terms of in in in it's it part of release process right?
07:47:54 It's it's part of the it's more about release process.
07:47:59 No, I I I would say I would not say that it's part of process.
07:48:04 I mean it's just it's a it's a design and architectural issue that we need to get around.
07:48:13 You know, I mean potentially. I guess we could do it as just a standard.
07:48:22 Let's see it's not a not a feature. But I forgot the specification, or I i'm trying to remember the one that in affects multiple projects. so a feature of you know feature it
07:48:38 affects multiple projects . impacts, so it could Potentially, it may be that be done as a feature instead of as a global requirement for an on feature, as the case may be.
07:48:50 Yeah,
07:48:55 But yeah, but I I understand your point catherine about We We don't want projects going off and implementing their own independent solutions to you know a a common architectural feature.
07:49:14 But we need some way to track where where the issues are.
07:49:20 So. because we always have this question, you know, like for aaf.
07:49:24 Well, which you know, which projects have a dependency on aaf will by creating a a a Jira issue and tracking it.
07:49:35 Then we have that information readily available as well as you know what progress different projects have made.
07:49:44 You know on that issue that's that's what i'm after basically it's just just a means to track this, and it and it may need to be tracked over multiple releases
07:50:01 Dave, I think there are any presented on maintained process.
07:50:07 I think that the Pto I think it's all combination architecture, I think that even release the reason I'm saying release, because when we the remove the Esr from owner, we went through the code and then
07:50:21 who's using the Esl and then also We talk to Ptl, and who depends on esa functionality so identified no one is using it.
07:50:31 Then they can the place Esl with a and I the Api.
07:50:35 So we at that time we are pretty sure that's why we contact oem.
07:50:41 And then we he moved to esl phone oem so that's what the emmy presented what to the the process for on maintain ending so ptr triggered, or the we lost pto
07:50:54 So if we don't maintain we have a security that's why we need to track something.
07:51:02 But also we think of each release to me we have to say these components not no longer available, and they're not in accessible.
07:51:11 So so that's why, that's the combination of the release management and the architecture, and then also Ptr will kind of go the you know coord corporation.
07:51:21 But we need some kind of tracking I don't know is part of the global requirement, or not.
07:51:27 But we need to some kind of process. I thought the Amy.
07:51:30 So the presentation is pretty good. I thought, Yeah. Well, Amy reviewed that in in our Un.
07:51:39 Maintained projects meeting before it was presented to the Ptl.
07:51:43 So i'm i'm familiar with that but that I mean that talks about the process given different starting conditions.
07:51:51 But it doesn't, really say anything about tracking per se So so. what i'm after is specifically that means to track status.
07:52:05 It's not it's not an alternative to what Amy is proposing
07:52:17 Okay, Well, back to the drawing board as they say i'll.
07:52:23 I'll take this back to the un maintain projects meeting and we'll discuss it and see if we come up with a different solution.
07:52:33 Why don't You feature requirements into which you put a jira for cool links to global government. So that way you can track inside the the current release the progress of that feature common release
07:52:59 containing would you have for all? link for all link to an unminton project?
07:53:15 My one input. is so feature, is not to me it's not just the feature, because, for example, aaf they have a feature, but we still need the feature. But what we are trying to do is when you place the
07:53:27 feature with different, you know, the different mechanism. So we are the doing oem team.
07:53:33 They do in Poc leveraging service match and the authentication authorization in open source tool, instead of using the, you know, on a proprietary security mechanism. So features.
07:53:45 There, but we are applying different way to a newer, more open source things.
07:53:51 But in this case, and also we lost Ptr: So teachers there.
07:53:56 But we have more than so. So that's why it's not, you know one I mentioned as much multiple dimension.
07:54:03 Now, when we deal with the one, maintain because we can.
07:54:05 We lost Ptr. or Pt. that you want to do anymore.
07:54:08 Then you know that's another aspect of the this un maintain not just a feature that's my just input So we we have A.
07:54:23 Is there anyone that disagrees with the need for a project to identify dependencies on an Un maintain project?
07:54:32 When we go into a release cycle. Is there anyone that disagrees with that?
07:54:39 As a concept. I I think, The solution that we need to define is a good way right.
07:54:47 There is a very is a step between. You need already to find an alternative which is step one, and and I would already track step one.
07:55:00 And then, when we have definition of the replacement then you can create something for the product team to implement go to first Indonesia, well isn't isn't isn't the first step though I identifying if
07:55:19 you've got a dependency on an un maintain project or not that's step one.
07:55:25 But do we have already done that? I I think, Yeah, I think, step one.
07:55:30 Is that to identify, to make sure that we all understand what the unmaintained projects are you mean under?
07:55:40 We know what then maintained. Projects are you mean what the dependencies. First, first, let's make sure that the list is is comprehensive, that everybody agrees that these are unmaintained projects, A.
07:55:54 B and C. Once we do that, we have a step within the architectural reviews.
07:56:02 As we move forward for every Ptl to identify their dependencies.
07:56:12 If there are any dependencies to the list of maintain projects, that we all agree to
07:56:23 So there is a step in the process that says, Please make sure that you, and then identify any dependency or dependencies that you may have on this list of projects, and once that defendancy has been identified, then we need to figure
07:56:42 out whether an alternative is should be in place, whether we should remove the dependency, and so on, so forth. Right?
07:56:53 But so the very first thing that we need that list from an architecture, subcommittee perspective it's it's it's there.
07:57:02 It's in the un maintain project but it's it's a moving target, right?
07:57:06 Because you have the list today. Tomorrow we lose a ptl, and then it becomes, You know we have to add something to the list.
07:57:14 Umhm. So let's let's baseline the list today, and I think we have it.
07:57:20 We're going to review it next week at the architecture subcommittee.
07:57:26 Amy is going to present to the architecture subcommittee next week, but I do wanna make sure that everybody understands It's not static.
07:57:34 It's a the list is dynamic and we need to always recess as we move through the release and into the next release.
07:57:44 But let's make sure that everybody agrees that the list that we have for all the Un.
07:57:51 Maintain projects is, reflects the reality. and then from the architecture subcommittee perspective. We will attempt I'm.
07:58:00 Not suggesting that we will identify all the dependencies but we will make sure that is the step in the process of the architect process to make sure that the project either it's not going to leave it a blank
07:58:19 we're going to say, Do you or do you not have dependencies in document
07:58:30 I think there are the functional dependency and core dependency.
07:58:34 So anyway, we need to analyze what kind of well, then, then, you have.
07:58:38 I mean there is a i'm doing this is because there are dependencies that may or may not be uncovered when in the architecture of you already views tales may not be aware of multiple defendances, right let's say for
07:58:58 example, the Pt. You know, one subsystem is dependent on component.
07:59:05 A unbeknownst to the ptl that component A has a dependency on component B right?
07:59:13 So but we can't we can't solve everything at this point in time, right?
07:59:19 And one, you know, at the you know, in in 1,912.
07:59:21 But we we could start and then drill down as much as possible to the next level of detail.
07:59:30 So at least we know what these dependencies are, and I think made a good point before.
07:59:39 And this is the point that we've been following we have been trying to keep the architecture diagram in sync with what O.
07:59:52 M. deploy so anything that Ohm does not deploy.
08:00:00 It gets acquiesced within the architectures diagram, and then the next release will just remove it
08:00:16 So so we'll we'll start the you know I don't know if we can agree on a complete process.
08:00:23 It's going to be an iterative process we'll start at this architecture.
08:00:28 Subcommittee document and db tendencies and we'll bring the outcome or the results to the Tsc.
08:00:34 And we need to, so we find them slightly. Then we could.
08:00:40 We could go ahead and do that. I mean trying to come up with and answer today.
08:00:45 100% correct. I I don't think it's possible that things has to be an iterative process
08:00:56 Okay, does. that make sense we we'll review this some more in the maintain projects meaning and sucker.
08:01:13 Maybe you can join us again it's canceled next week, but yeah, the week from Monday.
08:01:19 Yeah, i'll do that. so that we can discuss it and come up with a different plan but I we've spent quite a bit time on this, and I know we've got some other important topics to cover
08:01:34 so i'm going to go ahead and and stop sharing and and let Kenny move us onto the next topic.
08:01:46 What one Katherine, just send a a nice link.
08:01:49 I just created for the on maintain probably you can take a look, and then also that aligned with our Amy's presentation because we walk together.
08:01:58 So okay,
08:02:18 Okay.
08:02:23 The there was a Gpl. 3. Yeah. Yeah. This one?
08:02:36 I asked Kristina to follow up with you with David on it's and Eden
08:02:48 It's a I believe I believe this is similar to other projects but there is a second waiver in it's I don't think it's been filed yet.
08:03:01 Well, that yeah, the well a license a license exception wouldn't be setcom.
08:03:08 Oh, that was the guidance from Katherine on this.
08:03:13 Just to in mind. I think that we were so. We knew that the Os.
08:03:23 Team will not be able to other the geographic, He, garounding the Gpr.
08:03:27 3. that's where we we we wear and then I think the action item, Shanka, because I I was not.
08:03:37 There was, in fact, to create a weaver like we do for the exception, and then it's up to the second team to review it and and tell you yes or no what it is behind.
08:03:51 So did you have the chance to submit the weaver that's already different.
08:04:10 He, he can go to the second mailing list and get that Is it a let me check.
08:04:19 I think any check that for you i'm also checking at the same time, because I don't remember where it is cool.
08:04:31 Are we anybody from the sitcom to help us? or in mind where we put this waiver?
08:04:40 Well, the the so so that's part of the part of the release package isn't it I guess so
08:04:56 There is something going on up security exception, process. is it that one? Oh, it is.
08:05:03 I was just fine. Does any any Ptl can help us?
08:05:09 Maybe the home to link here, because I know you're already I I put a link in the chat for the security exception. process.
08:05:17 Is it? Is that the right place? Yes, but I wonder what not. but not for a license issue. Yeah, that's that was the part that was a little confusing.
08:05:30 Yet I just posted a link there to Yeah, Thank you There it is. okay.
08:05:39 What's the project status Project status in jakarta So that's where it lives.
08:05:44 That's where I was trying to get to
08:05:53 So that's where that needs to be filed thank you Fiatra.
08:06:02 You see, Shangha, there is a Kate weaver, and then you need
08:06:10 Yeah, because because Setcom is going to care about security issues.
08:06:19 But this is pure as as it stated There that's purely a license issue.
08:06:26 We We can apply similar courses. I guess from the Tsc.
08:06:34 To go to to be allowed in the release. Absolutely. Yeah. I just quickly click on the create button.
08:06:45 If there are fail which is not applicable, you just put in a but I think you can use a template.
08:06:51 But what it is important is at least as Skinny said, part of the had this packet, so we know
08:07:01 Oh, okay, socessants were i'm i'm i'm just gonna jump over the the relin stuff, and let's do the external api discussion.
08:07:21 Now So so 1 one update on this and and actually It's I should appreciate wanted to note s issue is addressing the set.
08:07:35 Yes, it's a lot of reasons why he's attention is diverted from this.
08:07:43 But we had. We had a call, and so what I reported last last week. was David discussing this issue as to what is the best way forward, and one of the things that came up based on the discussion.
08:07:55 And I don't know if he lies still here, but
08:08:00 So Ellen knows a lot about the deep details about this, and and when we, when we discussed it became very clear that I mean the project which is in some sense closest to this.
08:08:13 It would be so. the service orchestrator project.
08:08:15 And so then we had a call. this issue, and he was not available last week.
08:08:20 And so as like I said, he's going out of the way to just make sure he's available, and and he just got back on Monday. And so he agreed that that and so is what is involved.
08:08:33 But the main input from him, and what he was trying what he was articulating.
08:08:36 In the beginning of this call is that He said, he cannot just take over the all of the repo, because of the one, all the it's connections and dependencies to other things.
08:08:48 But one of the things he said is, there is one part of it which is the the Api related to.
08:08:57 So, and he said he could consider taking part of it.
08:09:03 But he was also immediately also explaining that that doesn't solve the whole problem, because external api is something that is part of one app, and it belongs as part of one app and it was created for a particular reason and so
08:09:14 even if he addresses part of it, that still leaves a problem that I think what he would have.
08:09:23 What he said in the beginning of this call is it's something that Ec.
08:09:25 Needs to address overall and and we have a problem, and he high level.
08:09:30 He can. he can help with part of it But so so you don't have us solution beyond that. you don't know what to do.
08:09:37 Yeah, , and also Eric and Andy.
08:09:46 , Okay, you also have some history of your your input.
08:09:47 What else? Yeah. Yeah. we yes I think at the beginning we we don't just project to to to facilitate integration with existing Pss using tmf Api Because the So: Api was not aligned with
08:10:09 the Tmf one, so that's why we decided to to run this project.
08:10:13 So today we unfortunately, we don't have any developer internally in your launch for that.
08:10:24 So, I think, can be a good idea. That external P.
08:10:27 I can be managed by Sso. but we we also be careful that as an Ip I interacts also with Sdc.
08:10:37 And I yeah, so it's It's not interface is it's with So, but it's we we have to to know that our c some interaction only 2 resource of components so the may be less
08:10:57 important but I think yes, it's a can be a good idea to to call the program today.
08:11:06 I need to move the the reporting assault, that can help to progress, because i'm pretty sure that there will be some so new evolution in the in the coming organization, because there's a occurred as some limitation as far as I
08:11:26 know, so we we should deep some extension for for the coming requirements. but we need at the end.
08:11:35 We need still developers, and I'm not sure that so team will be able to do it.
08:11:40 Yeah, ,
08:11:47 Yeah, I mean it sounds like slash is basically just said that that there's a a piece of it that the the team may be able to take on, but it doesn't address the larger issue.
08:12:00 The larger issue here is that we have key functionality which it seems like a lot of people care about, but no one's willing to support
08:12:14 So it mean it's not important right so it means that not exactly.
08:12:16 It means it's not important it's it's if if if it is important, as people are saying it is, resources should be forthcoming, and the fact that they aren't it sends a pretty clear message that it's really not
08:12:37 that important. So i'm this is just commentary from me I can't do anything about it.
08:12:48 I I can say from the telecom point of view, that we are at the moment in discussion whether to take over the responsibility for that, as we need at least when we go forward with our Tina project with would need an in an
08:13:10 external interface which was, would be in Tmf.
08:13:15 Compliant, and that would mean that it that we we are thinking of taking it over it at some point.
08:13:25 But at the moment we are still in the let's say discussion, phase here also with our external ones.
08:13:30 So that means the interest is there, and and we need definitely to improve the end.
08:13:38 The the the extra Api, and then make more features on that.
08:13:42 Because in that case, how it is done at the moment it's not so usable.
08:13:47 So it's not supporting the Michael flow well at this has some other restrictions, and so on.
08:13:58 So I think there is an idea, at least in our case.
08:14:00 We have interest in that one in that component. and of course.
08:14:05 When we have made a decision, then we would, may be a candidate for taking it over.
08:14:15 It's just as a outlook for the future but not at the moment that's why we speak about a long term plan.
08:14:28 So I think so. So if we can hit wine a little bit, I think there is indeed a value on it.
08:14:36 There's only value on it when we use it so over the past year.
08:14:40 Only one fix has been submitted so that's Why, it it was not really efficient to have a ptl for 1 6 per year.
08:14:50 No, if there is more than one sixth grade, we need a to take it seriously like you describe.
08:14:57 So I would see the long term plan is long right i'm a little bit interested to see if we fix the shortened plan, which was, I know Eric and Andy have been added as commuters from 6 have been,
08:15:13 merge, but because of i've been off unfortunately I i've love.
08:15:20 I could be sure that this team, who needed for short time we fix everything, or if there are still some steps from the Tsc.
08:15:34 By cooting their concern and and hitting out the the people.
08:15:38 So have we the image, or with the book included, or we are still an issue.
08:15:45 So. ahila I know it's quite late at your place we do.
08:15:50 You need all what you needed, we Kevin, or is there?
08:15:56 I see cabinets also there. So everything is okay. Or do you still need that? Somebody do something for you?
08:16:05 And then yeah. So the yeah, the fix was merged. It was tested.
08:16:10 And validated. but other one thing is like, the still the repos and active state, and the daily bills are happening.
08:16:21 But so is it okay to keep the build running?
08:16:28 So that is a open question. You can keep the bill of running.
08:16:37 Okay, then, it's , Yeah, So what what , , I feel , sorry.
08:16:42 Sorry. Still, we derive at the long term solution.
08:16:49 So it will be good if free. keep other bill running. So that, like we can use it for our use case we still produce the release management to what's next to?
08:17:02 So I think this you. need to provide a release zoom. and file in the external Api that people create next season, and then we need to put that on.
08:17:11 But we need to do that. I don't know when your image is okay.
08:17:14 We need to to findize it, but you can
08:17:28 So short term. Can you remind me? We say 12 for se.
08:17:37 So I I think, Aila, we need to have a deadline on the wines.
08:17:43 You will never be part of this release so that's why I put the May the twelfth where we need to have the final image?
08:17:50 Because otherwise we cannot finalize the testing either then it's also good is it we?
08:17:58 We need to set the day Katherine Will discussed about this release image last week.
08:18:05 But there is an action to be performed by the Ptl to release the tacita release image.
08:18:11 But that cannot be done because of considering the security issues associated with an unmented project, so like what the suggestion I got is like to use the master branch, master branch image version itself.
08:18:28 So we are continuing to use the master version image.
08:18:36 So, in in order to release the image for Jakarta release, we would help.
08:18:41 We would require help from Eric or Andy. But yeah, Eric updated, that that is not much simpler to do
08:18:54 Can contact me on the we can. We can serve the program.
08:19:01 Okay, , images ready when you're ready to to to , Yeah.
08:19:13 Okay, Thank you. Thank you so much.
08:19:25 Alright, I think we had a great discussion on that. We We know where we are.
08:19:29 From a short time plan the long term we see. Maybe at 1 point we move to medium stem, but we we are not in there.
08:19:39 So, David, too much or things with the super commiters rights.
08:19:44 Do you need additional support,
08:19:48 No, no! I saw the ticket that I think David raised but follow the discussion from last time.
08:19:59 So. Personally, I do not have to be a super committed to ask supercomers with a list that can he send to me?
08:20:09 I and help them meet out emerging verifying the patch.
08:20:16 So i'm personally do not have to be a super committed to ask them right.
08:20:21 Correct. Yeah. So yeah. But it's a good idea to have more people than to to leave you.
08:20:34 A patch for documentation and we'll ask them be as a list
08:20:44 Okay, Tomas, so I will send you additional people who can help you to review the the documentation.
08:20:52 2, maybe this you you ask, Okay,
08:21:02 Okay. zipping down the list. internships
08:21:13 The deadline is the thirteenth of May for putting your proposals in for folks that have participated in this in the past.
08:21:27 It is highly valuable. and The program details.
08:21:37 I will drop both of these links in there into the chat window for your convenience.
08:21:59 Well, that doesn't help does it let's actually get the link
08:22:17 And I had that open here somewhere
08:22:27 But it seems to be lost in. no, there it is.
08:22:34 So this it gives you the run down on the run down on the on what to do.
08:22:52 Where to go to fill it in. and how to do this this has been this has been a good thing for us, so I would highly encourage you to go take a look at that.
08:23:06 If you haven't already any questions about the internships
08:23:24 Okay, The badges should be coming out shortly.
08:23:31 As folks may know. Brandon Wick was involved in that.
08:23:39 He has moved on to other opportunities. and we're working to get it done.
08:23:49 As of the this morning it's being looked at today, so folks should start seeing those pop up incredibly shortly
08:24:10 We've got
08:24:25 My mouse is being a little jumpy.
08:24:32 So what the list Kenny, Because of the list we have been discussing with the Tsc.
08:24:38 So so. if you don't mind and how to proceed. but you have already won pat on the wiki you were sharing, and and I can I can finish that.
08:24:50 But so the theatre review world the nomination and I think it's important to recognize our heroes, and i'm pleased to announce that even if we had only one nomination for the top achievement
08:25:05 award Jack lucas Oh, i've been here awarded to be of top achievement for the Istanbul release.
08:25:16 So the city's on award I don't know if it is on the call.
08:25:19 But, as you know, Lucas has been doing a lot of work in junction with session, and i'm pleased to announce that is, or Istanbul citizen awards look at as you hijacki I hope I
08:25:33 don't jeopardize too much is family name so the Ftp.
08:25:37 Award S. 3 P. or it's related to all the non-functional requirements Try the project team is trying to improve the security.
08:25:46 The performance is capability and the stability. The dcae was not limited, and was also the winner for the Istanbul award for F. 3 P.
08:25:57 Awards concerning the own up demonstration it's not the first year, and you see how much it is important to continue to do to do this use case, to implement this use case.
08:26:10 So the onup demonstration, which was a great demo.
08:26:15 By the way, is the end to a network slicing use case, who have this award for the Istanbul Hades as well.
08:26:23 And then we look a little bit at the the other work, which is based on the Lfx tools.
08:26:31 So I will not say it is automatic, but we are using the matrix to determine.
08:26:34 We have pre winner for the code development of top winner.
08:26:40 Zoom han liam salon and i'm Krishna vesna to congratulate solution to all of you 200, because you have been contributing not only one lines, of course, but that's tough
08:26:52 that's that you are a winner for the istanbul release.
08:26:56 We also value the automation and the test coverage and winner.
08:27:04 Although is not with us today. you know, formal integration lead Morgan Higgins.
08:27:11 But those 2 studies left Maxwell, Jan Kedron, Magic Will has key and new integration.
08:27:19 Ptl, Mike Jaggalo. So all these people are just one that you join me to thank them, because again, we we really want to recognize our heroes, and they have been contributing a lot to the evolution to the hope map
08:27:34 to the implementation for the Eastern bull. release and we look for what already to see who will be the nominated people for the Jacques that when we are done so, that's the winner maybe I can put in the chat and
08:27:52 we will ensure that the wiki page will be updated.
08:27:56 Called ingly congratulations to all of you.
08:28:01 Congratulations, everybody. Thank you. Catherine. Appreciate that.
08:28:10 Sent out to the send out to the Tstp.
08:28:20 List. was the slide deck for the updates to the board meeting.
08:28:27 That can be handle asynchronously
08:28:33 And then shared. Here, March 6 is where the slides are.
08:28:41 I need to have the slide deck so that I can incorporate that into the governing board deck.
08:28:47 So on that one. Can you see, mia, I I know this week I I need a little bit to catch up due to my sick leave, but I will live in it.
08:28:57 Tackle the deck, supported by the Tse.
08:29:00 And staff to have some review of flying with the Tse.
08:29:04 So we can meet the deadline. but I don't think I will submit anything before Monday, as the first review.
08:29:13 So I want to see the opportunity to really ask the Tc tell me what it is in the deck is what is reflecting correctly.
08:29:22 What you are thinking, and also what the own app community is at.
08:29:27 Right. so more to come. But I have a plan at least, to meet that like
08:29:38 Okay. Dooke:
08:29:43 We've got next week. We have a all hands for Lf.
08:29:53 And staff, we will be basically unavailable for the entire week.
08:29:58 This is the first company-wide offsite all hands that we've had since 2,017.
08:30:07 And there's a lot of stuff going on so we unless it's an emergency.
08:30:16 I would say, don't count on us being very responsive. question should we cancel the Tsc.
08:30:28 Next week, because of that I I don't know I mean just cause David and I aren't here I don't see a reason for the Tsc.
08:30:38 To be cancelled especially given the fact that we've got a a deadline.
08:30:44 Here coming up on the 6. So, Catherine, what would you like to do?
08:30:53 Well, I think we will give some time off to hold the team.
08:30:57 I might set up a special meeting if I feel i've an issue with the deck.
08:31:02 In the meanwhile, if there is a any concern don't wait 2 weeks, but maybe drop an email to the Dsc.
08:31:13 With. please take a look or something striking in the subject.
08:31:18 So it is not lost, and we will work on your concern with the Tse.
08:31:23 But we, if the Ts is okay. The only thing that I wanted to progress was really the priorities and action plan.
08:31:30 Although a lot of people are already working on it. 2. Oh, we get console.
08:31:34 If the Tse is okay, as well okay, we'll do
08:31:55 Okay, Dooke developer and testing forums coming up.
08:32:01 Please start putting in your topic. proposals if there was this line. That's something I wanted to know.
08:32:14 Maybe we need to see there is a deadline to submit, because I believe there are some agenda activities to be performed, or or it will work
08:32:30 Topic proposals are, do,
08:32:52 I guess we've got a meeting on this tomorrow so I don't
08:33:02 An email sent to the owner Pc. and potentially discuss.
08:33:05 So everybody will be aware about the deadline cause I Don't think we can submit topics on June twelfth.
08:33:13 No