661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2022 TSC Recordings	2022 TSC Decisions	Anti-Trust Policy

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

Attended	Proxy (w/ @name)	Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Andreas Geißler	DT	Magnus Buhrgard (Unlicensed)	Ericsson
Cédric Ollivier	Orange	N.K. Shankaranarayanan	STL
Chaker Al-Hakim	Individual	Paweł Pawlak	F5
Dan Xu	Huawei	Ram Krishna Verma	Bell Canada
Dong Wang	China Telecom	Seshu Kumar Mudiganti proxy Shashi v.h.	Windriver
Gervais-Martial Ngueko	AT&T	Timo Perala	Nokia
Keguang He	China Mobile

Agenda Items	Presented By	Presos/Notes/Links/
TSC Chair	Kenny Paul	#AGREED the TSC approve cl664y@att.com remaining as the TSC Chair in a non-voting capacity until the new Chair is elected. Vote for TSC Chair Election - Nomination Deadline: Monday. Oct. 31st @ 23:59 UTC
Release Status	David McBride	Weekly update Kohn RC - Oct 27 London kickoff RAN Emulator - Source Code reviewed and merged by Lukasz Rajewski
RelEng/Infrastructure	Jessica Gonzalez	Tickets- Open showstoppers: Tickets- Waiting on Community: Migration Status / Upcoming Changes RELENG-4472 - Review Release Process and Documentation for ONAP Matt and Jessica still working, no further updates for now Responsibility for http://www.onap.org ; outdated link to documentation ; Ticket IT-24654 still an internal action item Mend scan jobs under https://jenkins.onap.org/view/WhiteSource/ Are they still needed? Can we deprecate them? #AGREED Cancel the license and remove the jobs GitLab - taking longer to get the pipelines set up than expected only chained-ci now.
PTL Updates		SO and MSB PTL Elections in progress OOF PTL - Call for Nomination - Deadline: Nov 2nd, 2022 may been some interest - stay tuned.
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Paweł Pawlak Amy Zwarico	SECCOM - new requirement as a follow up of unmaintained efforts: retirement of unmaintained repos – PROPOSAL FOR LONDON, but it does not make sense to apply to the new code (as per Best Practice state), as we consider old unused code, so we apply for Global Requirement. gerrit query to identify all the repositories that have been set to "Read only" - GET https://gerrit.onap.org/r/projects/?state=READ_ONLY The result will be captured in a *.json file Label is "unmaintained" in Jira For Kohn release, candidate repositories are tracked here: https://lf-onap.atlassian.net/wiki/x/1eb7 Paweł Pawlak New REQ Jira to be created for Retirement of Unmaintained Repos 21 Oct 2022 RELENG-4472 is the SBOM clean up
LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board	cl664y@att.com	LFN Board 2023 ONAP Budget has been approved i.e. Flat in comparison to 2022 (Gitlab migration not included) Request to present ONAP Status to the board on Nov 14th in Seattle (4.30-6pm PST). Material to be submitted on Nov 4th, 2022. Previous presentations: Community Updates for the LFN GB Paweł Pawlak will present to the LFN GB on Nov 14th. Discussion over providing info on the "mainstream" work to the GB. Update on the Mainstream work group next week. TAC -TAC Members will be able to nominate candidates soon for the following TAC Seats: 5G Super Blueprint: https://wiki.lfnetworking.org/x/1gpzB - 26 Oct 2022 17:00 PDT. Security: https://wiki.lfnetworking.org/x/1ApzB - 26 Oct 2022 17:00 PDT. New TSC will need to appoint a representative for TAC TAC meeting info - https://wiki.lfnetworking.org/x/5AAF -Need to provide a date to present ONAP to the TAC in November (9th or 23rd) or in December (9th or 23rd).
ONAP "Portal Next Generation" PoC	Georg Schweflinghaus Andreas Geißler	New Project Proposal for a successor of the ONAP Portal (presented at the DDF https://wiki.lfnetworking.org/display/LN/2022-01-12+-+ONAP%3A+Deutsche+Telekom+Portal+presentation)
TCC / ONAP Liaison Updates
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise		Next ONAP/SABRES working group is scheduled on Oct 26th Next Enterprise Task Force meeting is scheduled on Nov 2nd
TSC Activities and Deadlines	David McBride , Dan Timoney	Vote on the ODL Code transfer to ONAP Discussed in the TSC on Sept 22 Magnus had requested time for review Discussion - licensing exception needs to be timebound. suggestion of 12 months. cl664y@att.com invite Dan Timoney to 27 Oct 2022 TSC meeting ~~#VOTE: Does the TSC approve a licensing exception for the ODL RESTCONF API code in accordance with paragraph 7(c) of the ONAP charter?~~ To be discussed again next week.
Upcoming Events & Housekeeping	Kenny Paul	ONE Summit NA Nov. 15 & 16 2022 Seattle, WA, USA Please Register LF members receive a 20% discount with code ONE22LFNMEM LFN Developer & Testing Forum NA Nov. 17 & 18 2022 Seattle, WA, USA ONLY 2 days Slightly different format based upon the feedback we received from Porto General Very short kickoff No daily summary sessions No closing town hall Day 1 1st hour to be a cross- project session where each project brings a problem to the community Community brainstorming the rest of the day - 1 hour per problem/topic Day 2 More traditional D&TF sessions Content will be curated by the program committee more than usual given the short time available Committee strongly recommends making demos available via YouTube rather than requesting sessions to demos and general project readouts. Submission deadline: Friday, October 28th - Soliciting topics for LFN D&TF Nov 17-18 (onap.org) https://wiki.lfnetworking.org/x/YwNzB where should we discuss the ONAP's cross community topic for day 1 Add to PTL and TSC agendas for next week. Input from ONAP workgroups also welcome One slot per community, ONAP to decide which issue to present to LFN Community ONAP Day 1 Topic Page Input to be provided by 26 Oct 2022 TSC will chose the topic on 27 Oct 2022
<Available Slot>

Zoom Chat Log

07:00:09 From Chaker Al-Hakim to Everyone:
#info Chaker Al-Hakim, Independent Consultant
07:00:15 From N.K. Shankaranarayanan (STL) to Everyone:
#info N.K.Shankar, STL
07:00:34 From Magnus Buhrgard, Ericsson to Everyone:
#info Magnus Buhrgard, Ericsson
07:00:44 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
07:00:45 From Keguang He(China Mobile) to Everyone:
#info Keguang He, China Mobile
07:01:03 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:01:12 From Martial Ngueko(AT&T) to Everyone:
#info Ngueko Gervais-martial, AT&T
07:01:23 From Dan Xu (Huawei) to Everyone:
#info Dan Xu, Huawei
07:01:30 From Ram Krishna Verma to Everyone:
#info Ram Krishna Verma, Bell Canada
07:01:32 From Paweł Pawlak to Everyone:
#info Pawel Pawlak, F5
07:05:41 From Kenny PAUL (LFN) to Everyone:
#vote Does the TSC approve Catherine Lefevre remaining as the TSC Chair in a non-voting capacity until the new Chair is elected? +1, 0, -1
07:05:45 From Magnus Buhrgard, Ericsson to Everyone:
#vote +1
07:05:45 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:05:46 From N.K. Shankaranarayanan (STL) to Everyone:
#vote +1
07:05:49 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:05:56 From Ram Krishna Verma to Everyone:
#vote +1
07:05:59 From Dan Xu (Huawei) to Everyone:
#vote +1
07:06:00 From Paweł Pawlak to Everyone:
#vote +1
07:06:01 From Keguang He(China Mobile) to Everyone:
#vote +1
07:06:02 From Martial Ngueko(AT&T) to Everyone:
#vote +1
07:06:11 From Chaker Al-Hakim to Everyone:
#vote +1
07:06:25 From Kenny PAUL (LFN) to Everyone:
#endvote
07:07:33 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approve Catherine Lefevre remaining as the TSC Chair in a non-voting capacity until the new Chair is elected.
07:07:46 From Kenny PAUL (LFN) to Everyone:
https://lists.onap.org/g/onap-tsc/message/8985
07:30:40 From Magnus Buhrgard, Ericsson to Everyone:
Thanks Pawel, I can help
07:31:00 From Kenny PAUL (LFN) to Everyone:
https://wiki.lfnetworking.org/display/LN/Community+Updates+for+the+LFN+GB
07:34:04 From Kenny PAUL (LFN) to Everyone:
https://lists.onap.org/g/onap-mainstream/topics
07:51:31 From Catherine Lefevre to Everyone:
In addition
07:51:32 From Catherine Lefevre to Everyone:
gerrit query to identify all the repositories that have been set to "Read only" - GET https://gerrit.onap.org/r/projects/?state=READ_ONLY The result will be captured in a *.json file
08:23:17 From Cédric Ollivier to Everyone:
ODL uses Eclipse
08:35:57 From Catherine Lefevre to Everyone:
Dan Timoney is the ONAP PTL who is handling the ODL integration into CCSDK/SDN-C. It might be useful to talk to him if you need any additional information.
08:36:44 From David McBride to Everyone:
That's why I said that we need to get Dan's input on the timeframe before we vote.

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:47 Okay, Sorry about that.
07:02:56 Meetings being recorded, you all got to pop up like.
07:02:58 Please keep yourself muted. If you're on a phone, you can use Star 6.
07:03:01 Send me private chat messages. I'll cut past them into the public record, and we'll start with our antitrust policy This policy.
07:03:10 Is important where we have multiple companies, including potential industry, compared first participating in these meetings.
07:03:16 Please your view. If you have any questions, please. Contact companies, Legal council, number Slf may also contact Andrew up to Grove.
07:03:23 It's firmware to prevail. Lp: We could provide sleep with Council to the Ls.
07:03:28 And this product. This policy is in force. Whether there is anyone from Staff Chris on a call, or not
07:03:42 Okay, few things. First things. First, we'll talk about the new Tsc.
07:03:52 Got some release stuff. We have some infrastructure stuff, Have a proposal from Sitcom, which looks like came in Katherine.
07:04:09 I'll give a review of the Governing Board and the Tech
07:04:15 Talk about
07:04:19 Next year generation Portal. Alright. We've heard training Dt for a while about is potentially coming in and have a vote on Project for Odl code and then our standard. Care and feeding anything else anyone would like to add
07:04:46 Okay? And then shifting gears.
07:04:53 I had intended to send out the vote to have Catherine continue on as the Tsc.
07:05:02 Care I had intended to send that out via an email vote obviously that did not happen.
07:05:09 So first things First, I would like to put this out for a vote.
07:05:15 I'll drop it into the chat one down here in a second.
07:05:19 Basically, she would continue on his share until new charity is elected.
07:05:25 she would not have a vote on the Tsc.
07:05:30 She would just be the standing chair, So I'm going to drop that into the chat window right now.
07:05:41 Get that out of the way
07:06:10 in a couple more seconds
07:06:22 Okay, 5 more screen to one plank. Thank you, everybody.
07:06:58 Okay, So we have a The share election is employing the nomination Deadline is midnight on the thirty-first of October Pacific.
07:07:16 Time. Cool. Utc. So if you are interested, I'll copy the link and drop that in whoops.
07:07:26 I need to drop this first
07:07:38 now I will drop that one key
07:07:49 Just take a look at that email and respond. If you are interested in being the chair also, I will probably well, not.
07:08:01 Probably I I am going to set up a session for the an onboarding session for Tsc.
07:08:16 Members. Old members are happy, are welcome to join it, but I was sending it out to all of the new new Tsc.
07:08:23 considering how packed or or warnings are at least my mornings are, I will be setting it up in a Us.
07:08:40 And European friendly time zone, and then a second session up for an Apec friendly time zone.
07:08:48 so keep an eye out for that invite
07:08:56 Okay, I think that's it. Any questions for leading regarding Tsc.
07:09:02 can you? When do you plan to schedule those sessions
07:09:09 I? Well, I'll put a doodle pull out
07:09:21 And I'll I'll do. It is cause I I don't think you can combined poll those, so I'll probably do it.
07:09:32 One a pack poll, and and and one N. A R. E.
07:09:41 Otherwise I think it'd just get too messy. Okay, anything else
07:09:53 Thanks, Kenny. I don't think I need to share anything.
07:09:58 I just wanted to call attention to a couple of important dates.
07:10:05 we have the release candidates. Milestone coming up one week from today.
07:10:13 and then also remember, today is the kickoff of the London release.
07:10:20 There are no tasks associated with that. Just the the starting date.
07:10:26 Our first milestone, where we'll have really management task, will be M.
07:10:32 One which is on December first, and then I'm not familiar.
07:10:39 Katherine, did you add this this bullet about the Ran emulator?
07:10:47 yes, So last week there was a request. Raised by Shanghai.
07:10:45 I'm not familiar with that
07:10:53 he was asking if we could acknowledge 3.
07:10:57 Garrett, and well. When Masha check Lucas and I want to say thank you to Lucas was already not only reviewing the code and merging it, so I think Shankar, can you confirm that you are good now or is there any other blocker concerning the
07:11:19 alright, so thanks, thanks, Katherine and and David and Lucas.
07:11:25 Well, what was happening in the background? Was it sent an email asking for some merge to happen, and David raise this, Since that locus did the merge.
07:11:35 Thanks very much, and and they say no good deed goes unpunished.
07:11:39 Send one more request or 3 more. They were. There was something pending in one more It also has to do with the random emulator, but there was one more repo, and and so when I realized that I sent him one more email asking him to look at it but He has.
07:11:56 Been most cooperative. So somebody is the the thing that was raised last week got done, but after that we form a similar issue, and have sent an email request, and David, your CC.
07:12:11 On that as well
07:12:12 yeah, I think I saw that I I remember that. Now.
07:12:16 Okay, Great: Thank you. I I should also probably mention that I noticed that the the daily integration test on master has not been running recently, And I had an email exchange with Andreas and he said they ran into problems but they are working on that
07:12:47 yeah. So I I started it today, manually, and it ran successfully.
07:12:55 So we have the output there, although we have on 2.
07:12:58 let's say, links some failing a link here.
07:13:04 But everything is on, let's say, 100% besides. Then the let's say, usual security paths which are usually failing.
07:13:14 So the the the end-to-end tests are all 100%.
07:13:17 so I try. Or I hope that it's getting stabilized a little bit.
07:13:23 So we have issues in our lab in the Dt. Lab that sometimes then the pipelines are breaking, And this is just an issue I I raised with our teams here to check that.
07:13:35 Why this is happening. But whenever I see that it's somehow failing, I'll try I try to start it then manually, and hope that it gets through.
07:13:45 So, as I said so at the moment. The status is very good, and we are looking forward that I I think that will stay hopefully then in the coming week as well.
07:13:56 Okay, Great: Thank you, Andreas, and that's it for me.
07:14:00 Unless they're any good questions
07:14:15 Okay, moving. On.
07:14:24 Have a ticket here. Yes, are you on? Yep. I know that we couple of things that we wanna talk about here.
07:14:40 Yeah, I believe this is something that Matt was working on myth are doing the call
07:14:35 but let me open
07:14:54 I don't think so. I see him
07:14:56 Okay.
07:14:58 Yeah, I think he he he was working with Kevin on this, or with bank to be quite on hey?
07:15:06 I'm not sure who's working with
07:15:03 Yeah, yeah, yeah, it says no further updates for now, but just wanted to check
07:15:16 And got this ticket
07:15:22 On fixing the
07:15:27 Won't do this. I opened up. Check it. Let me check this one down, because that had to go through.
07:15:41 I think marketing, so I'll I'll need to follow up on that one's on me.
07:15:58 yeah, So basically wipers reach out to us if we want to renew the license with them.
07:16:07 I haven't been able to get information on exactly how much that's costing The project.
07:16:13 I'm working on that. What I know is that only only on App only the on a project is using it.
07:16:22 So. It all depends on whether the few jobs that we have in that Jenkins Tab are still being used by anybody that those jobs belong to a proof of concept that we were working with with the Security Committee But I'm not sure if anybody is accessing those
07:16:42 reports anymore. The The other thing is that the the white search team is reaching out to us to work with them on updating the unified agent that they they that is used to scan the reports So ideally, I I was still in Canada I wouldn't want it to
07:17:06 waste the white source Time, if we end up canceling the the license, or if we are not using these jobs anymore.
07:17:15 So I I rather hear from the team. If anybody still accessing.
07:17:21 These reports, or is still being used anywhere
07:17:38 Okay, Well.
07:17:42 Yeah, I know on the call, And if you're not making use of it, it would be a sitcom thing.
07:17:38 use it, using them.
07:18:00 That the Okay, yes, and yeah, I just wanted to make sure that nobody's is using the Ui access anymore.
07:18:10 If you guys are not using it, if I will, you're not using it, or Amy is not using it anymore.
07:17:53 So I'd say we should go ahead and and close it
07:18:13 Then we probably can tell the theme team to to cancel the license
07:18:29 I'm gonna mark that as an agreed
07:18:50 Well remote. The jobs now
07:19:14 just let's say the information that I I don't know exactly the same status of me house requests for the no migration of the getlap projects basically I had the feeling that it's taking really Obviously, quite long to get to pipelines up and running or
07:19:39 something so Still, we'd only have this. The chain Ci.
07:19:44 in so synchronized between Garrett and and Github.
07:19:51 I provided the code for the ex testing, and I think Mikhail was working on the Om install, and I think there, anyway, a couple of other projects which are pending I don't know exactly the status so mihail is not on the call here but I have
07:20:10 to say it. It takes quite long, obviously, then, to get it stuff running, I I mean, I'm happy that that the d change the eye is in, but without the all the other projects we cannot start.
07:20:23 The kind of pipelines on the Unh lab.
07:20:25 So it's requires still a lot of work
07:20:35 Chain, ci
07:20:40 That's chained as Oed chained and and dash other slash.
07:20:36 is that one word or 2, or hyphen
07:20:58 No problem.
07:21:03 Okay, Thank you for that. Update
07:21:08 Appreciate it. Lots of hard work going on there, so big.
07:21:14 Thank you to that. To this folks working on that
07:21:21 Okay, couple of Ptl elections in play. Call for nomination for over F deadlines.
07:21:36 November second. There's no deadline, if there's no deadline.
07:21:43 If no one steps up by the deadline, we have yet another headless project that we are going to figure out have to figure out what to do with
07:22:00 This seems to be a This isn't an issue that we really see elsewhere.
07:22:10 it seems to be a a fairly own app centric
07:22:20 Issue with these headless projects.
07:22:37 Well, it's in the context that
07:22:45 Yes, so I I'm saying this like in the in the context of code that is still dependent upon
07:22:58 Functionality in the code. Base that's no longer beings in in projects, it's no longer being supported.
07:22:24 you. I'm sure, Kenny, isn't it, that we are good at identifying and and handling it
07:23:04 That's the context.
07:23:13 So one comment on the skinny is on the Of.
07:23:16 Part, there is some. I just got an email today. In the morning.
07:23:20 There's some possible interest, and I'm encouraging the person to They are new, and they're trying to figure things out.
07:23:27 It's it's not from any of the companies We'll look at the La.
07:23:40 Yes, and that's the proposal of call for money Form a nomination.
07:23:46 I mean what we've tried to estimate a new thing.
07:23:51 This process was first to try if there's any committers within the project, wants to step up, and then, and then, after that we' a Tsc.
07:24:00 We usually launch a final call for nomination. The person can come from any company, but have commitment.
07:24:07 That at least they they will own and manage, or the project for for a moment.
07:24:15 So that's the proposed. Even if after that the Tc.
07:24:19 Had to do a an exception, because the person might not be a commuter c immediately, and could be a committers before being Pierre.
07:24:27 they will, It will require a Ts exception. But the most important, I believe, is find motivated people to continue to address and maintain this project, which is key.
07:24:40 One. We speak about net of slicing, or when we speak about Fivegs, some time, You you know, Shan Cap person, that I I do.
07:24:50 So I try to put some critical words. When I did the lunch, because that was my commitment.
07:24:57 Kishna try, and then we we as a Tsc.
07:24:48 yeah.
07:25:00 To make a final call. So let's hope you will be successful, even if the Tsc.
07:25:06 Have to make an exception, at the end. What it is important is to find motivated people who still can announce this type of scenario.
07:25:02 Yeah.
07:25:15 Yeah, you will come. I was actually surprised that people are listening, and there is some work going on that I was not aware of.
07:25:24 So I'm and encouraging people and and like, I said, it just happened today.
07:25:30 It's it's at least there to let people know.
07:25:33 And then we can follow the right process right
07:25:38 That's outstanding. So fingers crossed
07:25:47 Okay. Oh, do you want me to hand it over to you?
07:25:55 Or you want me to share
07:26:05 if you're speaking, you are on mute, sir.
07:26:23 Okay, let's come back to that. Might be some audio issues.
07:26:29 There.
07:26:30 Kenny
07:26:34 Yeah, sorry. Sorry. Can Can you move with the agenda to the next point and and come back to the to the second one?
07:26:32 Yes, Oh, I can hear you now
07:26:40 I have a some, some urgent things I need to follow.
07:26:44 Yes, happy to
07:26:55 sure. So We had the board meeting this week. In fact, it was yesterday.
07:27:05 We discussed, We spend a lot of time mostly on the budget on the overall budget, which is the consolidation of all the open so's called project, but also the the committee like what we need for the tech the Mac S PC whatever.
07:27:24 And I'm I'm happy to report that what we have submitted, and maybe I'm sure they've put the link to original submission, which was, in fact, we stay flat in comparison to 22 has been approved with the fact, that we all agree that we are with the forest Yes, we agree that
07:27:44 the Gitlock migration will not be included, because it's normal.
07:27:47 It was no more the focus at that time, so good news, no good jet has been appropriate, and will he make flat?
07:27:54 No reduction then. After that we got a request from the board.
07:28:00 You might know that we have the ons, and then the Dts.
07:28:06 But the the ons will start. On November 15.
07:28:09 So the day before the Monday, In fact, when do Youness is not get started?
07:28:16 The board will gather all together, and they are inviting representative of each project to share a little bit.
07:28:24 I know what they are doing, what the intent to do.
07:28:30 So the link, you will see, was what we were presenting previously to the board, so I know that the Tsc.
07:28:37 Is still in transition. The deadline to submit.
07:28:41 The package is in 2 weeks, so I'm happy to help But I don't feel I should present to whatever or should should do all the deck because it had to reflect what you want to share As new Tsc but I'm.
07:28:57 Happy to support you If you need me, you can set up time, and we can work together on the deck.
07:29:03 but we need a volunteer to work on this package and to submit it.
07:29:10 By November Fourth. So is there any? Do you see?
07:29:15 Member who would like to nominate themselves and work on this package
07:29:22 It's only few slides. It's not like you have to explain everything in large, and maybe the material that you are using for this board can be used later for your discussion with attack
07:29:38 Yes, it's probably speaking. I could. I could try. I will be on the fourteenth, just just in case.
07:29:39 Usually. That's what I do. Okay.
07:29:51 Good.
07:29:54 So. Thank you so much. Parallel, and I'm sure that maybe they're older Tcse members would like to give you or help you to do it, but we will capture your name as the lead for the material in the presentation and as I said if I can help you for anything.
07:30:11 Let me know. You should have access to the website to see what was presented last time.
07:30:17 If you don't have access, we will make sure that we provide the material to you.
07:29:46 Hmm in Seattle. So of the messenger
07:30:24 Okay. You wanna come
07:30:22 Thank you so much. Bye one
07:30:34 So can we put the link to the previous materials, so I could know exactly what was presented. And you know, as a starting point
07:30:40 Yeah, yes, yeah, You see, the blue line community update.
07:30:47 No updates for the elephant
07:30:49 Yes, oh, yes, yes, that's for the elephant.
07:30:52 Yes.
07:31:01 K Catherine
07:31:06 yeah, just some idea. I wanted to share. So there is this work led by Magnus about started with the next 5 years.
07:31:17 Now it's the own up adoption, a task force.
07:31:20 Would it be appropriate to share some of it with the board?
07:31:30 I I can comment cranny. I I think that was what I wanted to maybe suggest to Powell.
07:31:39 we, because I'm just sort of digesting the the comments and trying to make heads and tails of it, and also to put in a a proposal for the Seattle meeting the the Dtf to have a session, there and so I I think that's a
07:31:24 Or to. Does the Tsa feel it's too early
07:31:57 good idea.
07:32:07 Hmm.
07:32:14 Yeah, with some planning to to say something about this in next week in the in the Tc.
07:32:20 It. I haven't had the the bandwidth to to to conclude that work this week, but and then then we can sort of check with the to see if there, happy with some conclusions out, of that and when then we could probably bring that in here
07:32:39 Okay, Okay, Magnus. So you take the point to to present next week.
07:33:01 and I I can. Take the opportunity that anyone who wants to be part of that sort of mail chain that we have you can subscribe to the It's called the own up mainstream, may list and and you will get access to all the the the comments.
07:33:43 go ahead and drop dead in
07:34:09 Okay.
07:34:18 Okay. Yes, shifting to the text. So just a reminder that there are 2 additional tax seat that have been open.
07:34:29 you can still apply, or opera via your tax representative, because I understand only the tech member However, to nominate the candidates, so we have still time.
07:34:17 Okay, shifting to the tech
07:34:43 Another week, about less than a week. If if you know somebody interested to be the tax seat for 5 years from looping or or security, ask them to contact contact the tax representative to be nominated the next stack call is set up i'm just looking at my notes on the
07:35:10 26. I don't know if somebody from the Tsc.
07:35:16 Would like to hit us on the tech next week
07:35:22 So typically the call is up running 2 Pm Utc 2, 5, to 2, 3 Pm.
07:34:59 Okay.
07:35:34 Utc if I don't mistake
07:35:42 Yes.
07:35:52 So that's that's something. Also you will need to think If there is nobody, I will have double hat, but it would be nice to start to think who could, be your except if you're waiting for the Tsc.
07:36:11 Chair to take it over. So let me know. The next is only 26 from 2 Pm. Utc.
07:36:21 To 3 Pm. Maybe we can capture the date, so I forget to put the dates on the time
07:36:29 And then when you are doing this, just a suggestion again.
07:36:36 You you you do as you want. Maybe you could reuse the material that you were thinking to the Elephant Board for your presentation to the Tech.
07:36:49 I did not commit any date at this stage. I was just highlighting the the slot that you could select, which is either November for not not November ninth November 20 third November December ninth I don't know if
07:37:08 There will be a December 20 third, so you have still time to decide which lot.
07:37:14 But the the key aspect will be first to decide what you want to present to the tech team Any question.
07:37:25 Well, what I've shared
07:37:37 Thanks, Katherine. So just want to take second here to to tease this out a little bit.
07:37:48 the
07:37:52 Default has been that the chair
07:37:59 Person for their E community is the designated yeah correct representative. In the absence of another delegate being being appointed
07:38:19 Is so? Is that something that this is a discussion, not a decision?
07:38:26 is that something that the good hmm members of the of the Tsc.
07:38:33 Wish to continue with that, or just make it a vice chair.
07:38:43 Roll. Just keep it with a on a pointed rep
07:38:50 and I think we should start from the discussion. If there are any candidates for the for the chair and vice chair.
07:39:08 Yeah, I don't think that we have
07:39:12 Any responses, yet
07:39:24 Oh, wait! I hope I I I open that, but it pops up There's no responses that I see as of yet.
07:39:35 the reason that I'm asking for a discussion here is, if there is the expectation that it would be the chair, or whatever that might, that that that might impact somebody wanting to run forward or not.
07:39:54 So I guess we'll we'll we can.
07:39:57 Denny.
07:40:09 Hi Kenny, maybe a basic question. And you want to cover this in the onboarding of New Tsc Member.
07:40:00 We can bookmark this and and and as a think about, but we will need a new. We'll need to rep some point
07:40:21 the tack is the Technical Advisory Council.
07:40:26 it is comprised of a seat granted to Member platinum.
07:40:35 Members of the Lsn. Governing Board, and to to the projects that are in graduated lifecycle.
07:40:46 State. It is something that I would be covering in the onboarding in more detail, but it's the group of people that look at.
07:40:59 How to best enable cross collaboration and recommendations, and in terms of best practices, the project should be adopting, and things like that.
07:41:20 Okay.
07:41:22 can. It? Do you think we could come back to the second topic?
07:41:25 50 ticketed. Yup. Would you like to share?
07:41:28 Thank you.
07:41:32 Hey, if you can open the presentation, it would be easier, so obviously we we have a requirement subcommittee on Monday, and and I've seen And Tima was was sharing the invitation.
07:41:52 So we will present th those requirements as well there.
07:41:29 Or do you want me to share
07:41:58 Oh, I think you need to open it from the
07:42:06 The The key point is that maybe it's more like a discussion point, and I will.
07:42:10 I will cover it in a in a second. That's as you guys, remember, or for the new Tsc. Members.
07:42:20 We had the we had this notion of having talk proof of concept, then best practice, and you best practice was applying for the new codes and the global requirement that was applying for all the all the on up I call them projects.
07:42:37 Right so here, I'd like to simply summarize the global requirements that we have already approved by the invited.
07:42:47 You see in the past it concerns the python language update, Java, the update.
07:42:54 We have some progress, and just leftovers to complete.
07:42:57 So I hope that we could achieve this goal within the London release.
07:43:05 We have also continuation of packages, upgrades for the direct dependencies.
07:43:09 So this is also progressing for for some projects we are successfully in one and 100% upgrades every even for the for the con release for some due to the limited resources it's unfortunately, not, the case, and the continuation of se of of badging score improvements procedural level for
07:43:33 some projects. It's even for the goals. And this is also the new.
07:43:37 The requirement that we'd be. Let's say, in correlation with the London.
07:43:41 London. Release! Right, But these are the every release requirements for a few releases, so nothing new.
07:43:48 So if you go to the next slide.
07:43:52 We have a new proposal for for the for the global requirement.
07:43:57 So we have security locks, fields for Java.
07:44:00 So we'll Pineeman is is leading this topic, and we had a lot of exchanges with the ptls.
07:44:12 I think the community is pretty aware of this of this requirements, and the new one in green.
07:44:18 So this is for the unmaintained repos, and this is the so.
07:44:24 This is requirement from the from the from the previous release.
07:44:26 So we'll build a new new new version for the London.
07:44:30 The is a retirement of unm maintained repos.
07:44:34 So, as you know, Amy, with Mundasa, and with Thomas and and some other folks.
07:44:40 worked hard to, to, to to, let's say, to develop the process for the amendment repos.
07:44:51 but here we have a. We have some discussion point, and I'd like to to to get advice from the Tsc.
07:44:59 Because normally best practice apply for the new code Right here we are talking.
07:45:04 Okay, we have some old code. We want to get rid of it and it doesn't make sense to go to the best practice notion right?
07:45:14 Because it would apply for the new code. And here we are talking about the old one.
07:45:34 I just point out that we, the Tsc. Have this discussion last spring, and at that time, anyway, the the the Tsc.
07:45:17 So the question is, if it would be possible to to to to get this retirement specifically for the retirement of the unminded 3 post to promote them from the park to the global requirements
07:45:43 Rejected this suggestion
07:45:45 so I just want to. It's just 1, 2, explain.
07:45:47 Okay, there is a, there's a new Tsc: So Yeah.
07:45:49 Yes, I I want
07:45:54 Yes. But you need to explain the why, which is probably not the reason of today.
07:45:59 So, the reason why that you see, was rejecting at the time.
07:46:05 It's first. The request came in in the request to he died.
07:45:52 Thank you. Thank you. David. Hmm.
07:46:09 On maintaining repo game within release, and we didn't want.
07:46:15 There was nothing of socialization with the Pta, which is not the case today.
07:46:20 The majority of the unminting workforce was not there.
07:46:24 So it's a need for home context, I think. Here you are proactive.
07:46:28 We are not in the middle of one. You are planning to introduce these requirements within the right timeline. Right?
07:46:38 I would say. There's been a lot of socialization about the benefit and about the work you are doing.
07:46:43 So I'm I'm pretty sure that the it it will better receive than one year.
07:46:50 Okay, right? So that's why I wanted to have context to not influence and say does mean, reject wise and and no, it's a different context.
07:47:01 There's been a lot of work over the last year to socialize.
07:46:51 Yeah, yeah, true?
07:47:05 the great work made by the working group, the unmaintained working group superintendent's supporting by architecture.
07:47:11 Exactly.
07:47:14 Ptl. Know what you intend to do, and, as you said, it's not the only robot requirement who became immediately Oh, gloomy department because it did not make sense to be a best practice, You did a Poc.
07:47:29 To demonstrate the value. So for me, it's a different context.
07:47:34 But, as you said, it's up to the new Tsc.
07:47:36 Now to take the decision no later than in one.
07:47:43 But but if they want to decide today, they can also do so.
07:47:53 Thank you. Catching very much. Appreciate that intro guys Any questions for for for this one, because, as as captain mentioned, the team working on Mondays, spent really a lot of efforts and time to document the process to have exchanges to present it to set to Tsc to Ptls
07:48:17 So I think whole community is aware of the of those efforts, but we want to formalize things.
07:48:26 We all know that there are some repos that are UN maintained, and you know not used and so on.
07:48:34 So we should have a process to remove them, not to use the resources for scanning them not, you know, to document it properly, and so on.
07:48:42 So we need to have some exit, criteria and exit.
07:48:48 and we we did just have our first successful test case, too.
07:48:46 Exit. Option. Right?
07:48:49 Is there any question
07:49:03 So? Is there any question, especially from the the new Tsc.
07:49:18 hey paddle to the shocker, so I I think what would be helpful, especially for the new members.
07:49:29 Is to make sure that we have an active link to the list of unmaintained projects or repos.
07:49:40 So this way it can be referenced from a from an official document, if you will.
07:49:50 So everybody knows what the unmaintained repos are on regular basis, otherwise people will be looking for The references may be looking for the references or for the data in the wrong place.
07:50:05 So with whatever you think that Repo is, I would include it.
07:50:16 Can I comment on that? So the the way this came about is that we're using the version evolution.
07:50:10 I would include the link in this document. If this is the official document that we want to maintain moving forward, of course
07:50:28 Tool, that I think was developed by Margon, and to find candidates for the process.
07:50:38 And what what I've done is because we wanna track those as part of the the release process.
07:50:49 And so I created a a page in the cone release that has the list of current candidates that that we're looking at.
07:51:12 Absolutely, absolutely absolutely And the additional point that I'm making is that if somebody is looking at this document, they should be able to click on a link that takes them to that repository.
07:51:09 yeah, yeah, that's
07:51:29 Yeah, yeah, So that we do mind to to add this link to the to the Wiki.
07:51:24 That you just mentioned David. Otherwise they wouldn't find it. They wouldn't be able to find it right
07:51:43 Yeah.
07:51:50 Absolutely. And I could certainly edit to the architecture subcommittee.
07:51:55 The Rcom Portal to make sure you know I'll reference whatever you reference over here.
07:52:00 yeah, yeah.
07:51:58 So we're all pointing to the same source. Yep.
07:52:03 Yeah, any in addition to that, in addition to that, because you know, it might change at any times what we did.
07:52:16 There was a query that was created by It's a query that you can use to in typically when they are set to hit.
07:52:27 Only they are in unmaintained. So I have just posed the gay query that people can use if they want to know what anytime the the the list, of repository that they've been undergo and maintained, or archive and usually this comment will hit off to a Json
07:52:51 we also created a tag for the the Jira issues right, I should say a label label is unmaintained, so you can do a search in own app Jira, for you know label unmaintained and find all of the ones that that the
07:53:25 okay, Kim, I have a formal question. Is it the right right time and place to ask for some voting?
07:53:32 Or you need some extra time, or maybe and that's some additional questions that we could answer to give you the right guidance on on the Hmm.
07:53:43 On this request for the retirement of unnecessary repos.
07:53:57 Katrina, what would be your suggestion Can we?
07:54:03 so I will. Who comment that if there is no other question, maybe we can make an attempt to have a vote here if there is no question, especially from the new Tsc.
07:54:18 Who might discover this, or if we give 1 one, we get Sc.
07:54:24 As I said, we had to have a decision before the end.
07:53:59 How can we move forward? Please.
07:54:26 One, which is next week
07:54:30 Oh, so the before the M. One which is, I think, next week I need to look at.
07:54:35 no, it's December first.
07:54:36 The longer Huh! No, it's the Sc. Yes. Sorry Sorry we we have still time.
07:54:39 Yeah, yeah, yeah, yeah, our Rc: is for the R: our C: is for the cone release.
07:54:53 So you want to. Things I heard was that that additional information was was gonna be added to the to the slide deck.
07:55:08 Was that correct? Okay, So why don't we get that done?
07:55:14 And once that's provided.
07:55:22 We can go. So the the on. I'm sorry.
07:55:27 I don't know what I'm sharing at the moment.
07:55:30 That is what I want. So we've got a couple of things.
07:55:07 yes.
07:55:39 One is best practice. E. Tlc
07:55:48 Yes, wha what what I was gonna say is to in ensure that that we're we're being clear.
07:55:39 And if you can, so sorry for interrupting yes, if I if I make complete the the because these are the new global requirements right
07:56:07 No, no, no! This one is for the security locks, fields, right for the retirement they will.
07:56:11 The there must be like brand new created, I mean, we had the We had this talk right so from Park we would like to go to to the global requirements.
07:55:56 We're talking in this case about that requirement being made, the global require
07:56:23 So so here will be another requirements that will be brand new.
07:56:24 Okay. So: So: So yeah, so let's yeah. So let's let's let's create a new wreck on that.
07:56:31 And then that's what we'll vote on.
07:56:30 yeah, yeah, yeah, exactly. We're talking about 2 different requirements over here. Yeah, sorry.
07:56:30 One, yeah, yeah, yeah, Yeah, So we will we will add it for the yes, we will add it.
07:56:38 We'll add it as a as a for the next, as the final final, and see draft proposal with the link from David, or with the with the Garrett command. Right?
07:56:36 Yes, I'm sorry.
07:56:56 So you could have a full part of the information for for the for the retirement of I am, and maintain repos right
07:57:05 And if you could
07:57:06 So to based on that, maybe given to the week. Be give another week to the Tc.
07:57:11 Yes, yes, yes, if it's if the deadline is December, we would.
07:57:12 So you can finalize the material based based on what
07:57:20 Send it in advance, and maybe suggest the whole check. Or what do you think a vote next week in giving off time for anybody to good? Their mind again?
07:57:29 On this requirement, and then postponed the vote to next week.
07:57:32 So we all the material already, and have you able in advance.
07:57:07 so I just
07:57:42 it's it sounds good to me just I just wanna make sure we're on the same.
07:57:16 Yes, yes, yes.
07:57:36 Does. It sounds good
07:57:46 Page. So someone is going to create a new requirement. That would be attached to the retirement of unmaintained repose that we could always all track right So we'll have a requirement number because I will take that requirement number and I will create we will create from the architectures
07:58:06 subcommittee perspective, a Track in Jira ticket so we could track all these unmaintained projects, and when they come for review, and you know all the updates.
07:58:19 So so at least, we have a way to track the their progress as well.
07:58:23 Okay, Thank you. Alright. Thank you.
07:58:25 Yeah, we we might want to talk about that a little bit shocker, because the the working group has come up with a an Oregon is a Jira organization for for doing the tracking and and you might want to do your tracking in combination.
07:58:29 Okay.
07:58:46 Okay.
07:58:44 With what we're doing rather than creating a new set of Jiras.
07:58:49 Okay, I could do that
07:58:50 but you. You might want to attend our meeting on Monday morning, so we can talk about that some more.
07:58:56 Okay, Okay, so we do. I will.
07:59:03 perfect. Thanks. Thanks So much. Okay, guys. I don't want to hijack for all the meeting.
07:59:11 So if we could please go, to the last slide. That's presents.
07:59:15 Yes, that presents the best practices and folks that we plan to to to move forward with the London release.
07:59:25 So we have basic image from integration. As we had no resources to to to to progress.
07:59:32 So this is like, let's say, continuing in this level, we have also.
07:59:40 it's more in informative for the for the Tc.
07:59:42 Then we would like to as bombs for the entire on up.
07:59:49 And this is more on the Ptl and Lfn.
07:59:55 Engineering side how to organize the work. If there is no ptl.
08:00:02 If the elephant, it could do the the the asbound creation.
08:00:06 We know the process, we know how to do it. It was already there were several box already done Mutasa is leading this topic, and I think here also overall community has a good understanding of the work that needs to be done.
08:00:20 So we'd like to for that London release to generate the the Asbomb for each, and every project under on up, and we have to to proposals for the box One is the let's say the it looks management like continuation of the efforts and brand new one for the
08:00:44 security Lox fields with the python, Both Heineman is is working on it, and leading this topic.
08:00:54 He's already in touch with with with Pts.
08:00:57 He's working with Vj: So I I think we do.
08:01:01 We good good step forward to to have the starting point with the talk.
08:01:22 It's it's John here from cps just on the as forms, you are aware, there's still an issue that the teams are.
08:01:06 Yeah, So these are the all items we we plan to to do a sitcom and open for any questions
08:01:32 Did implement the Esp in in own timeframe. There's a problem with the Release process. Around here's bumps
08:01:42 I think what Doesar mentioned something around it? Let's
08:01:49 I've just shown you. There's a blocking issue You can't roll out the asborn until that issue is no Yep.
08:01:56 Okay, that's good. Yeah, no. Just want to make sure you're aware of it.
08:01:53 Do? Do we have a ticket? Do we have etiquette open for it?
08:02:00 That's all
08:02:00 Okay, Okay, but but do you do you know the reference ticket for it?
08:02:08 No, I think Matt will just say it. I don't have it handy. I can see if I can find it, and then and and ping it over to you
08:02:16 Yeah, I think, Yeah, to be honest, to take, it wasn't specifically covered a few issues, and I kind of have to raise some concerns about that.
08:02:26 But Yeah, it's part of, I think a bigger ticket.
08:02:13 Okay, if possible, to share. So we could have a, you know, some some reference point, and we could work on it
08:02:28 But I'll see if I can find that ticket
08:02:38 Yeah.
08:02:29 Yes, be sure and if not, let's create a very specific to this one, because I don't want to have this as boom efforts blocked my mood multiple, issues, but directly, for by the one that that is there I know the moodas are work with with Jessica to solve the all the issues
08:02:47 and my my perception was that we have already the process.
08:02:52 We know how it should be configured, modify it, and so on.
08:02:55 Everything is in Jjb. File or whatever. I'm not that much, you know.
08:02:42 Yep.
08:02:59 Experts here, but it's just a matter of applying configuration
08:03:02 Yeah, I know the handsome generation of itself work. There was a problem with the release process that was caused by the way the Asb form file name was generated.
08:03:11 Okay, let's track it. Let's track it to flying.
08:03:18 yeah, and actually that you know that Jira issue, Kenny, that you were looking at earlier from Matt.
08:03:14 Okay, Thanks a lot.
08:03:48 not a question, but just a suggestion. On the previous slide I saw that there is a process for retiring project which was approved earlier. Right?
08:04:03 Yes, we have a We have a weekend dedicated Wiki with the Rasi Rasi chart.
08:04:10 And Yeah, and we have quite a lot of documentation. So we will add this: I will last month to to add this information, or or David you.
08:04:00 So if you could provide a link of that process
08:04:17 We can also supply this one. Yeah, definitely. We we have a lot of source materials for this
08:04:25 You wanna
08:04:46 Find the right window. Okay? Fine, hey? You with the action item for the for the new girm.
08:04:57 And I know the jump. Get slide, deck.
08:05:05 Okay, onto portal next generation. Who should I hand the sharing over to
08:05:12 you can give me the sharing right? So I'm gonna ask you
08:05:25 Yeah, welcome on my side. And from Geeks side, who is also on the call here.
08:05:31 This is the gay, O. S. S. A. S. Ch. If you see him in a in the members list here who was actually with me here to present or to makeup project proposal for the for a let's say a successor of the existing on our portal which is as we all
08:05:56 know, not maintained anymore, and also not even part of our let's say, default delivery anymore.
08:06:04 so it is, and Kalek had presented that on the Ddf.
08:06:12 in January. Already Let's say, the efforts Dodger Telecom spent on the teenap portal or on a on a in our case, Tina, Portal so that a telecom portal which is let's say, combining basically the old features of a portal
08:06:30 like launching off application user interfaces as well as replacing or adding, Let's say, a functionality which we have in the or hat in the bit Actually, so in sensation of services, and so on and also other features.
08:06:54 In there, and our goal is, or was, or is now actually to start to upstream.
08:07:09 This work, at least from starting from the basis and we would like to make a proposal then, for let's say, a new project actually and starting, as a pop in London.
08:07:23 Now to create, then to start with it, let's say first lightweight part, which is just about launching the applications, and then, yeah, if that is so far working, then trying to enhance this, then with the other features which we already have what we would then also upstream, But first, we would
08:07:45 like to to. Let's say. Start with a with a pilot of that.
08:07:51 which is in here, Maybe it's get off.
08:07:58 may take over. This is the the let's say, export over, a wiki page we have in our Dt.
08:08:06 Vicki. But of course that would be. Then we would then put as then oh, project proposal, or get this input, into, I think it has to be done in the a project proposal page on our Wiki actually Yeah, So basically, Yeah, it will should then Replace: our
08:08:34 success, the the existing portal which we have, and a little bit is she is shown from the from the architecture point of view.
08:08:56 Yes, I can provide some details, maybe, where we are, where we stand.
08:09:02 So this is not coming entirely unprepared from from our side, as you may have noticed.
08:09:08 So we've showed where we are in the internal development.
08:09:13 So we've started an internal tasks, or let's put it to some component to have a portal for our activities, which are right.
08:09:25 Now mainly centered in the radio area, and what we were looking at was, which parts can we share in the first go and and layers?
08:09:37 What was happening us to to scoop this a bit, and what we, try to achieve is to look at can we really split what we internally develop from what we can can provide?
08:09:52 And can we have it as a basis for that work? So this is what we we're performing.
08:09:56 I I can't say that it's 100% done, but we have have cut out or affected our code into also a community edition, and this is something that we could then offer as a proof of concept and as I see it, and what I experience.
08:10:18 Right now. It might be whites beneficial for the whole solution, because right now we are having a few issues that we see on our side, like we have this issue with the Sdc that is still requiring a token and where the portal, in the future could play, a role to
08:10:44 yeah, they basically authenticate authorize users, be be the portal to to to enter the system and the various front ends, having it authorized.
08:11:01 And yeah. Also then in the future provide more than the very basic functionality for the commute. Do you?
08:11:09 So that that might be a start. I I can't say that we are can provide something fully finished.
08:11:17 This is why we think we should start with a proof of concept, and not just with something in a release.
08:11:22 and I guess this is also I I don't know.
08:11:25 That's so. You are the experts, There, maybe.
08:11:41 so it One thing which I would like to add here is, as you see, we're that's all the portal is you using actually key clock as well.
08:11:53 And that would also fit quite well to the let's say, focus in London release which I might definitely present next week, as well on the Ptl call, and maybe also in the Tsc.
08:12:07 About the updates for the service mesh release, where we also have for external access the entry for user authorization and authentication.
08:12:23 We introduce, anyway, a key clock to that that would fit quite well into the let's say, overall strategy and the overall target for London which we see from the on team as well the Kong here is, I think something we will not put here.
08:12:43 In that our AD as a component. This is just in the picture.
08:12:46 Yet so it will work without kong, without any Api gateway, internal because it's not required here.
08:12:54 So yup, the let's say, add additional part would be, then these kind of components of being part of the portal, and that would be then the the idea.
08:13:08 To put this as as as proof of concept.
08:13:15 yeah, if there are any questions, or any any any comments to that, I otherwise I would have the comments.
08:13:27 So how is the process actually to get into or to to integrate us or integrate the code into the pro into, let's say, our gabbit of let's say, project structure how to go well, how do we go forward with that So first part would be of course, that we
08:13:50 put on this the content of the slide in a in a project proposal that would be fine.
08:13:57 Put more slides, maybe, on that. And to document that.
08:14:01 But I think we would need to have then need to have the possibility tend to get get it a repository for that That would be, I think, my question how we proceed with that the next step
08:14:20 So basically as as we walk through what you had we're displaying there on the process.
08:14:34 And basically we we follow that as a proof of concept awesome.
08:14:32 yeah.
08:14:46 In order to make this open to the community, we need a a community based Repo: So part of the the approving.
08:14:52 Hmm.
08:14:59 This as a at as a a draft. You can approve something as a project, but going into the release as a Poc
08:15:11 Yeah.
08:15:13 So that would be my recommendation of the approach that we take is that that falls in line with with what we have here, and then then handles the repo creation, and and everything that goes along with that and so basically fill it out once completed, it tsc is notified 2 weeks.
08:15:43 and then the the Tsc. Would vote on the propose me project.
08:15:52 So I mean, just walking through the the Alright. The process should be able to to to get that done.
08:16:17 Kenny. One thing I I know: we have the concept of a Poc for requirements like for a use case.
08:16:02 Cps did this most recently. So if there's any any undocumented gotches to the process, Yeah, Yeah, Yep.
08:16:25 But do we have the concept of a Poc for a project?
08:16:29 I feel like we're
08:16:33 but I I thought that that's what we were describing here.
08:16:29 There is no concept of a Poc for a project so
08:16:42 Well, it going into the we're assuming this is targeted for the London room.
08:16:32 Yeah.
08:16:38 cause. The term poc is meant and mentioned several times
08:17:13 But that's for a requirement, not a project We're talking about a project.
08:16:49 Yes, it would have to go in as as a proof of concept right and by definition, proof of concepts, or you know formally not part of the release they they there can't be external code dependencies upon them, and there's all the rules that that or related to that
08:16:50 Yeah.
08:17:24 A, a, a, a, a, a project, is required to create a repo.
08:17:33 Right.
08:17:31 Yeah. That that's the that's the issue. So the first would be the th that there is a project, and the project is is, let's say, requesting a a repo to be great by Yeah, and gather it or multiple repos, and that's the that's let's say
08:17:43 Yes.
08:17:49 Yeah, absolutely. And And there's just I mean a process can be.
08:17:56 I'm sorry a project can be created. The repos can be created, and and then things are going to evolve from there.
08:18:06 We are never going to be in a situation where repose is is created, and it's immediately the C code comes in, and it's immediately 8, a a a dependent part, of a release it's always going to be like the the first go round is always going to be in it and kind of a proof
08:18:26 Hmm.
08:18:30 so So when you're using Poc: you're you're using it in an informal sense.
08:18:36 You're not using it in the formal sense that we have for requirements
08:18:47 I mean we We have a formally defined Poc for introducing new requirements.
08:18:43 it's okay. So
08:18:57 This it is so so so so yes. In that context, the discussion here.
08:18:55 We do not have a formally defined Poc for projects. As far as I'm aware.
08:19:06 Yes, being. Used informally. The request is for a new project to create a new repo, so that then the folks that want to contribute the C code to the community can make it available to the community
08:19:26 And the initial work on that is going to be done in an exploratory context.
08:19:36 And that exploratory context is what we're talking about generically.
08:19:22 hmm, hmm.
08:19:49 Hmm.
08:19:52 Okay.
08:19:55 Okay, so far, I understand. So we will have. Let's say we fill out all the the stuff which we have.
08:20:03 accordingly what we, what we are proposing, with all the required information which we have, we have to check.
08:20:11 What kind of project name we would take. So Hi, there! It's something like a portal of next generation, or something like that, or whatever cockpit, or at I don't.
08:19:42 When the the word poc is, or where the accurate poc is being thrown around
08:20:21 Know what we would like to do. That's something we we can't think or we can discuss.
08:20:28 Maybe then, in the next 2 weeks, when we come to that, or we define something I don't know if there's any preference for for something like that.
08:20:36 I would avoid to take the same project name as the original project.
08:20:22 Yeah.
08:20:55 Yeah, yeah, and and kind of an example of that. The original Dcae C: code.
08:20:40 Of course, so I don't know whether they, whether they are any preferences for the project itself. And then, of course, we would need them to check how the repositories would also be named them finally
08:21:04 Came in. And then that was basically immediately after that Dcae, Gen.
08:21:05 Hmm.
08:21:15 Yeah.
08:21:14 2 as a repost structure was created, and the original Dcae C.
08:21:21 Code was put into a locked repository. But we we only refer to it as Dcae.
08:21:18 Yeah.
08:21:28 Right.
08:21:29 Yeah, yeah, yeah, this is the old ones. And then this is just a new one that basically, yeah, yeah.
08:21:35 Yeah, So I I I think portal and G, or something like that, would be perfectly reasonable.
08:21:42 That would be, I think, also Portland G. Would be would be nice.
08:21:48 Yeah, that would be also my preferred one instead of a cockpit, or something like that. Yeah.
08:21:52 But then we can discuss with discussed and do the proposal accordingly.
08:21:56 Then in that by creating a new proposal slide here, and then we go forward.
08:22:04 Then with that, and I think we can also make some presentations of the current status where we have that already installed in our labs on top of our existing Jacoba.
08:22:20 Release and I think that's also what we can.
08:21:45 From my perspective.
08:22:23 Maybe then present in the next, in the next week, or in the next 2 weeks.
08:22:29 Sounds, great
08:22:30 Good.
08:22:38 just just the question what what licensing will be?
08:22:33 Looking forward to new code, good
08:22:39 Yeah.
08:22:49 Like, but
08:22:52 Yeah, licensing is fixed in the licensing.
08:22:50 I think yeah, sorry.
08:23:09 Hmm.
08:22:56 Is fixed in the charter on Apache 2. The next topic that we've got coming up, which is talking about the Odl Code transfer to own app is the one where we're actually have to vote because the licensing is an exception for that Legacy code
08:23:20 Hmm.
08:23:31 Okay, yeah.
08:23:41 Hmm.
08:23:45 Yeah. But I think we have already discussed this.
08:23:53 yeah, that's the internal consideration. To be honest, I would have to check it again, because that was already handled with our internal open source.
08:24:04 Let's call it offices. So month ago I will have to look it up.
08:23:50 I think then, that it's Apache 2 right
08:24:09 But yes, that's the current assumption. Yes.
08:24:19 Yeah, yeah, that's all. As I said, our understanding and we did a a license check across the everything that we use.
08:24:35 Okay, with the 5 min we have left, I'd like to shift gears to the legacy.
08:24:45 Odl Code transfer them so that we can get this in
08:24:55 This was discussed during the meeting on September 20 s.
08:25:07 it was put out. Basically the justification. Nobody else deprecating this code, will no longer maintain it own app is still dependent upon this code solution is to move the code into an own app repo where It would be maintained by and Ccsdk the code will exist in its own
08:25:25 dedicated Repo with the legacy licensing
08:25:34 Which is eclipse, comment.
08:25:38 So, that's what's being discussed and voted upon here.
08:25:45 on the 20 s there was a request to have some time to look at it.
08:25:55 we receive feedback that there are no concerns.
08:26:01 granting this is an exception, hi in the context that it's provided.
08:26:15 sorry, Kenya. I heard about that on the open the right side. I'm just a bit lost here.
08:26:24 you Want to to modify the code, or it's just about okay, no.
08:26:29 For well, see if it's to kind of get some model using the right the rightation.
08:26:27 No, it's it's not being modified
08:26:40 It's it's it's being deprecated.
08:26:35 it's there is no licensing issue
08:26:44 Yes.
08:26:41 And open daylight, but own app is still dependent on it.
08:26:47 And so the
08:26:47 Yes, but but you could still leverage a another an old open the light release Z. Then the one will remove the risk of the formula to have to ask for discount.
08:27:00 Yeah, we we we spent about. We spent 4 or 5 months discussing this in the Odl own App Sync meeting, and the conclusion was that this was the best solution
08:27:32 Yeah. Robert participated in those discussions as did Dan Timmy, and the ultimate conclusion was that the best solution was to move the code into own app and then request a licensing exception from the Tsc
08:27:55 And we we had about a I don't know. 30 or 40 min discussion about this on September 20, s, and it's been discussed extensively in the open daylight.
08:28:08 Own App: Sync meeting It's also been reviewed by Lf.
08:28:35 so? Can you. Does a shocker? Sorry. Go ahead. Are we going to be bound by a timeframe for this proposal?
08:28:48 What I mean by it is is this an open, ended proposal that would last for as long as it needs to last?
08:28:14 legal team. So I think we've, we've, you know, done due diligence in investigating it.
08:28:58 Or are we going to bind it by a or is it going to be bound by timeframe?
08:29:06 it when I talk to Dan about this, and there's a notes in the the the notes from September 20 s.
08:29:25 Okay.
08:29:29 Yes, yep.
08:29:33 I think the proposal has to be bound by timeframe. Right?
08:29:37 So I I've had the discussion with Dan on many, many occasions.
08:29:43 I understand how he feels by it, but I think we need to.
08:29:46 I don't know if 12 months is the right timeframe I know for the 18 months.
08:29:51 Is it? Is the right timeframe, but has to be bound by some time limit, and then revisit the discussion.
08:29:14 But he he expected that own app would deprecate this in the next year or 2,
08:29:59 After that otherwise it becomes open, ended.
08:30:02 Yeah, I I I'd like to have Dan's input on that.
08:30:08 Okay.
08:30:26 I think it. It makes sense for for this Tc. And new members here to to be able to to look at it in an email vote and and then not sort of and and keep it to this Tc: term.
08:30:21 Just okay.
08:30:45 So I think 12 months would be appropriate, and then to look into it.
08:30:56 the second question is, when the on that module will be updated to latest iotf stand up.
08:31:03 Oh, request, phone
08:31:07 So you you are using a formal draft. If I'm not wrong.
08:31:13 So now you somehow, you have to update on.
08:31:19 That must be updated according to what Otto is doing.
08:31:26 yeah, And that's what we're referring to about this code being deprecated.
08:31:43 Because this is important
08:31:43 I have the comment here, Because for okay, if you are adding some codes to to or not, I understand this code would be scanned with the clam drinking jobs right as we do, for the regular existing onup code right
08:32:02 Okay, when it's good, start, we would like to review the the outputs of the scans right for the sub software composition analysis with an exercise queue, and then to to see what are the vulnerabilities coming up of this code right and then sync with with Robert and
08:32:22 audio team on on on their plans to to upgrade their repositories, and so on.
08:32:01 correct.
08:32:31 Well. The open daylight is deprecating this code.
08:32:31 alright. So this is this is gonna be okay, right?
08:32:36 it's the even though he rem removing it's removing. It's not just deprecating.
08:32:38 It's it's it's
08:32:40 It was simply did before. Now it's fully removed for the nascent.
08:32:44 Right, So so the repo is going to be forked a new repo here is going to be created.
08:32:48 So assuming and assuming that we haven't, I mean, I'm assuming that the scans are already taking place in Odl.
08:33:10 how are we talk? Are you talking about scanning the odl repo?
08:32:35 This code is going away for open daylight
08:33:14 The new odial report that is being forked off
08:32:59 So based upon that, we would have a history right off the bat of what's of what's going in as far as
08:33:20 Exactly. Yeah, But I'm trying to understand. What is it that we're scanning?
08:33:29 Okay.
08:33:23 Well, no! No! What you This is this this is what I'm saying is, if if there are security, stand scan questions, we should be able to go and check with the current.
08:33:44 no, no, no, no! Sorry if you fuck something which is being which is removed It's only on your side, on on, upside.
08:33:41 State of that is in in Ol, and I don't know the answer that off the top of my head
08:33:53 Right, but correct, correct. But we would be able to understand the th.
08:34:10 but still I think that it should come from our scans based on updated databases of nexus IQ. And So on.
08:34:02 The current security state of the code coming in, which is what Powell was asking about
08:34:08 hmm.
08:34:19 I'll I'll I'll ultimately yes, I'm not saying it's in lieu of, I'm saying, Yeah, it will give us an idea if there is a concern.
08:34:37 Well, well, we have to be careful there, though, Right? I think I think the reason that we're forking off the Odl repo is because we are unable to make all the changes necessary.
08:34:49 To make within own app to support the new netconf interface.
08:34:31 About it before it comes in
08:34:55 So to me, it's a transitory, a process, or transitory, an approach So and that's the reason, right?
08:35:06 So it's very to me. It's very critical into Magnesis Point We it needs to be bound by a timeframe where we we as A. Tsc.
08:35:20 We should vote and agree on assuming any risks that we can that do exist with in the code base.
08:35:33 If there are any rooms that we need to assume, and then say within a year, then the repose should be removed, and now we should be able to use the no netcom interface that basically follows.
08:35:05 That's absolutely correct.
08:35:50 The itf standards.
08:35:58 Okay.
08:36:03 Exactly, and I'm I'm just maybe I'm repeating myself.
08:36:06 maybe it's obvious to a lot of people. I just wanna make sure that at least everybody I share with everybody what I know, and perhaps it's well known facts out there, but at least from my perspective, that's the reason for us to in in order for us we we need to be able to
08:36:25 bound the this effort with a specific timeframe, so that if there are any vulnerabilities to parallel point, then we need to make sure that we're all comfortable with the vulnerabilities.
08:36:40 And we need to agree that these vulnerabilities would last for X number of number of months up to a year.
08:36:48 I think Magnus is proposing a year, and it seems to to be fair to me.
08:36:52 But at the same time we need to make sure that we have a commitment from the own app team to implement all the changes that are required to support the new netcom interface
08:37:15 yes, and I yes, I I don't want to interrupt you, because I feel that there was a good dialogue.
08:37:15 I know that makes sense to everybody. Yeah, Okay, sorry.
08:37:24 But if you need additional information, maybe we could invite Dan to the next Tsc.
08:37:30 So we don't rush for any decision, because you need to feel all comfortable, and then you you you can ask any question that you might have from Dante, and and maybe later on you can think about something else so.
08:37:40 Okay.
08:37:46 Shall I invite Dante money next week, otherwise you can meet them on Monday or Yep.
08:37:50 yeah, Katherine Dan's been involved in the discussion all along the the discussion that we have with the Tsc.
08:37:51 Bye.
08:38:00 I know.
08:38:08 I I don't deny them as not being involved.
08:38:11 I just try and I know they are new Tsc. Members here.
08:38:15 They they may be heard for the first time. The discussion we might need to put them up to speed so that's why I was just offering to.
08:38:05 Yeah.
08:38:26 I was just offering to all of you the opportunity to have done on the bridge, and to ask any concern question that you might have.
08:38:38 That's it It's it's an offer you can say yes or no.
08:38:36 Yes.
08:38:44 I I think, Catherine this is shocker. I think it's a very good idea, right?
08:38:49 it, it, It seems to me that it does make sense to to to Dave's point David's point, We this issue at least from my perspective.
08:38:59 I've been looking at it for 6 months, and then has been gracious enough to go over it many, many times. Right?
08:39:06 I think what's missing in this proposal, based on my understanding and my understanding could be some off is the timeline, for when this exception X expires, let's say we about we bind it by the year and the second is commitment, from the own app team to implement the changes
08:39:33 required to support the new netcom interface
08:39:52 agree.
08:40:06 Okay, So you can put an action on me, and I will invite Dan to the next.

Agenda Items

TSC Chair

Release Status

RelEng/Infrastructure

PTL Updates

Subcommittee Updates

LFN Cross-Organization Updates

ONAP "Portal Next Generation" PoC

TCC / ONAP Liaison Updates

Task Force UpdatesCNF, Wiki 2.0, ONAP Enterprise

TSC Activities and Deadlines

Upcoming Events & Housekeeping

ONE Summit NA

LFN Developer & Testing Forum NA

<Available Slot>

Zoom Chat Log

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise

Browser not supported