661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2021 TSC Recordings	2021 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)	Gov. Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Alla.Goldner	AMDOCS	Fernando Oliveira	Verizon
Andreas Geißler	DT	Magnus Buhrgard (Unlicensed) alt. Tony Finnerty	Ericsson
Bin Yang	WindRiver	N.K. Shankaranarayanan	STL
Former user (Deleted)	Bell Canada	Ranny Haiby	Samsung
cl664y@att.com	AT&T	Seshu Kumar Mudiganti	Huawei
Dong Wang	China Telecom	Timo Perala	Nokia
Eric Debeau alt Sylvain Desbureaux	Orange	Yuanhong Deng	China Mobile

Agenda Items	Presented By	Presos/Notes/Links/
Release Status	David McBride	Istanbul Weekly Status email Documentation status please review open doc patches DOC (ISTANBUL) OPEN: Still issues with the doc builds caused by changes in lfdocs-conf for the following repos - cli - modeling/etsicatalog - oom - vfc/nfvo/lcm - vnfrqts/guidelines Check pending patches: https://jira.onap.org/browse/DOC-765 Check other issues: https://lf-onap.atlassian.net/wiki/display/DW/Istanbul+Documentation (Composite/Marketing) Release Notes not available 2 / 5 Jira issues closed Jakarta release schedule updated with recommendations from working group. Note that the milestone dates were previously approved by the TSC on Sept 30. These have not been changed. #AGREED the TSC approves the Jakarta release schedule (v.5) of https://wiki.onap.org/x/VIKfBg
RelEng/Infrastructure	Jessica Gonzalez	Tickets- Open showstoppers: Doc issue is the primary - 5 repos still need to be updated Super Committer rights will be utilized by RelEng for IT-23176 Tickets- Waiting on Community: Migration Status / Upcoming Changes
PTL Updates	Sylvain Desbureaux	Update on OOM GitLab migration status suggestion to lock the repo in advance of any migration to ensure that no new patches are submitted via garret when pilot is complete TSC will need to decide of what system will be used by the entire community will use - a split solution cannot be supported over the long term
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Alla.Goldner Timo Perala	Requirements Subcommittee have only seen a few requirements submitted for Jakarta Jakarta release - functional requirements proposed list ~8 requirements for Istanbul were reduces in scope and would logically be completed in Jakarta Need confirmation from requirements owners that they will be continuing in the next release David McBride will reach out to the 8 requirement owners to remind them about the process. 05 Nov 2021
LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board
TCC / ONAP Liaison Updates
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise
TSC Activities and Deadlines	cl664y@att.com	TSC Chair Elections - Nominations end Nov 10th https://lists.onap.org/g/onap-tsc/message/8241 TSC 2.0 - Project Life Cycle Initial feedback to review: https://lists.onap.org/g/onap-tsc/message/8060 https://lists.onap.org/g/onap-tsc/message/8061 Target the 28 Oct 2021 for update review to the document WIP - 2021 Project Lifecycle Proposed Edits Clock Changes (backward) in Europe on 10/31 and in the US on 11/7 ONAP Community Awards: Honolulu Release (Vote has been kicked off)
Upcoming Events & Housekeeping	Kenny Paul	PTL Call Canceled on 01 Nov 2021 TSC Call will be canceled on 11 Nov 2021 (EU holiday) & 25 Nov 2021 (US holiday) LFN Developer and Testing Forum, Jan. 10-13, 2022 , Virtual Event - PLEASE NOTE CORRECTED DATES! finalize text for website Topics Page ONE Summit Europe, March 8-9, Antwerp Proposal: 2 Day Developer Event March 10-11 Hotel Radisson (same space as last time) LFN Developer & Testing Forum, June TBD Physical Event Europe or Asia (preferred)
<Available Slot>

Zoom Chat Log

06:59:22 From Fernando (Fred) Oliveira to Everyone:
#info Fred Oliveira, Verizon
06:59:37 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
06:59:59 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
07:00:00 From Yuanhong Deng (China Mobile) to Everyone:
#info Yuanhong Deng, China Mobile
07:00:05 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:00:16 From N.K. Shankaranarayanan to Everyone:
#info N. K. Shankar, STL
07:00:51 From bin.yang@windriver.com to Everyone:
#info Bin Yang, Wind River
07:01:06 From Bruno Sakoto to Everyone:
#info Bruno Sakoto, Bell Canada
07:01:21 From Tony FINNERTY (Ericsson) to Everyone:
#info, Tony Finnerty, proxy for Magnus Buhrgard, Ericsson
07:01:27 From Sai Seshu to Everyone:
#info Seshu, huawei
07:01:27 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
07:01:57 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
07:03:01 From Sylvain Desbureaux (Orange) to Everyone:
#info proxy Sylvain Desbureaux, Orange
07:03:17 From Catherine Lefevre to Everyone:
#info, Catherine Lefevre, AT&T
07:09:02 From Kenny PAUL (LFN) to Everyone:
#VOTE - Does the TSC approve the Jakarta release schedule (v.5) of https://lf-onap.atlassian.net/wiki/x/S4j7? +1, 0, -1
07:09:12 From Andreas GEISSLER (DT) to Everyone:
#vote +1
07:09:13 From Fernando (Fred) Oliveira to Everyone:
#vote +1
07:09:17 From Catherine Lefevre to Everyone:
#vote, +1
07:09:17 From Dong Wang (China Telecom) to Everyone:
#vote +1
07:09:18 From Alla Goldner to Everyone:
#vote +1
07:09:18 From Tony FINNERTY (Ericsson) to Everyone:
#VOTE +1
07:09:18 From bin.yang@windriver.com to Everyone:
#vote +1
07:09:21 From Yuanhong Deng (China Mobile) to Everyone:
#vote + 1
07:09:22 From Sylvain Desbureaux (Orange) to Everyone:
#vote +1
07:09:25 From Sai Seshu to Everyone:
#vote 0
07:09:26 From Bruno Sakoto to Everyone:
#vote +1
07:09:27 From N.K. Shankaranarayanan to Everyone:
#vote +1
07:09:32 From Timo Perala (Nokia) to Everyone:
#vote +1
07:09:58 From Kenny PAUL (LFN) to Everyone:
#endvote
07:10:37 From Kenny PAUL (LFN) to Everyone:
#AGREED the TSC approves the Jakarta release schedule (v.5) of https://lf-onap.atlassian.net/wiki/x/S4j7
07:10:42 From Thomas KULIK (DT) to Everyone:
DOC (ISTANBUL) OPEN: Still issues with the doc builds caused by changes in lfdocs-conf for the following repos - cli - modeling/etsicatalog - oom - vfc/nfvo/lcm - vnfrqts/guidelines Check pending patches: https://jira.onap.org/browse/DOC-765 Check other issues: https://lf-onap.atlassian.net/wiki/display/DW/Istanbul+Documentation (Composite/Marketing) Release Notes not available
07:42:38 From Catherine Lefevre to Everyone:
Thanks Thomas - I hope these issues will be solved early next week
07:43:48 From Catherine Lefevre to Everyone:
Thanks a lot Sylvain - crystal clear presentation and I also appreciate the visibility about the next steps.
08:08:00 From Kenny PAUL (LFN) to Everyone:
+1
08:32:30 From Bruno Sakoto to Everyone:
Sorry I have to drop
08:33:34 From Timo Perala (Nokia) to Everyone:
sorry, need to drop off

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:44 Okay, I have started the recording, I started the transcript.
07:02:56 Reminder folks should keep themselves muted, unless you're speaking you can use star six to unmute yourself if you're coming in on a phone line.
07:03:06 Just send me a private chat message, I will simply cut and paste that into the meeting minutes, and it will become part of the record of this meeting.
07:03:19 So on Thank you, Catherine Thank you.
07:03:28 If I could get someone to volunteer to play gatekeeper for me.
07:03:32 I would appreciate it.
07:03:41 Start a meeting
07:03:43 that was Fred.
07:03:45 Yeah. Okay. Thank you, sir.
07:03:53 Appreciate that.
07:04:02 We'll start off by talking about our anti trust policy as we do every week you can find this link from the elephant the project websites. This policy is important for us, where we have these multiple app, where we have multiple companies participating in these meetings, including
07:04:12 these meetings, including potential industry competitors. Please or do you have any questions, please contact companies legal council members of the elf may also contract, contact, Andrew up to growth from Gizmo up to Grove LLP which provides legal counsel
07:04:29 to the Linux Foundation,
07:04:39 or as what we have lined up today.
07:04:45 Talk about the weekly status is going to be brief here.
07:04:50 We'll talk about the Jakarta schedule and get a vote on that.
07:04:58 Now there's a couple of it things that didn't get added there but there will probably need to talk about those.
07:05:06 Om get an update on the get lab pilot requirements subcommittee will be sharing their contributions and their achievements for the year.
07:05:19 Then we've got some basic housekeeping items that we will cover down here, is there anything anyone else would like to
07:05:29 like to discuss today.
07:05:37 So Thomas yeah I expect that documentation will be discussed during the updates for the upcoming assembled release, I think. Right.
07:05:50 Okay.
07:06:10 Very good. Thank you, sir.
07:06:12 Okay, um, let me double check that.
07:06:18 David's on the line he is I will stop sharing and David turn it over to you.
07:06:23 Alright thanks Kenny.
07:06:32 Alright, so the the release status fairly brief today.
07:06:41 I sent the weekly status email to the list. Yesterday, so you can read the details there.
07:06:52 I did want to talk about the Jakarta release schedule.
07:07:00 You'll recall that the TASC approved the schedule.
07:07:09 A couple of weeks ago or a few weeks ago, I guess.
07:07:13 September, 30.
07:07:16 And then there was some interest in updating the schedule to better reflect the, the continuous delivery aspect of the release process. And so, I had an email exchange with Magnus, and we agreed on this format.
07:07:43 This was shared with the PT else.
07:07:49 So, earlier this week, I think or last week I can't remember now.
07:07:54 Earlier this week, I think or last week I can't remember now. And so, we still need to get final approval on the schedule and remember this is not the dates, the the TSP already approved dates, but just the schedule as a whole.
07:08:08 With these additions that you see here on the bottom, showing the, the continuous delivery tasks that we have through a release cycle.
07:08:21 So there's some vote text in the agenda.
07:08:31 Do we want to go ahead and move to a vote, are there any questions about the schedule.
07:08:48 Okay hearing that I'm going to go ahead and drop the vote in.
07:09:12 And the vote is in the chat window so TASC members please pound the vote
07:09:12 was one, zero or minus one.
07:09:42 Okay, give a 10 more seconds.
07:09:53 54321.
07:10:01 And that has passed Thank you folks.
07:10:04 Right, thank you.
07:10:06 And then, Thomas you mentioned that you want to discuss documentation status I don't have anything specifically prepared for documentation status was there something specific that you wanted to look at the show, give only a short term status for the symbol
07:10:26 of the lease and I kindly ask people to to track pending Petrus and all the issues we have noted down in the symbol documentation page. I will put it also into the chat.
07:10:45 So, we still have issues with five repositories.
07:10:51 With the documentation for five opposite Tories. We have still a few pending patches. Other issues as we noted down. And I also discussed was Kenny that does a composite marketing release notes are not available yet, so.
07:11:09 So if we should add them to the release notes and would be good to have them in a agreed form and.
07:11:23 Yep. So, again, guys please check the pending patches and other issues that we can finalize the documentation.
07:11:35 Thank you.
07:11:38 It's almost a.
07:11:40 That reminds me that I did
07:12:07 I haven't had a chance to look at those the status of those Jerry issues, but those have been assigned to the projects that did have pending merge requests for the documentation.
07:12:20 Yeah. Now there are only a few, it's getting better here, but we also found some smaller issues, which we noted down in the symbol documentation page in the wiki, so please also check effect there.
07:12:37 what can be improved, or must be fixed.
07:12:43 Right. Thank you, Thomas, what
07:12:49 was there any questions regarding release status, just a reminder that sign off is scheduled for one week from today.
07:13:01 The sign off release management tasks and assigned to the projects and to the requirement owners.
07:13:16 And so I'll be following up on those in the coming week.
07:13:20 All right, thank you.
07:13:30 Okay. Um, there's nothing else on release then we will move on to
07:13:40 it.
07:13:42 Let's see who's got banked.
07:13:47 We do you want to run over. Do you want to run over.
07:13:53 You want to cover some of the some of the things you might want to run over me.
07:14:03 I know that there's some, some work in progress if you want to cover it.
07:14:09 I think the biggest one is the documentation that Thomas has talked about there was so far I don't think we've ever had any, Any outages, or anything on the infrastructure.
07:14:38 Okay. Does anything. Does anyone have anything they would like to bring up for for lunch.
07:14:48 When I was just wondering, also have we have to solve the documentation issue.
07:14:58 Thomas mentioned there was only like five reports left that have some issues with.
07:15:05 I've got one ticket in today regarding.
07:15:12 They wanted us to use the super committed rights to just add a plus two because they were out of commuters would rise to do that on the map project I think your schema free book.
07:15:24 I signed that on to you, Jessica, by the way.
07:15:30 Thank you. Yeah, I can, I can take a look in yeah if if everybody's okay with that. I can help.
07:15:37 I can help merging this change is there is there any, they only wanted a plus to some done could merge it yourself.
07:15:54 Okay Okay good. Okay, you're saying that to get to me right. Yeah. Okay, thank you.
07:15:56 Maybe we need to also help for other projects.
07:16:02 To do so to speed up the process because people are not reacting. So, yeah.
07:16:09 Could you interest.
07:16:10 If that's what you want, then maybe check in here and then raise a ticket.
07:16:18 Yeah to consolidate them. The missing changes that are a place where we can see where an amazing changes that will be there will be great.
07:16:28 But yeah, I mean if if there's no concerns about me helping out with a expected in this, then I can put up what I want to say is for the remaining issues, we have to do a deep dive per repository, because that the more tricky ones.
07:16:50 And let's see if some from the project, who can help or maybe we need a supercomputer that saves us.
07:17:10 The only Reapers left or the AI so and Seelye or
07:17:17 not trick trick was sent into the chat. So I'm looking at the dock 765 page. So, there are a few more CL I'm at the catalog.
07:17:34 Whoo M. As I, as I copied in the chat and also check, we have to check the documentation wiki page where we also noted down a few issues which are not
07:17:45 currently in the patch patch list.
07:18:07 I think that was it for me anyway.
07:18:14 Okay, anyone else.
07:18:23 Okay, thank you everyone.
07:18:26 Nothing, just a small comment, super committed rights will be utilized by rolling, that's not was that the court plan for everything for this, or was it just the ones that we asked, we were received a ticket for it or some release notes that they wanted
07:18:39 to be updated.
07:18:54 What's the ticket number.
07:18:58 I'll find it.
07:18:59 Okay, just pop into the chat window when you get it. Yep.
07:19:03 Can you, can I posted something into the chat maybe you want to have this also in the, in the notes.
07:19:46 23176.
07:19:46 Thank you.
07:19:50 do what I do, 1-376-231-7631 762-312-3176. Yeah.
07:20:07 Okay.
07:20:12 Then I will stop sharing and Sylvan you can bring us up to date on where we are with the get lab.
07:20:25 I look for Oh,
07:20:25 yes, you need to allow me to share my screen.
07:20:30 Yes, sir.
07:20:34 There you go.
07:20:37 Okay.
07:20:45 Let's share.
07:20:48 Okay, can you see different slides.
07:20:54 Full Screen.
07:20:54 Yeah. Very good.
07:20:56 So, this is a status update that was requested I think last week or the week before last week to release. I don't know how many times I am and. So, knowing me knows I can talk for hours so I will try to be as fast as possible but, of course, I will take
07:21:17 some questions at the end of the presentation.
07:21:20 So first, I will explain the main differences between Garrett and get lab.
07:21:26 As a different checks that are done today. In May, in on main repository.
07:21:36 Also repository under by M.
07:21:36 Released checks. So everything that, but are the checks that have done to this repository subset, I would say, of the checks that are done into our main repository.
07:21:51 So, that means that if we manage to make a minimum repository to work as expected, or just want to walk or service.
07:21:59 So administratively intimidating releasing and a small roadmap to to explain what, what can be the base for for that and, of course, if to see which Jessica, if you took it from there.
07:22:15 Okay.
07:22:18 So, there is a big difference in the Philadelphia between gate and get that is our new code submission is ended.
07:22:28 So guarantees a review based.
07:22:31 So that means that you people walking on gate will will work on one commit for a new feature or could you could submission.
07:22:43 and you will you will amend it.
07:22:49 In order to, to, to make a commitment, okay to, if you're not happy because you see it as an issue with what you have proposed and so and so, we added a new one commit so in in the Git repository before the marriage, it's a new one commits that will leave
07:23:08 with different amount on it, and changes on it.
07:23:14 So, and when it's marriage, you will have to commit murder on on the branch, as a target branch, one will be committed that you have walked around and Joseph one will be a match commit message.
07:23:27 If, at least on om people. That's how he's done maybe he can be done a bit differently and it was only for me but today that's always done on om on Twitter and GitHub.
07:23:39 Also, everything is mad request based. So, instead of walking into one commit, you will walk in a branch that will be on the same repository, or into a forked repository, and you create what is called the match request from this branch into the target
07:23:57 branch so your main branch matter. Of course, if you want to.
07:24:02 Because Julian, when you first one master main branch.
07:24:07 So master in a nap.
07:24:09 And then you will share to get to our branch if needed for.
07:24:15 If you, if it's a breakfast.
07:24:18 And that you want to back brought to zero.
07:24:23 And, and then every time you are not satisfied instead of amending your committee we create a new committee and push this coming into the branch. So to be clear, this is really feels a few different that as we know, change the life of the developers and
07:24:44 both of them have pros and cons I will not go into
07:24:49 that, but they will have some consequences on the way we work.
07:24:55 But that's not a senior impossible to 200.
07:25:00 So, as a first check we out with a good news for two shakes and the media for that it's just stuff that we check in order to be compliant with I would say Linux Foundation for DC, I guess it is just super easy.
07:25:19 So guys three nice checks I saw they know on an apple, and the other on what we could click on it, so that means that when you push your commute into.
07:25:35 You, you will, it will be rejected. If one of the three, check is not bath best. So first we will check that user seen it as a CLA have an app server and we will check that the either Eastern ID.
07:25:56 And last is to see, to check that we have got we've got the center of by. So I put my email but of course it's his email of the computer that is in the commit message, actually, that could be an email but I guess it's just a hex but at least you need
07:26:15 to do to have a signed sync permit, and history, and the ceiling.
07:26:21 So, as, as you understand, she's done as a pre commit.
07:26:26 So, because on on Garrett we have a full.
07:26:31 So fit at football on the agents who can add pick a message into a deep lead pipe at on the pavement wouldn't get lab. So let's say that instead of Garrett, we would have deployed the GitHub.
07:26:49 We could do the same but, of course, on a really clever, we can add some paper meter stuff, but if we want to do something a bit more complex like CLA, we need to do to use what we call jobs, CA jobs in the into the Thames.
07:27:12 And so that's what we do. So, we will our first job is that tweeted, check that user that is pushing the code that is part of the CLA these that is a present somewhere.
07:27:35 This is what the zoo is a pure see that as as done, Christopher during the summer, so we'll use it users is this good to do that. And we will also check the commit message, and we will see if it match, good execution.
07:27:45 So, issue ID signed off by but also titled buddy, because you see that that's something that we enforce it. So, in a in a in a different way.
07:28:12 So, just to say that she's a, you will ever fail so for four hours per meter so for me it would be very easy to see that.
07:28:07 One of the jobs that failed and to something needs to be corrected, Rick push the commit message and this one.
07:28:30 So in om today we have 1234567 insects that are performing using Jenkins jobs.
07:28:39 So, we are checking that there are no training species, no tabulation. That's, that's basis.
07:28:48 It's a some documentation, update, you we have some documentation in team with Doug, Doug building and ducking checking, and also spitting.
07:29:06 We are, We are also linking the geek comic message.
07:29:06 We mandate to have a data with a certain format and a big message I know that some.
07:29:18 We are validating that there is no fascism, so that she sends his using specific function of bash you know as a shin and Dr Darvish.
07:29:29 When you have generic for insurance, of which walks as.
07:29:33 into. for wholesale some that are available.
07:29:38 We are doing that because bash is GPM v3 so we try to remove bad data back from best clips from a om engine and.
07:29:51 And we have few items for it so where we are launching into a date.
07:29:57 Very soon so that's a very small part. And at the end we have Emily Doom main repo is mainly Elmer shots. So, there is a command in n, which is named Edmund.
07:30:12 And so we are using it on an order shot at the present in order to verify that there are no mistakes, so usually they are simple mistakes I would say, but, but still quite important to protect them as soon as specific.
07:30:29 So today as they said that they are don't judge inking jobs in the club.
07:30:35 We will, we will use a, what is a guru sort of job. Happiness stages or a specific moment which we will be named a LinkedIn.
07:30:47 And all of them will use a specific Docker.
07:30:51 Most of them are already existing and if needed, we will create a profile.
07:30:57 So, that means that we will have exactly the same behavior as before. So, a failed job. If one of these are not the
07:31:10 next one is a big one is gauging so as you may know, in every time some money, pushing a match request or so, new patch setting right now today.
07:31:23 We will try to deploy om with this
07:31:29 master Macedonia Shimla teach a seminar on a stable Russian with a master of action. We will, we will try to play with this new patch set and verify that behavior is as before, or better off course.
07:31:49 So to do that we have a bunch of micro services that that has been that they have deployed a long time ago. So mainly we have a listener on a previous show on gate controller, because we have a pool of forgetting systems.
07:32:21 And so we need to wait for proof to be available before pushing, asking these people to, to start the work. And so we have a with a walker. So we have a controller and Walker, listening, and in the middle of that we have a MTG to boycott MTG Israel a
07:33:00 a very lightweight and tools are topics that are created and summer, pushing a message to the beaker and others that are listening to this.
07:32:58 So in battle puter odds against events, pushed into gear peaks and in function of the topics as deep as the controller of the gating system will speak on it as a new metric Wester and and put it into a queue and when.
07:33:19 And when the water is already will send it to the walk.
07:33:24 And I went to Walker I finished the job so yes, try to deploy the om was dispatched, it will send, so he's huge into a defeat, and as Microsoft is actually listening to this topic, and pushing, Sacramento that has been done major component.
07:33:45 into into Garrett Yeah, its API.
07:33:49 So, obviously, this won't work.
07:33:53 As he.
07:33:53 When we will move to the club. So, we will change a little bit 16 but it will be a roughly the same. So we'll create a micro service with the best deck yeah into Asia, where we ever should be on it so we are also use your micro services are running today.
07:34:13 And with some credential, of course, and we will post will do a post on the script Sally's zc former, a job, into MCA.
07:34:26 Let's see.
07:34:30 Zc micro service will push foot will format as event you know that we're compatible eventually the rest into the right empty to peak, and then everything will be as before, instead of that instead of retrieving the could of course from gateway would we
07:34:47 choose to come from, from get lab it but this is really simple, in the way we have walked.
07:34:53 Grab it, but this is really simple, in the way we have walked. And when it's finished.
07:34:56 And those are the costs that we use we sent us a specific entity to pick like the one for the eight, and will create using the API messages into the club match request.
07:35:12 So, this is something that I have started to work on. I don't see any big issue. To do that, I'm sure it will be available,
07:35:25 it's less about that we have is a release process. So again, an OEM.
07:35:29 less about that we have is a release process. So again, on Om. We are a bit different than the other one.
07:35:33 In particular, if we will get. So in any is DMC and so on. zR main release our doctor for Docker containers. and as your face.
07:35:44 For us, each, and packages.
07:35:46 And so we have two jobs to do that one which is to do that at any time we are merging into master.
07:35:52 And we really push, or, or n packages into a neck, and to own up. Next use into a story that is named staging of something I don't remember but into a specific date.
07:36:06 And when we want these, they're showing up for not just something that is great new we have that.
07:36:15 Jessica walked out to to to make it happen. So, I will use it for Russian stumbled up sorry, another woman is for example.
07:36:25 It's to use it, please release a specific comment into a guarantee of you. So the last one.
07:36:32 When you want to create your release, and then the push into the final and repository or from that mixtures.
07:36:42 Zhu Zhu, and packages so that means that everybody would be able to use them instead of having to make them. So this is something that is great news that has been walked with Jessica, and so shotgun is working well i i i'm pretty sure there's 001, or
07:36:58 are true and we've decided that very soon.
07:37:02 And so, we will have, of course, again a different behavior on get lab but we again can do the same thing.
07:37:08 So so first couldn't be done.
07:37:30 Omni unprotected branches. As a staging pusher to push through the staging and an exercise. So, protected when she's our master branch and all the stable branches.
07:37:30 He stumbled on Hulu and one in one and the second will be done. When we are on the deck. So that means that,
07:37:48 that means that every time a tag is create either on GitHub GitHub with a specific ci ci pipeline and escape a plane we will average that we push
07:37:56 that we will have created. into into the finance and.
07:38:01 So, of course, we have some prerequisite for that is, for credentials. So, in next year's, I don't really know next year sofa or an appeaser either administered better underneath am administering the inside orange.
07:38:18 I usually create a specific user that does.
07:38:42 Zero right Bruce to a specific story, and. And so, yeah.
07:38:30 What we would like to have is to have one or two.
07:38:36 Producers at one for the staging one for the finance we can protect. So different variables in that would be allowed to push to the side, and it was.
07:38:45 Once we have that, that brochure work as already being done by myself as a city insider arranger specific here.
07:38:59 Let's see ci so this is something that can be done very.
07:39:04 So now, a bit of code map.
07:39:08 So, maybe I'm wrong but they thought that he stumbled say enough was November 14 but maybe it's November for those that doesn't change anything.
07:39:19 To see November for if it's November for.
07:39:24 And I apologize, it's November for one week from today. Yeah, yeah, yeah, I'm very bad at it as you can, as you know, and so.
07:39:36 So, you see for you shouldn't see 14, but for.
07:39:40 I would send an email into an opportunity to say that, for me, people will move to get lab. One week or two weeks as you wish.
07:39:48 So that she's gonna Yes.
07:39:53 And, and joins the screech.
07:39:56 What we'll do is research will be to, to make a fake women repository into one of our own people.
07:40:12 Ongoing that we have and we will verify that everything is working as expected. We will also start to walk on the future, or at least on the event, hit me that MD, and especially an hour to contribute that because it's a bit different at what we are doing
07:40:30 engaged. So, with some screenshots and stuff like that to explain what out to do out to make a contribution into Om.
07:40:39 And when everything is ready so a week later, we will move to get that the Om. So when I'm seeing moved to actually already into the data and great but.
07:40:55 Step.
07:41:04 a leader I would say offers what it was doing. And we've stopped from there. Of course, there will be some Eclipse at stuff now as Jordan, and we will do our best to with our free stuff to make this as good as possible, as soon as possible.
07:41:19 So that's what they either.
07:41:22 I don't know that any questions, comments.
07:41:28 Quick question, Tony Finnerty here.
07:41:39 So, to eat.
07:41:45 I could do, maybe what I can do is a quick demo of because it's a big world maybe but as you know we are.
07:41:55 As you may know, we are also have some
07:42:00 and share the screen and share the magic quiz that we have today
07:42:09 on orange open shorts
07:42:15 took your, I guess and reaching the right one.
07:42:20 So, wherever it is.
07:42:33 So let me three main screen, I have, I have last year, sorry Anthony be faster than that.
07:42:37 Yeah.
07:42:52 So she's just she's a or a way to instead you're going to test using the fk to and that's just for the example and I'm not pushing anybody to use it. So you can see yas to match requires that we are, we've got this point of time.
07:42:58 We've got at this point of time.
07:43:02 So,
07:43:05 here you will see that I can see the changes.
07:43:09 So the main difference is that in Garrett, so I can show up during the night, and Garrett, sorry, change, so you can compound.
07:43:20 So you will see five by five if you want it.
07:43:25 You can change that to your configuration, but I prefer to have each one face to face to face so it's quite easy to, to show it to seed but sometimes we got to find it.
07:43:38 it's better than having all of them here.
07:43:39 And so in Garrett if I take one of mine, myself and also so I know she's at that.
07:43:48 Both of them are from me so a
07:43:51 joke, you will see that, yeah I can have roughly the same. So, this is the geek lab way, and Garrett way. I can make. If I want to make a comment, and Garrett I do my comment in geek lab it's for free the same I can make a comment, so many friends that
07:44:12 I think is quite interesting for for people is that you can, and especially for
07:44:19 commuters.
07:44:20 Most of the time when I'm doing a review. I'm saying you shouldn't do this, this way, but I cannot really, so the person has to understand or to put the best what I'm saying, Yeah, you can set it to Jason.
07:44:33 Jason is very nice or let's say that at that 122 and 21. And when you start as a person, we see that and could and could apply the suggestion that once if it doesn't want to explain.
07:44:49 And, and, and then as you do your review. So, the difference is won't be won't be a very big two main parties that year. It's pure Mac down year, it's a pseudo Mac down, I guess.
07:45:10 So sometimes it's a bit, we had a two seat. The second thing I, I like is that you have, of course on this one we don't have but you have the number of schedule, and he's ur.
07:45:32 a good idea for all, everything has been resolved or not. And so you can see different stages. So, here on Lisa we are very faint, and Sybil Indiana and here we are creating a Docker file.
07:45:44 And here we are launching our gates, you see.
07:45:47 I'm a funder of gate, even on our project so we've got these gate systems that are running, so that instead of five India.
07:45:59 In a job very famous one.
07:46:02 Yeah, for example because I have some failure I know you look at, year, year, I can see directly but, again, as this is very small different season.
07:46:13 Everything is as a committee I think that that's really roughly the same.
07:46:21 Did I answer your question.
07:46:25 Did yes thank you could think of any other Christian comments or maybe I'm a bit late, so you need to kick me off for now, because, again, as I said, I can look good okay so on.
07:46:43 This was just a question so is there any plan on the outstanding Jared patches, do you have a sort of a two, make them part of a separate most up to date lab or is that something you'd expect the contributors to over them.
07:46:56 So, if I understand where your question is that, as a vj knows well, maybe not everybody knows, we've got a lot of patches.
07:47:08 So you can see here we see, I think it's up we've got only one patch page. That's very good. It's better than before.
07:47:19 But if you look at, we have it no from Mab, we have 30 pitch that are not met yet for yet for several reasons. Most of them, I would say at least from ear to ear will be match interests.
07:47:42 I, I say that, I don't know, that's a good question, actually, what would be the best way that I guess that the best way would be for us with our crystals to match, as most desperate during this week window.
07:48:08 window so we can clean as late as most as possible. And for the ones that are still there and we we we have a Steeler and stuff from people, because I found this by now usually that's that that's that.
07:48:22 Those are ones that so he's not there anymore.
07:48:24 Yeah, maybe they are now, do me any more into an insurance of. There are very old patches.
07:48:31 But for the other one.
07:48:33 Maybe if not diligently asks a person to move it to get lab with alpha if it's possible that would be possible. Again, I, my goal would be to ever as.
07:48:48 So, least possible number of patches where we do that, but I guess we will have a few of them, especially mine because I'm a very slow guy so I've got a very old batches and that should be that I'm working on so of course I will move.
07:49:02 That does it answer your, your question. Yeah, I think, maybe you might want to enforce some sort of free spirit or lock the ripple sooner before at least a week before you start the process that way.
07:49:15 Your new patches coming in and then they work through the current outstanding ones first. Yeah, that would be a, that's a good proposition I see, yeah.
07:49:30 I will not get into the slides before us and everybody's agreed.
07:49:33 The other question I had to learn in terms of the jet lag ca jobs right and the current process for Jared we have to see a job to manage and DCA management reports on this new setup, how will be, how would that be managed.
07:49:48 Is it something left field managers something although empty will manage or.
07:49:52 So, for om for sure that will be orange team that we manage. So this is the chairman Fila, like this one.
07:50:02 Again, as this one is close to what we will see, I guess, agenda on Om. And you see that it's not very I, again, it's a main thing and when is that, as I said, we are not ending the same package artifact than the other projects.
07:50:15 And that's why, usually, Jessica, a talk a lot for us to do, because we are so different than the other ones and and we know with the free stuff out to do when they're dead so this is something that we will we will do by yourself without any acid.
07:50:42 But after you so I was up projects want to move. I think that I think that the LSAT is walking on the gang of. Same thing as Jenkins within the club, I'm not sure so maybe adjust your banker, going into on that, before I, for one, for sure, that we do,
07:51:01 and committees that we let the responsible for the CFA.
07:51:07 comedians that we love the responsible for the CFA. But this is going to be in a separate repository on chat lab maintained by No no, it's a, it's just a finer.
07:51:15 Oh, okay, the same.
07:51:15 Okay so fat, enjoy repository. So that's something I like also to us because you can also do some gating on your side.
07:51:26 It's kind of done. Today we say management.
07:51:30 Chain Management will verify that your ci failure walks is a valid j phi, but it's complicated, at least for me to validate is that as the steps that you have put, which is that either on your unseen management is actually doing what you want.
07:51:51 That's where I struggled a lot into a Jenkins ear, as its premier match request that will use it as you see a fader, you can see very first he said it's exactly as you
07:52:13 wondering.
07:52:13 QUESTION So om is the only repo that is moving to get lab, because GitHub is solving some pipeline requirement that you have with it mean that for all the other projects are still remains and will remains on on Garrett, is it, and any comment on this.
07:52:34 So, I have no comment on everything outside of for me. I think it's really.
07:52:42 Yeah, it's more this more coming from an om requirements to to move this one too. Yeah, right.
07:52:52 So what, what I will say, in that context for now is that in the past we have had various communities that have tried to maintain over the long term, a split type of repository management.
07:53:12 It has always been a massive problem. So the goal here would be that if this proves out as a very positive thing for om that the entire community would then be migrated over.
07:53:32 We can't have a, you know, as a pilot it's it's it's fine having two different models.
07:53:38 But over the long term we need to have one that the entire community is is leveraging whether it's Garrett, or GitHub or get lab that matters not as long as everybody is using the same time so from a pilot perspective, perspective.
07:53:57 We're good, but the TSP would need to then decide which direction that the community is going to go.
07:54:18 And a quick comment on that.
07:54:09 Just a lot of people are using om to a lot of people I know I seen the least and done. So any tissue and so on.
07:54:30 We've, we will have not done any, I would say om commit a new user you.us back but also feedback for a lot of
07:54:45 us. I would say for our users or users that are walking on a lot of different peoples and.
07:54:51 And I'm pretty sure that all of them will have a
07:55:08 closing costs to to to ensure it won't be and the guys that will say yes it was cooler, or not it was a it was bad. But really, if you if you look at the diversity of people pushing changes.
07:55:13 It's a, it's a lot of people because most of most of the changes that our vision burns of stuff like that that are done by by pts or, or this out, as I said put our user off of a competent.
07:55:33 Yeah, and also yeah I can add and this what you were saying that. Yeah, we also are using the club so for for a process perspective, Garrett and get lab are are very similar after that it's just a matter of difference from the look and feel the, the tool
07:55:52 itself but it's quite from a process perspective it's quite similar you know big differences there.
07:56:05 I have a question a couple questions from our reviewers point of view. This is Tony Hansen.
07:56:12 Yeah, go ahead. Good. Tony sorry.
07:56:16 So, I'm make heavy use of the Garrett dashboard to tell me things that need reviewing some of the repos where I review things I'm committed ran and others I'm just reviewer and om being one of them for things that are related to the repos that I am a
07:56:42 competitor in.
07:56:44 And we'll their.
07:56:47 First off, we'll get lab.
07:56:51 Things will sing single sign on with my Linux Foundation ID, work with the get lab Om. And the second question is there any plans on having a unified dashboard that would show things, both in om world that need.
07:57:09 Get in the get lab world that need reviewing for om as well as things and Garrett.
07:57:19 So I guess he's more fit into on both of them but I said Kenny I think I need to put two types I won't be any dashboard first. And, and, and as it would be a decision to move to one or two key to to move to geek out to stay on Garrett, I guess, again,
07:57:39 that dashboard is not needed. At the end of the pilot for single sign on from LA fit.
07:57:50 I have no clue. To be honest, I am already a geek that user so I did use my geek lab user account, so I can then show you in that instance.
07:58:07 So I know that there is this is Kenny I know that there's been some work.
07:58:13 Looking at the get lab integration into the.
07:58:24 lf suite of tools. The single sign on being one aspect of that.
07:58:27 I do not know off the top of my head. What's the status of that is.
07:58:33 I'm not sure if anyone from REL Inge knows, but if not we can reach out to.
07:58:40 Trevor Branwell who's been working on that kind of stuff.
07:58:46 Yeah, I think he will be probably the best person to give us an idea where that work is, I can reach out to him.
07:58:55 Okay, if you could do that just I'd appreciate it. Thank you. Yeah, sure.
07:59:09 The other thing that I wanted to mention is that the easy CLA hooks into get lab.
07:59:18 That is work that is are currently trying to debug because what we've been experiencing.
07:59:30 Is that get lab is taking somewhere in the neighborhood of about 40 seconds to detect if a projects covered by the CLA or not.
07:59:42 So, that is ongoing work there obviously there's nothing that we could release into production, until that kind of performance issue is, is addressed.
07:59:53 But that's one of the snags that they've run into.
07:59:58 And why do we care about the time.
08:00:02 I mean, is there anyone who's going to march patches foster them 40 seconds.
08:00:10 I don't think it's a snow that's that's on their name.
08:00:15 Yeah that's on that commit.
08:00:17 I think it's, it's the setup. It's making me like it's part of the setup let me associate get lab repos with easy CLA.
08:00:28 Oh, so maybe that's my misunderstanding then I thought it was the commit check was taking 40 seconds.
08:00:37 No, I, I could be mistaken too but my understanding was that it's part of the setup.
08:00:45 You actually participated in project with the dev team, where they were looking for volunteers to, you know, walk through the process and they give them feedback and so I did that, and they warned me about the you know the 42nd delay, but basically they
08:01:04 they consider it, and an acceptable performance issue and so there.
08:01:11 That dev team is coordinating with get lab they they believe that it's a bug and get lab and so they're trying to get that resolved.
08:01:24 Okay so, yeah, that was my misunderstanding if it's if it's like for setting up and associating the repos different story.
08:01:35 Yeah. In general I thought that the process work well. There's a lot of clicks and and information that needs to be entered so you know I told them that they need to provide you know good documentation with screenshots and everything, because it does.
08:01:53 There are a lot of steps, but it seems to work well.
08:02:01 So I know that we, we are good.
08:02:05 I was just gonna say. The other issue, which we were talking about yesterday his insights.
08:02:13 So, you I talked about that Kenny.
08:02:23 No, I was the next thing I was going to bring up so yeah go. Why don't you go ahead.
08:02:24 Um. The other aspect of this is insight support.
08:02:29 That is work that is kicking off, separate from this so they are estimating insight support for get lab to be in the February 2022 timeframe.
08:02:54 The means that we can continue to learn from the old experience.
08:03:02 And then we need to have a plan of migration and probably do one project at a time to a vote issue, a little bit like we did when we migrate to sort of flow though we migrate to other stuff we were doing one project at a time.
08:03:23 Yeah, I can't see a scenario where we would do a big bang cut over.
08:03:30 I think the level of risk involved in that it needs to be.
08:03:36 It needs to be a, a migration as you stated.
08:03:51 And then, you know, once we get there, get everybody and then the old system would be would be quest and we'd be on the new one. Um, there is one thing I heard that, that I want to get clarification on.
08:03:58 And I heard that that a couple of basically privileged user accounts, need to be created that would have permission to do a lot of the activity.
08:04:13 How are those, you know I being being an old systems administrator anytime I hear somebody mentioned the use of a privilege to count.
08:04:25 It hurts my ears up.
08:04:28 So how would the access to that account be managed.
08:04:34 Or is that is that just information that we need to figure out after the pilot.
08:04:40 Um, so, I mean, you're probably talking about the information about credentials to accessing Nexus or anytime that stuff right.
08:04:51 I don't know, some other accounts. It was just, ya know, it was something that Sylvia mentioned.
08:04:59 Yes, so from this security standpoint, the Geek lab itself works on per user basis. So, everyone has its own account. And then you just assign a particular rights to particular sub spaces or particular Rico's, so that's not at all everyone's going to
08:05:21 work on their own account, and that's it. And there is no sharing involved here. And the other thing that is there is that need to integrate the job that will be running on Nita with the infrastructure that we already have, like for example Nexus, or
08:05:42 we need to have credentials to accede to access Gary, just to be able to you know enforce the CLA stuff, as I've been showcasing a few weeks ago. So for that, you will need, we would need credentials for some account.
08:05:59 And that would be not the credentials that are used by some particular person but that would be credentials that that will be used by our jobs that they're running.
08:06:09 And I believe that it's actually pretty much the same as we have currently with Jenkins right have a job that is pushing artifacts right and it needs those credentials.
08:06:19 So there is a service account Nexus or whatever infrastructure ad job is using, and then basically the jobs gets the credentials.
08:06:29 Okay, cool.
08:06:39 So this is, this has been great information great presentation.
08:06:46 So, thank you so much for that.
08:06:51 Sorry. Yes. In addition, I gave them the permission to be maintained or not an owner of the puzzle. Good luck.
08:07:01 Got it. Thank you.
08:07:05 Um, if there are no other questions, then I think we should shift over to requirements subcommittee read out.
08:07:14 Who will be sharing that will it be Allah, or Timo.
08:07:18 Hey, I'll be sharing. Okay.
08:07:28 Can you see my screen.
08:07:32 Okay. Yeah, we are looking at your email right now.
08:07:37 I'm not good. Now you see what you're supposed.
08:07:42 Yeah, so basically you know what we did during the past year is basically the review requirements so each release.
08:07:54 Prior to release submission and approved, you know requirements to be introduced into the release and then you know, we made sure that also the relevant JIRA tickets are created and you know in some cases you know whenever asked the kind of you know approach
08:08:13 to gain the participants, you know, with the tasks, basically, you know, asking them to complete the text before each relevant milestones so that in large.
08:08:25 What we did during the year.
08:08:30 And the reason I'm showing this.
08:08:35 You know, this with page, and we've discussed this this team as well, is that we see. Recently, especially for Jakarta and this significant decrease of requirements submission the relatively, to the point of time via we stand right now, you know, an old
08:08:57 Jakarta timelines right i mean we had significantly more requirements submission let's say two releases back, and even for the symbol release, we had significantly more.
08:09:13 Now I've been calling for the new requirements submission for several weeks so far we've had on the one meeting with two presentations, basically you can see them here in the water show on obscene effort, orchestration was even not just presented I guess
08:09:34 it will be presented chocolate but the rest of our presented during the past meetings.
08:09:39 They already you know the scope is being included here on the big page and you know those. Hopefully we will proceed into Jakarta release but this is really what we wanted to highlight during this meeting is indeed you know that one day for you have a
08:10:11 were supported to Jakarta so first of all you know again, use this opportunity of the tea significant can call to community issue the call to community guys, this is the time to bring them. But also, you know, have a brainstorming here of what if, in
08:10:15 what can be done.
08:10:30 discussion.
08:10:30 So, do you think it could be also due to the fact that the team is trying to finalize it some more. And there no they they have not yet had the needy.
08:10:48 To hide some specific, because I know we know.
08:11:03 I think that we faced exactly the same issue for all of the races try that, you know, same teams developed requirements and about always overbooked. These the existing release especially at close to release completion right so that has always been the
08:11:10 case, this is not something unique to what the situation that we are facing right now, is a stumble so this is why I'm highlighting that especially.
08:11:22 I don't think that ever prevented people from bringing a new requirements, especially since you know from the requirements subcommittee perspective, and there are not many things, which needs to be done for submission and approval requirements which is
08:11:39 still pending architectures have committed subcommittee review and so on right but, you know, a more detailed requirements basically needs to be discussed it sort of saw I saw honestly I don't think thats related to the pressure and put the overload,
08:11:56 which currently exists because you know again, that has always been the case.
08:12:01 Okay. Did you also, I noticed that they are several Allah PUC, which were implemented in the context of Istanbul. Did you also follow up with the PLC order to see there is anything that they would like to official lies, as part of the Jacka DVDs.
08:12:27 And also I used to the call basically as I typically did for all of the releases to all of the requirements have committee members several times, asking again to submit requirements and the source also basically what happened in the previous releases,
08:12:45 those pieces, which were intended to become requirements for the following the release you know the otter super brain given the requirements, you know, for the new release.
08:13:11 So, that was business as usual buki NPK you want to talk to him on if he wants to it something to watch I said, no nothing really to that.
08:13:25 Okay, guys, We have a usual network slicing use case. Five
08:13:48 at total, even from Dyson, and that's really, you know, one of the key, and there was so many, you know submissions or discussions for all previous releases related to that.
08:13:48 Not yet, have not gotten a single request to present any slice and requirement for Carter this all all that was submitted, you can see on the screen.
08:14:06 Slicing is not there yet. So I hope that will be alone, we are not yet closing up the release but nothing has been proposed yet and again you know, we're talking about people who are aware of the procedure, right.
08:14:22 So, in case of slides in quite a few key people change year in the last release but still you know, even those who lead the use case right now that ever of how the process works.
08:14:37 We also have about, looks like a requirements from the stem bowl that reduced scope.
08:14:46 During the release cycle, and I, and I assume many of those will be continuing those requirements into Jakarta.
08:14:57 Well, they have to be submitted for for that.
08:15:01 But is it possible to be poor active and maybe with your subcommittee, you reach out of these people to understand they're in debt.
08:15:18 A while we can reach approximately, you know, one by one, right, that can be done of course, as I said, I don't think that's the issue because I feel that people are aware of what needs to be done but of course you know.
08:15:25 And this is something that we can do and, you know, they'll do.
08:15:32 Yes.
08:15:31 If I may ask a question so why you believed NT requirements been previously reviewed and approved that they have to be resubmitted based on what we, I mean, based on what we discussed when we've been introducing the process.
08:15:48 If something is approved, then it basically can be implemented. It doesn't matter if the team and then just to implement that within a single release or they need a little bit more.
08:15:59 Right.
08:16:03 Right. The one The point is that we cannot make a conclusion silently that you know that will be continued that requirements will be continued and there are resources allocated by the company for their next release right so at least on the level of commitment
08:16:23 that has to be reassured right I'm not even talking about the technical scope, which was, as you say, already you know submitted and agreed, but, you know, it is not necessarily the case that there will be resources allocated for requirements in the next
08:16:46 release right. Okay cool so I'm practically, the only thing that you are waking from the requirements owner is to just confirm that that they will be continuing their requirements for these requirements, which postponed.
08:17:06 from the one of the releases Yes.
08:17:09 Yeah, there is some work there we have a process for that because we we agreed in order to have traceability and in order to maintain the history.
08:17:21 We agreed that if a requirement continues from one release to the next. Then we create a new JIRA for that.
08:17:31 That way we maintain a record of, you know, the work being in the previous release. And so there is some effort there, and I think what all is saying, it makes sense because it doesn't necessarily need to be reviewed again but we we do need to understand
08:17:50 their intent to continue into the next release some of them need to be in place in social situations in the past, right, that companies were committed for wanderlust not necessarily committed for this sequence one right i mean that's,
08:18:09 I think, I think I can help out here all so I will send an email to the owners of those eight requirements, asking them, you know, to make a decision and follow the process if they tend to end up all copy you and the requirements subcommittee list on
08:18:34 that, that email, so we can get the ball rolling there.
08:18:38 Okay, great.
08:18:40 Okay, so this is definitely something that probably have to be executed but, you know.
08:18:47 Okay.
08:19:11 maybe,
08:19:11 and your question for an anti GMO
08:19:16 or just have a combo Blitz Your sins are going because.
08:19:20 Yes, sure. Yeah.
08:19:23 Hi, just, just a comment for Alan chemo, at least from the sun use case perspective, I think, and I see the seven in the slicing use case, I think there is an effort to.
08:19:33 There is a draft of requirements and there's an effort to try to figure out what requirements makes sense and and what might be supported.
08:19:42 Instead of just saying, These are the requirements and we may or may not be able to support this I think that's I see that happening.
08:19:49 But I'll bring a list of requirements to the next and at least we can put them down in this format. And so, and I think, I don't. At this point I don't recall exactly when he made the presentation for the assembled release but in Jakarta I do see that
08:20:15 work, it's the same people doing requirements and thinking about what it's doing it's not two separate exercises, right. So, there was some, some overlap because of that.
08:20:19 And then, like you said, there are also some.
08:20:24 Maybe that changes in scenarios waiting one one discussion waiting for another discussion that kind of thing happening.
08:20:31 So, I don't I can't, I just want I don't recall exactly how different it was before. for example.
08:20:40 Okay, so basically what you're saying something for the use case. Yeah.
08:20:45 So, what you're saying you're saying that perhaps a more
08:20:51 careful process has been implemented right now than in the previous releases, not just to submit but actually you know proceed or Thursday, or whether it can also be implemented.
08:21:13 That's always, you know, the better think that they, the issue that might be is that you know we have timelines right and we've chatted for the information of Jakarta Banda so we don't have much time.
08:21:20 Right.
08:21:24 One is December 2 way.
08:21:35 So guys please broadcast.
08:21:39 If you would like to present your requirements during the next requirements of committee meeting in the half from now that's really suggest that you know, again, After that you'll have to go for architectural solutions subcommittee so there's still work
08:22:12 done right. A lot of work to be done. So those who intended listen to those submit requirements for Jakarta should be doing that for the next meeting, like David said there is carry over work also, which, in some sense, I don't see a big change in the
08:22:15 architecture discussion, but a lot of complexity on on what work is left and how will it get done and we'll, we'll have that discussion on the use case and the requirements.
08:22:27 Okay. Great. Thanks.
08:22:31 Okay, thank you.
08:22:42 Anything else
08:22:48 debo for at least giving our bonus but I think the list is not finalized, and we look, look for maybe in the next few weeks after we sign off, Istanbul, we might have some carry over to.
08:23:23 Thank you.
08:23:07 Thank you.
08:23:13 Jane.
08:23:17 This backup.
08:23:22 Couple things.
08:23:24 Chair elections kicked off yesterday.
08:23:29 The email message is right there. nominations and on November 10,
08:23:38 the life cycle, I'm Catherine you suggested that that'd be taken just to email for discussion.
08:23:50 When I was hoping to go through because I have some question myself, what has been written but I know we have only seven minutes.
08:24:00 So I'm not sure if it wasn't valued to kick off now.
08:24:04 Okay. Um, so, so, yeah, I will shift, how we continue to sleep maybe next week is not possible because of the sign of to see where we are.
08:24:20 And I will keep my topics for later. There is not really an urgency, but I just wanted to find is this part so I want to thank already, Amy, and also Thomas and Martian we've been providing some feedback, but it would be nice if the TC could also be used
08:24:41 us so I really insist that the TSP review because we will need to vote on that proposition. And I will try to formulate.
08:24:52 Some of the question I have myself when I was doing the last review. So, next day potentially will be the 18.
08:25:03 And I really would like to go line by line, because I have some question about bubbles some, some items.
08:25:12 Thank you.
08:25:17 Okay.
08:25:19 I've kicked off the vote for the Honolulu awards it's being done via Oprah vote.
08:25:25 This has been voted on by the TASC members.
08:25:30 Please, take a look. Make sure that you have received the vote, the ballot.
08:25:41 If you don't see it please check your spam folders.
08:25:48 The PDL call will be canceled. On Monday, this coming Monday. As a result of a holiday in a number of parts of the world.
08:26:01 Also we've got the TLC meeting that's going to be counseled on the 11th do too. I think that's Armistice Day, if I'm not mistaken.
08:26:14 And then holiday in the US on the 25th for the developer and testing forum.
08:26:21 The dates have been weeks now we've been saying it's the week of the 17th, that is not correct.
08:26:30 It is actually the week of the 10th, specifically the 10th through the 13th of 2022 not 2020 that would be rather difficult for us.
08:26:46 Anyways, so wanted to bring that to everyone's attention, also wanted to get finalize the language that's going to be used for own app.
08:27:00 Here is what it currently says, and if the community would like to change that. Or let's do it right now because this needs to get posted on the website registrations are currently open.
08:27:18 By the way, and I will drop that link in here.
08:27:22 After we get the text updated.
08:27:25 So currently reads on App community will be hosting meetings for alignment of architecture modeling security and other aspects of systems line. As we look forward to future releases of the platform.
08:27:38 Is this the current text, is this the text you guys want to keep, or do you want to change it. No, I think we were already working last week, any of you know delete the previous version and yep Give me one second here.
08:28:06 Well I had that tab open obviously I don't
08:28:11 know because we were speaking about it will also give an opportunity to share the latest demo.
08:28:20 And the result of the task force.
08:28:23 Yeah.
08:28:45 So if you take your modeling requirement.
08:28:49 The donor committee will also
08:29:05 always say, it would be also an opportunity to discover the latest.
08:29:10 Well, so if we incorporate these things into a logical sentence, do you guys just want me to do it, provided that these items get incorporated
08:29:37 Did you set you want to finalize here. Yeah, I, I, I do, I do want to finalize your possible.
08:29:56 Let's take this.
08:30:05 Do you want that we type in the chat.
08:30:13 We can, you can type it in the chat or see what I'm doing here.
08:30:24 And Task Force.
08:30:33 Task Force deliverables.
08:30:54 capabilities and
08:31:05 I'm sorry that you guys are putting up with my typing here, and other aspects of system design
08:31:15 spin up. Also, this will also
08:31:21 also be an opportunity, a demo and demonstrate the new functionality, or. Okay.
08:31:34 To demonstrate, new functionality, or to demonstrate the latest functionality.
08:31:50 They've looked in Istanbul or something like this.
08:32:09 And to discover the latest announcement.
08:32:16 And to discover the latest announcements
08:32:24 over
08:32:27 and do these quarterly this announcement.
08:32:31 I wanted to highlight some things related to production readiness to change so it is an announcement implemented enough to change or, you know, delete some announcement.
08:32:47 The blog by the integration team, and the other one.
08:32:56 I think it's like a bit of a complicated text and I think the main thing we want to attract people to join, but I'm not sure this text, really excites people so I can think of something I really need to drop off for another

[data-colorid=wmk3gs5udj]{color:#1d1c1d} html[data-color-mode=dark] [data-colorid=wmk3gs5udj]{color:#e3e2e3}[data-colorid=bqe5bx14y0]{color:#333333} html[data-color-mode=dark] [data-colorid=bqe5bx14y0]{color:#cccccc}BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Agenda Items

Release Status

RelEng/Infrastructure

PTL Updates

Subcommittee Updates

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

Task Force UpdatesCNF, Wiki 2.0, ONAP Enterprise

TSC Activities and Deadlines

Upcoming Events & Housekeeping

<Available Slot>

Zoom Chat Log

BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise

Browser not supported