BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09
Passcode: 209247
We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Attended | Proxy (w/ @name) | Gov. Holiday | Did Not Attend |
---|
Attendance is taken purely upon #info in Zoom Chat
Alla.Goldner proxy Mike Elliott | AMDOCS | IBM | ||
DT | China Mobile | |||
WindRiver | Turk Telecom | |||
AT&T | Reliance Jio | |||
Ericsson | Bell Canada | |||
TBD | Vodafone | Samsung | ||
China Telecom | Huawei | |||
Orange | Intel | |||
Verizon | Nokia |
Agenda Items | Presented By | Presos/Notes/Links/ |
---|---|---|
EMCO Updates | Bob Monkman (Deactivated) | A quick update - Work being done to better align EMCO is a way that will align with |
PTL UpdatesDoc, CLI, Portal, VID, ExtAPI | Thomas Kulik New Doc PTL CLI
Portal
|
VID, ExtAPI
Feedback from VID, ExtAPI PTLs
- No interest from the current committers to take over the PTL role
- Collect feedback from the Community & send final call ?
OOM
- Asking for a TSC approval for LFN Mentorship proposal: "Externalizing ONAP DBs to a separate namespace"
TCC / ONAP Liaison Update
Formal alignment between ONAP/ORAN SC about SMO
First feedback from O-RAN SC/ONAP TSC Chairs and LFN discussion
Next follow-up meeting with TSC Chairs/LFN later today
TSC Activities and Deadlines
TSC 2.0
- 4 reserved seats have been inactive most of the year. All have been inactive 6 weeks running
- 3 are no longer Platinum Members of LFN. Now all Silvers
- still count against quorum for meeting attendance and voting
- potential turn-over of TSC Members based on TSC focus going forward: Execution vs Strategy
Release Status
Istanbul
- SECCOM Request - Moving best practices (Packages Upgrades and CII Badging) to Global Requirements.
- Kick off (M0) today -
- Question: Honolulu GR/Best Practices applicable to Istanbul release by default?
- Istanbul Release Requirements
- TSC Vote - New Requirements frozen (excluding reqs from previous release)?
- Remainder of schedule is TBD
- ATTN Req Owners: Best Practice and Global Requirements must be reviewed and socialized with PTLs AND approved by TSC NLT M1.
Honolulu
- Status (Mar 31)
- UUI- https://gerrit.onap.org/r/c/oom/+/119844
- SO - Release the H release sol005 adapter (I79949521) · Gerrit Code Review (onap.org)
- RC0 Req Owners - 100%
- RC0 Projects - 99%
- RC1 Req Owners - 71%
- RC1 Projects - 60%
- OOM Gerrit Filter (Krzystztof)
RelEng/Infrastructure
- Tickets- Open showstoppers:
- Tickets- Waiting on Community:
- Migration Status / Upcoming Changes
- EasyCLA migration Kenny Paul
Subcommittee Updates
Arch, Ctrl-Loop, Lab, Modeling, Seccom, Requirements
LFN Cross-Organization Updates
MAC, SPC, TAC, EUAG, LFN Board
Committer Representative to the Governing Board
Task Force Update
CNF, Maintenance, ONAP Enterprise
Upcoming Events & Housekeeping
2021 Internships - Call for project proposals and mentors
- Proposal submissions due
- TSC sign off proposals
- Approved projects announced
Action Items
Zoom Chat Log
...
VID, ExtAPI Feedback from VID, ExtAPI PTLs
OOM
| ||||||||
TCC / ONAP Liaison Update |
| |||||||
TSC Activities and Deadlines | TSC 2.0
| |||||||
Release Status | Istanbul
Honolulu
| |||||||
RelEng/InfrastructureNOT COVERED |
| |||||||
Subcommittee UpdatesArch, Ctrl-Loop, Lab, Modeling, Seccom, Requirements NOT COVERED | Proposal for moving 2 best practices to Global Requirements:
| |||||||
LFN Cross-Organization UpdatesMAC, SPC, TAC, EUAG, LFN Board NOT COVERED | Committer Representative to the LFN Governing Board | |||||||
POC FindingsNOT COVERED | Control loop in Tosca | |||||||
Upcoming Events & Housekeeping | 2021 Internships - Call for project proposals and mentors
|
Zoom Chat Log
06:45:09 From Kenny PAUL (LFN) to Everyone : #topic rollcall
06:59:11 From Bob Monkman to Everyone : #Bob Monkman (Intel)
06:59:34 From Ranny HAIBY (Samsung) to Everyone : #info Ranny Haiby, Samsung
06:59:48 From Bob Monkman to Everyone : #info Bob Monkman (Intel)
06:59:51 From Ciaran Johnston (Ericsson) to Everyone : #info Ciaran Johnston, Ericsson
07:00:21 From Mike Elliott to Everyone : #info proxy Mike Elliott, Amdocs
07:01:06 From Dong Wang (China Telecom) to Everyone : #info Dong Wang, China Telecom
07:01:10 From Olivier Phenix (Bell Canada) to Everyone : #info Olivier Phenix, Bell Canada
07:01:15 From Jason Hunt to Everyone : #info Jason Hunt, IBM
07:01:20 From SaiSeshu MUDIGANTI (Huawei) to Everyone : #info Seshu, huawei
07:01:38 From Timo Perala (Nokia) to Everyone : #info Timo Perala, Nokia
07:01:39 From bin.yang@windriver.com to Everyone : #info Bin Yang, Wind River
07:02:52 From Fernando (Fred) Oliveira to Everyone : #info Fred Oliveira, Verizon
07:03:08 From Andreas GEISSLER (DT) to Everyone : #info Andreas Geissler, DT
07:03:13 From Eric Debeau to Everyone : #info Eric Debeau, Orange
07:03:23 From Srini Addepalli (Intel) to Everyone : #info Srini Addepalli, Intel
07:04:37 From Catherine Lefèvre (ONAP) to Everyone : #info, catherine lefèvre
07:05:03 From saleem abdul to Everyone : #info,saleem Abdul,LF
07:09:21 From Catherine Lefèvre (ONAP) to Everyone : Thank you Bob for the update !
07:12:16 From Catherine Lefèvre (ONAP) to Everyone : can you approve my phone
07:12:32 From Catherine Lefèvre (ONAP) to Everyone : ok i will reconnect
07:12:38 From Kenny PAUL (LFN) to Everyone : don't see it
07:13:37 From Catherine Lefèvre (ONAP) to Everyone : i have reconnected the audio
07:13:46 From Catherine Lefèvre (ONAP) to Everyone : can you see me?
07:13:57 From Jason Hunt to Everyone : yes
07:14:11 From Catherine Lefèvre (ONAP) to Everyone : i will make an attempt to speak :-)
07:14:29 From Jason Hunt to Everyone : we heard you
07:14:32 From David McBride to Everyone : I heard you
07:16:57 From Andreas GEISSLER (DT) to Everyone : +1
07:16:58 From Ciaran Johnston (Ericsson) to Everyone : Sounds reasonable
07:17:15 From Timo Perala (Nokia) to Everyone : +1
07:17:52 From SaiSeshu MUDIGANTI (Huawei) to Everyone : +1
07:29:54 From Kenny PAUL (LFN) to Everyone : #AGREED If no contributors step forward the Portal project shall be moved to unmaintained status
07:37:15 From Jason Hunt to Everyone : great idea - thanks for pulling together
07:37:23 From Eric Debeau to Everyone : #info I fully support this mentorship proposal
07:38:14 From Olivier Phenix (Bell Canada) to Everyone : Great proposal, +1
07:38:30 From Srini Addepalli (Intel) to Everyone : +1 on the proposal to have databases and infrastructure pieces outside of ONAP installation.
07:40:18 From Kenny PAUL (LFN) to Everyone : #AGREED the "Externalizing ONAP DBs to a separate namespace" LFN Mentorship proposal is approved
07:42:04 From Morgan Richomme to Everyone : related to previous discussion, a wiki page to collect the different UI offerent by ONAP, please complete the list, we will try to setup a healthcheck test that will just check that the GUI are available: https://lf-onap.atlassian.net/wiki/display/DW/Honolulu+UIs
07:59:56 From Jason Hunt to Everyone : my apologies as I have to lead a call now. On this topic, I’m in favor of the “strategic” view of the TSC member who takes on some additional role/task.
08:00:17 From David McBride to Everyone : Thanks, Jason
08:00:21 From Srini Addepalli (Intel) to Kenny PAUL (LFN)(Direct Message) : Sorry. Need to drop now for an internal meeting.
08:03:13 From SaiSeshu MUDIGANTI (Huawei) to Everyone : +1 on the thought
08:14:38 From Catherine Lefèvre (ONAP) to Everyone : https://lists.onap.org/g/onap-tsc/message/7135
08:15:42 From Catherine Lefèvre (ONAP) to Everyone : honolulu kick off was on October 10th
08:16:31 From Catherine Lefèvre (ONAP) to Everyone : then it took up to Dec 11th for M1
08:16:34 From Catherine Lefèvre (ONAP) to Everyone : 2 months :-)
08:17:01 From Catherine Lefèvre (ONAP) to Everyone : i am fine to have 2 months of back and forward if it is what the ONAP Community wants to do
08:17:31 From Catherine Lefèvre (ONAP) to Everyone : sorry 2.5 months :-)
08:18:15 From Catherine Lefèvre (ONAP) to Everyone : would like to avoid we squeeze dev/test while we take a lot of time to get req rights :-)
08:20:15 From Kenny PAUL (LFN) to Everyone : brb
08:21:56 From Catherine Lefèvre (ONAP) to Everyone : honolulu = 5 months already
08:22:21 From Catherine Lefèvre (ONAP) to Everyone : Guilin was implemented in less than 5 months
08:22:31 From Catherine Lefèvre (ONAP) to Everyone : if 2.5 months are spent between M0 & M1
08:22:44 From Catherine Lefèvre (ONAP) to Everyone : we will not be able to improve our release cadence
08:23:00 From Kenny PAUL (LFN) to Everyone : back. sorry.
08:24:11 From Lukasz RAJEWSKI (Orange) to Everyone : for new reqs maybe it is 5 months, for those that continue the work on thr req, new release starts after sign off of the previous one - so real work is definitely not 5 months.
08:24:51 From Catherine Lefèvre (ONAP) to Everyone : thanks lucas for the clarifications
08:30:02 From Lukasz RAJEWSKI (Orange) to Everyone : "Candidate requirement proposals will be frozen on TBD" https://lf-onap.atlassian.net/wiki/display/DW/Istanbul+Release+Requirements
08:30:07 From Lukasz RAJEWSKI (Orange) to Everyone : TBD should be concreto date
08:32:52 From Timo Perala (Nokia) to Everyone : +1 @Lukasz
08:34:17 From Catherine Lefèvre (ONAP) to Everyone : I need to leave
08:34:20 From Jim HAHN (AT&T) to Everyone : has RC2 officially slipped? Or is it still today?
08:34:38 From Catherine Lefèvre (ONAP) to Everyone : #Vote +1 for UUI Waiver
08:34:59 From Catherine Lefèvre (ONAP) to Everyone : Dear TSC - I have also added a note that we did not agree to freeze the scope of Istanbul
08:35:05 From SaiSeshu MUDIGANTI (Huawei) to Everyone : #vote +1
08:35:18 From Eric Debeau to Everyone : #vote +1
08:35:24 From Andreas GEISSLER (DT) to Everyone : #vote +1
08:35:24 From Catherine Lefèvre (ONAP) to Everyone : thank you and please continue to raise your voice if you disagree, we are here to continuously imporve ourselves
08:35:46 From Ranny HAIBY (Samsung) to Everyone : #vote +1
08:35:50 From Olivier Phenix (Bell Canada) to Everyone : #vote +1
08:35:50 From Ciaran Johnston (Ericsson) to Everyone : #vote +1
08:36:01 From Dong Wang (China Telecom) to Everyone : #vote +1
08:36:20 From Timo Perala (Nokia) to Everyone : #vote +1
08:36:54 From Kenny PAUL (LFN) to Everyone : #endvote
08:38:40 From Kenny PAUL (LFN) to Everyone : #AGREED the TSC approves a waiver for UUI https://gerrit.onap.org/r/c/oom/+/119844 to be included in Honolulu
08:46:43 From Krzysztof Opasiak to Everyone : I need to drop bye!
...
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:03:29 Through our normal
07:03:32 things here meetings being recorded. Everybody's muted when you come in please keep yourself muted, unless you are speaking, if you're on phone line you can use star six, and if you send me a private chat message in zoom it will become part of the meeting
07:03:46 record.
07:03:48 Andreas, Eric Sweeney Thank you
07:03:55 start a meeting, as always, by mentioning project Jenny cross policy. You can find this link from the left and the project websites. All of these important where we got multiple companies including potential industry competitors participating in meetings,
07:04:18 Please review if you have any questions, please contact companies legal counsel.
07:04:11 Remember the lF may also contact Andrew of growth from get their approval LLP, which provides legal counsel to the Linux Foundation.
07:04:23 With that, I will stop my share.
07:04:30 So agenda, we're going to do.
07:04:34 Bob's gonna provide a quick update on em Co.
07:04:38 Got some ppl issues to work through.
07:04:43 Talk about only happen around alignment and TLC to Dotto. We'll talk about the release.
07:04:53 Couple of things on infrastructure subcommittee updates. Wow, build up overnight.
07:05:02 And then, just some housekeeping issues, anything else anyone needs to add.
07:05:11 Can you just want to ask.
07:05:11 Nicholas send out a request for five minutes.
07:05:15 It is that ok to have it today or.
07:05:25 I sorry I didn't see that.
07:05:29 She sent out in Monday for a presentation for control looping Tosca.
07:05:32 Okay, we'll see if we can do that.
07:05:35 Okay.
07:05:36 Thanks.
07:05:39 Catherine. Thanks, I will.
07:05:44 Oh, I didn't ever share mine when I'm looking at here I'm sorry, kids here, your agenda screen.
07:05:53 Okay. Bob I'll just turn it over to you. Yep. Very good, thank you for the time frame for getting an open for me.
07:06:02 Good, good afternoon, Good morning, folks.
07:06:05 Bob Hoffman here from Intel.
07:06:08 On February 18 training you know I had a presentation on em CO and there was a robust discussion about the needs of the own app community, and I just wanted to give you.
07:06:22 It's been a while five weeks or so since, since that meeting. I want to just to make sure that everyone knew that training I and others and Intel are working on this we're taking the request, very seriously, we are, we talked through a number of options
07:06:38 and one option that was requested was.
07:06:42 It would be just more ideal for the own app community and other communities if if m co were hosted in an open governance environment so we're taking that very seriously.
07:06:53 We do not have a decision yet but since it's been a long time I just wanted to come back to you and let you know that training and I and our management are exploring all the options and looking at this very seriously and we might we might have a decision
07:07:11 for two weeks for the 15th TLC meeting, I don't know if we'll get there or not but we're getting pretty close. And so, just wanted to let you know that we are we are working on that and seeing if there's a way for us to accommodate the, the own app community
07:07:28 so I'll leave it there is any questions or comments and.
07:07:35 Is there anything that this forum can do to help you reach the optimal decision like do you need the formal voice of the TC or something to share with your management or are you good and up front.
07:07:47 I think I think the only thing I would say is, any stakeholders who have any particular input they'd like to share with screening if you have our email addresses, send us a direct message.
07:08:04 But I think we have enough input I mean a good. We've had offline and in other discussions we've talked about this for a while we have the input from the, the February 18 meeting.
07:08:16 But if there's any other things you'd like to share, or one on ones you'd like to have just reach out to us on email, Bob. McMahon at Intel. com.
07:08:26 Copy training and we'll, you know, we'll we'll, we'll have another conversation if we need to, but.
07:08:35 Right. Great.
07:08:37 Thank you.
07:08:40 Thank you, Catherine and Kenny for the open to come on and give that up there I thought it was important that we start doesn't languish and folks didn't think that we were had forgotten about you, we had not you know that's good Bob Thank you so much.
07:08:56 Really appreciate very much jump to my other meeting. Okay.
07:09:02 Well I'm stuttering I'll say goodbye.
07:09:05 Thank you. Thanks.
07:09:11 Okay, um,
07:09:15 I guess I can share my screen.
07:09:24 Before,
07:09:24 there is there, but
07:09:30 ok see things on the ppl front.
07:09:39 Tomas quick
07:09:42 PGLO the docs project so congratulations and welcome
07:09:49 is kinda garage on all
07:09:56 know there was about to give him supercollider privileges that past so I'll ping him to open up the ticket, and then
07:10:09 reference the email
07:10:15 on the portal project.
07:10:21 We had a decision to initiate a portal election, because the ATL is
07:10:32 out with, with personal issues and may not be back anytime soon.
07:10:39 But the PTO was basically the only competitor on the project.
07:10:45 There are a couple of folks that we can promote eventually if they are interested.
07:10:54 Let me
07:11:00 just pop over here.
07:11:09 Shouldn't have that up beforehand. I'm sorry.
07:11:13 Um, so this is looking at the past six months, only we can extend it longer but there are a few
07:11:23 folks on here that that could potentially
07:11:31 be,
07:11:34 could potentially be promoted.
07:11:38 Any thoughts from the TLC.
07:11:57 Okay. The other thing that we had discussed
07:12:04 on this was that
07:12:10 some folks chimed in saying that they weren't using it.
07:12:15 From the TLC.
07:12:16 It is a component of what.
07:12:20 Iran is
07:12:23 Katherine don't see you.
07:12:50 She's not in the waiting room I'm not sure. I see her on the very bottom of the list.
07:12:57 Yeah, she's on the bottom of the list because she's in with video only and know.
07:13:05 Yeah, the phone and come through earlier so I don't know I approved it must have gotten disconnected.
07:13:13 She said she's great to reconnect.
07:13:20 Carry on this particular issue that is the proposal that you would have the TASC.
07:13:25 What about change your procedure hair so that you would open up the, the Patreon election to contributors as well as competitors or is there some other procedure you're proposing that we execute.
07:13:40 It could be, it could be one where the ESC intervenes to initiate the election which is, is what was approved here.
07:13:55 Normally, that would the election would be conducted from the pool of existing competitors.
07:14:04 Since we don't have any existing competitors.
07:14:07 We would need to both promote.
07:14:14 And then,
07:14:14 you know, from that actually a point of ppl.
07:14:22 So, It would be it would be different.
07:14:26 It would be a PSC intervention, basically, to make sure that that things are moving forward, which is the, it isn't in the context of what the PSC can do.
07:14:41 That's wanted to add something if you can hear me. So, just a reminder I send the TLC final, final call for the fourth time, more than two weeks ago, I guess.
07:14:58 We didn't get a response. So the final item would be to contact as you said Kenny the individuals who could be eligible based on what you shared previously with the LSE inside that that's something we can do.
07:15:14 But we cannot force people to step up for sure so that that's what I would suggest as a next step, except if anybody to see members you have another suggestion, before we move this project to maintain.
07:15:36 And based on previous feedback from someone that was on that committee members.
07:15:43 The not really using Boston, they are using the API to build their own interface, their own UI on top of it.
07:15:53 But I just want to notify that I believe this poster might be used for this thing.
07:16:00 So any additional so beyond what Kenny has presented suggested that VZO.
07:16:17 As the final call the eligible eligible people.
07:16:26 There is no objection I would say okay let's contact.
07:16:35 The people you were sharing with us.
07:16:36 To see Venus in any interest.
07:16:38 If there is any dress item to say we move books that under, and maintain status.
07:16:47 We in alignment.
07:16:49 I'm just asked again.
07:16:58 What I'm gonna do is I'm going to mark that as an agreed that if we, if, if no one steps up as a if don't want to express an interest that the project will be who unmaintained.
07:17:18 Yes, just to make sure that I understand that correctly, import or export all these move to maintain state, it means that will disable for our health.
07:17:30 Right.
07:17:36 Can you repeat the question. Yep, so we stopped the, if it is moved to our maintain state, it means that will stop deploying it by default, right so we will disable it in our home charts
07:17:51 are correct.
07:17:53 We follow what was defined in the step.
07:17:57 So some of the steps will be either you continue to use it because it's needed for the think of balls and you use the latest container.
07:18:08 If it is not needed for testing, then yes you can remove from the enter in depending on the case where we are.
07:18:16 Okay. Thank you.
07:18:18 Yeah.
07:18:22 I know it's crystal, the as the CPT.
07:18:24 And just want to highlight that.
07:18:26 As DC relies on dr for the y axis.
07:18:30 So if you disable it you won't be able to use as DC one.
07:18:35 Yes, that's right.
07:18:37 I think you will not be able to do to remove it from the distribution of the installation and.
07:18:47 That's sad.
07:18:52 That was the Gestapo, which is some, oh no man because pasta was really in any capacity capitulated SBCUY policy UI and all those uy, so it was the scope policy, remove the UI sometimes ago.
07:19:11 As we see still need to rely on the UI to facilitate the onboarding of the results. So, before, if we have to wait to information.
07:19:27 So I give
07:19:33 you the very last component.
07:19:36 Using a several that raises Cassandra might add.
07:19:41 And today is, I guess, used to access may need some UI, like is here.
07:19:49 Visa and so on.
07:19:51 We used to inside arranger developers, tiny Prasanna, that we know that today's episode, which we're actually doing only as a guarantee of success with the same level of security which he then proceeded to a VC of Eden.
07:20:13 So, because he he simply so with the quota.
07:20:29 Hello visa and needed a cookie, and that they could hear it. And you know, cookie, your right to hide, hide value which is actually the same thing in different.
07:20:32 So this is something that we could meet with a very very simple component.
07:20:38 I thought that there were some proposal to to to propose this component.
07:20:44 If, if nobody, nobody wants to cooperate this kind of component idea that the arrangement, open, or a proctor which is actually, I don't know, hundreds later fighter now so super super thin, and he do raises a war for basic access to to to an app as a
07:21:06 demo of course for for the your work.
07:21:11 You will need your own possibility say, it could be something that we could do.
07:21:18 If anyone is interested in.
07:21:21 Yes, I think the same. We are doing and our portal so using in the header or to eat some cookie stuff.
07:21:30 I think that it's a good idea at the moment to have. What, what, what I suggest is.
07:21:38 So a kind of, let's say, small or lean component and later check whether we have done some enhanced portal in the pipeline. As I already said so maybe we will also table we also thinking of, let's say up streaming the work but it's it's too early at the
07:21:58 moment for doing that.
07:22:01 So I would also suggest it to do with sevens suggestion.
07:22:08 Yeah, I'm also supporting that direction.
07:22:16 To be clear,
07:22:16 so the work has been done by one of my colleague emphasises Smith my maker budget.
07:22:36 I'm pretty sure it will be.
07:22:36 That sounds good.
07:22:33 Thank you.
07:22:38 Okay, so right now I'm just that we want to remove a box to other one with that works, but notice that you just a secret Barbara, no matter what the folks who maybe after.
07:22:59 No matter what the work so maybe after. If you want to keep it a little bit we need to have some some some testing and so on. But today, it's really 100 lines of code that I turn into
07:23:13 job.
07:23:16 Drop your kids see agree, I guess that you can consider because developer weather, isn't it, we get, we can do that for sure but, again, between it maybe meet with quality requirements that are not ask for a demo for desta and and segregate.
07:23:40 Yes, it was some some some basic butter with Europe internally, but we need to check to a tree to test it again with maybe a new roof, to see if it's still walking on Yes we can, of course, we can
07:23:59 stream it on the baby share with maybe with the community when it when it's ready I'm going to be too.
07:24:11 I personally believe that, even if it doesn't currently meet the standards for best coverage or anything that we have in all now.
07:24:29 Still, it would be easier to work on 100 lines of Python and make it meet those quality requirements rather try to queue older the Romulans that the leafing cocking sharing both Oracle's source code.
07:24:38 Okay.
07:24:41 I'm taking this approach to to to to look at it, I will do some tests on a daily deployments.
07:24:46 And I hope to publish something next week if you want to do extremely well.
07:24:55 Yes, I think what would be important because if it had to be marked as a distinct tool so people should not stop to open issues because of security because of the great package, because of non compliant with a non compliant with the best fatigue.
07:25:36 think in terms of communication would not include in the architecture, somehow, but all to mention clearly it's a testing tools.
07:25:29 Yeah, I think we need to discuss that to where we put a good answer on this.
07:25:36 But let's let's check that is working fine assets around maybe we can do it.
07:25:44 I'm sure what what it is on after we can decide where to put it on.
07:25:50 That sounds good. I think we can go to crack we can make a final goal with the computer, you don't divide by Kenny.
07:25:57 So it gives you more runway to see if we can ever knock down.
07:26:03 Okay.
07:26:11 propose propose a tourism native year round we already have something called you.
07:26:12 Again, I'm not favoring anything as.
07:26:15 I'm not against any of those two proposals I'm just saying, Can you also check us one of the alternatives which we already have as a compliment on that.
07:26:27 I think that it's an opportunity if we step down from the time to reassess if I do have CDs, either uuy can take it over this old. But again, we didn't get any feedback on this previous position.
07:26:44 But that was something I liked it again either one of two weeks, probably two weeks ago.
07:26:51 So, week, I would suggest to look at all the alternatives and to let community and finally TASC to to consider all the options with, again, what you have suggested situ was also phase, but nobody stepped up to you to take the opportunity to consolidate
07:27:12 all the UI together.
07:27:15 Regarding the UI, same so Morgan speaking. Recent main to the mailing list. I think two weeks ago. It was a discussion integration with try to a reference to collect all the UI on that people are using.
07:27:30 Because there are lots of UI in an app in order to make a simple UI check your test and as part of the check to be sure that the UI that are in the documentation known on that the endpoint that tested.
07:27:45 So I, I took some point yesterday to create a wiki page to just reference this endpoint so that's something we used to do in our open another.
07:27:57 But as you can see that there are lots of UI. And when we, when we in the CI or in any tests, we do not simply checks that are all answering. So it will be a simple very basic test, showing that but first we need to to collect two different UI that people
07:28:15 can use either for the use case, or as admin or when they are using an app, and to be sure that we are not forgetting them. So, if I will create a wiki page.
07:28:29 Been integration integration project but I will send the link for the wiki page to complete an area invite you to reference the UI you are using daily with your own app in order to be sure.
07:28:52 Well,
07:28:51 Thank you again sorry we have missed your email will retry and maybe to add it to do this minutes.
07:29:10 So why can you tucking the feedback from Morgan. We have a similar situation where to ppl notifying the community to step down that they will sit down.
07:29:25 Catherine just on the surface interruption Yeah, I'm sure. Do we have. Do we have a formal agreement from the TSP for what I have highlighted if no company.
07:29:30 No contributors step forward, the portal project should be moved to maintain status.
07:29:36 And I pound agree that.
07:29:41 Okay, I will thank you. Go ahead.
07:29:45 Sorry Kenny. So we have a similar situation to other object where the, the PTS don't. And also, the ppl election and nobody step up.
07:30:00 So I don't know if there is any images reaction that we can collect from this goal, or the license story.
07:30:11 I will send final goal on own up to see and discuss to bring awareness and we will need to take a decision about these two projects that move unless the committee, who is attending the meeting today.
07:30:28 See already some concern regarding VIP and external API.
07:30:41 Yeah, good. Good thing I would check again internally in around if we can
07:30:49 find someone.
07:30:52 Okay, so let me be.
07:30:56 So, thank you for clicking. What I suggest I will send the final call give two weeks.
07:31:03 Notice, and then we can hear sets in two weeks which means we can have this on the 15th of the TLC level,
07:31:15 give time to the upcoming EP, and we send the mail on up to cn discuss, I hope I did it with postcard can remember, with all the to this call is to reach a maximum of people in zero interest,
07:31:34 any concern from the TSP about the next step.
07:31:38 I think it's human enough causes that you apply on any project that we were the PTS the dome.
07:31:50 For the moment I just hope that none of the MVP will be impacted.
07:31:55 And then I will give you the flow I think it's two crystals.
07:32:07 And then I will give you the flow I think it's to Christos with submitted a month of ship proposal. We can also take a look at the page, I think, to know, Christoph on behalf of the om team has submitted, only one proposition.
07:32:14 I don't think there is all the one Kenny.
07:32:17 I should do that we have a look so Christoph Would you like to go through your proposition.
07:32:24 Sure.
07:32:25 So, basically, the goal of this proposal is to have someone that could work on externalize databases that we have as presented during class, we're def.
07:32:38 We have a large number of databases that are often embedded into our components and that are hard to be replaced that they're hurt to be maintained our heart to be back up and all that kind of stuff.
07:32:52 So what we would like to do and what has been presented as a high level vision to om was to be able to complete our deployment into multiple name spaces that couldn't be provided.
07:33:05 Using our testing tools or that could be provided by the end user.
07:33:10 So, in other words, we will allow to use not only the databases that we have embedded into our map, but any database deployment methods that our user prefers so if you have dedicated database in junior school just provide you with a URL username and password.
07:33:32 That's fine, you simply put that in our config files and we are good to go. We will use that database. If you want to use Kubernetes operator, we are also fine with that device in the URL service name username password, we will use that.
07:33:48 If you are just testing on the app and you want a single click deployment, then okay can deploy all those databases for you. But basically, walked on up to be more flexible and allow user to choose which components may use shirt databases which components,
07:34:07 shouldn't use databases and substrates. And this is not only for databases, but we view databases as a first step, and then we'll move to the other components which are listed here as platform, and use cases.
07:34:23 So, the work, isn't that complicated. From the technical point of view it obviously requires some knowledge of how on Kubernetes on writing column charts, etc.
07:34:36 But it's definitely tedious so it requires a lot of time to be completed. So, we believe that the eatin. None of us unfortunately have the time to complete that.
07:34:51 So we believe that we should be able to achieve this.
07:34:55 With the help of internet that could benefit from that.
07:35:12 Creating a real piece of software that will be later used by don't fear.
07:35:12 See SPC indoor.
07:35:10 That will be probably, we don't have any preferences or regarding our regarding working dollars, whether it's full dive halftime.
07:35:21 It doesn't matter that the best we can get.
07:35:25 We are flexible here.
07:35:29 So that's probably, I'm sure, If you have any questions.
07:35:36 Kenny, so the the work here is going to be.
07:35:44 So the work here is going to be self contained basically within this high level vision.
07:35:50 Yep. So it's self contained is going to catch Om.
07:36:05 Maybe a little impact on components if they have some database names hard coded in their containers, things like that but no major impact on the components themselves.
07:36:09 And also, the word is kind of good because no matter how fast it goes or how bad it goes.
07:36:17 You may always stop so if an inter manages to externalise all the databases, that's super awesome. We are really happy and that's a huge success. If you managed to externalize one or two databases, that's still better than nothing.
07:36:37 Right, so whatever he he or she manages to do. That's a huge help for us in a huge step forward.
07:36:43 Okay, thanks.
07:36:52 Any questions or input from the TSP.
07:37:00 I think it sounds like a good idea to have flexibility and the types of sort of back end persistence that we use or the way that I can persistence is deployed I think it's a really good idea so that's a, That's a good proposal.
07:37:15 Chris up do you do you document somewhere in there.
07:37:21 Because you mentioned a number of levels of completion, I think it would be good to document what the what the minimum expected outcome is so if the minimum expected outcome is to externalize the least one database.
07:37:37 That would be good to document.
07:37:41 I believe it's already documented here, the outcome second section.
07:37:46 So we expect the installer yet with at least one database. Okay, All right, I see what you mean. Okay, thank you. That's the plan of minimum but I hope that interval managed to do more than that.
07:38:02 Right. Got it. Thank you.
07:38:06 Okay, I'm seeing and hearing support for this.
07:38:10 Yes, yes, I think it's a.
07:38:13 We all know that the team is not very need some Arab so it's very good to have such kind of proposer to to add on team.
07:38:26 And we want to thank for the team because we know it's also an investment from all the slides to ensure that the interns will understand what it is expected to work.
07:38:41 Thank you for your position.
07:38:46 I think we did a great, that's a great example of what I was talking about the other day.
07:38:51 As far as the benefit of the intern program, because here, you know, the om team has this project that they've had sitting on the back burner. They know what needs to be done, but they don't have the resources to get it done so they bring in and turn
07:39:06 turn, and they're able to move forward so really encourage other projects and pts to consider that that example and what sorts of similar projects, you might be able to contribute.
07:39:23 Okay, so I'm going to mark this as a greed.
07:39:29 And we think the opportunity to remind people, you can still submit any proposition until the fifth.
07:39:37 So, If you didn't do it at the end of the minutes of the agenda and you will find the link, and the process to submit your proposition.
07:39:49 Thank you.
07:39:53 So, can you just a stupid question because I am doing that for the first time, right so 3ds in up.
07:40:00 So how does the process for from this moment looks like I mean, do I need some kind of PSC voting or that I should now go to the wiki page and change the change the status of the proposal or you will do it or Katrina will do it.
07:40:15 How does it look like
07:40:20 you would go to where it's there.
07:40:27 So, I will go and mark this as as approved, but okay so.
07:40:35 Okay, cool. And then someone from the Linux Foundation will contact me about that right. Yep.
07:40:41 Okay, cool. Thank you.
07:40:49 Okay, So yeah, that, that looks like a
07:40:55 mean pretty much a textbook example of where this program will provide benefits to, to the elf so thank you so much for doing that.
07:41:11 Okay, shifting to discussion of RFC.
07:41:30 My whole dress I was a new, so just wanted to give you a feedback, as you know, we receive a lot of positive feedback from the community.
07:41:41 Swami Mustaine and john was presenting a great presentation last week demonstrating how we can reinforce the relationship between the own up and the organ is see, especially about the service management orchestrator.
07:41:57 And it's been was facilitating of girls meeting last week with the organ is teacher, and vice chair. Here we go, positive feedback, the organ is CT is a chair and vice chair, we're suggesting that additional follow up.
07:42:17 We'd be equal with the requirements subcommittee.
07:42:23 In order to finalize these agreements, because it's the requirements subcommittee for Mohandas see who is defining the symbol for us to move forward. And we have another meeting today.
07:42:38 After this call, I guess, to continue the discussion have a whole weekend, a spot on the TMC facilitate this formal agreement, even if we have the members Pomona up, and also for mono Annecy the requirement the architecture subcommittee working together
07:42:58 to really ensure that the sum of all enough components that can make the difference. Not only today, but also in the future so more to come. But as I said it was not opposed back it was really welcome the discussion, and I will continue to keep you updated
07:43:17 based on what I'm learning and discussing with the my counterpart, from the
07:43:36 Sikh community.
07:43:38 Any questions, comments, thoughts.
07:43:42 Thanks a lot for years.
07:43:46 Yeah.
07:43:50 Yeah, what what is your foot two and when we set for my for my alignment between an app on his Mo.
07:43:58 What does it mean
07:44:01 for the moment, because there is no I don't know if the OC is consuming a set of component from Leona community.
07:44:14 So it means they didn't need to develop anything to support.
07:44:20 They have known non time
07:44:23 functionalities, which is supported by the service management of case crater.
07:44:30 Having a former agreement will be that they will not look to any identities, and they will continue to consume own up from a downstream perspective to build a service management orchestrator.
07:44:43 So it means that if they are so fast he will start to monetize on up.
07:44:49 They don't need to build own up to serve network automation functionality for the customer and and propose another solution for the same customer for all hands.
07:45:00 So they will be one set of components that they can monetize points by that's really the objective to help active own active members to monetize not only in the context of owner, but also if their key partner in the context of organization to monetize
07:45:20 toys.
07:45:21 So, again, I'm still discussing at eye level but at one point and we need additional support from architecture committee and I Kauffman, including Swami Muscatine and and and john who did this presentation to look at the next level of detail.
07:45:42 Is it clear.
07:45:45 Jessica Thank you.
07:45:53 Maybe as we're internal discussion is. I think that would be great is to try to, to develop an end to end use case based on on.
07:46:01 You can reach out for maybe let's start with begins. If you can think about it could be greater so to demonstrate that we have a free alignment between both projects.
07:46:13 Yes, and I think that's what for me Maxine and Joe have been doing in the past, who the requirements that they are dealing with about a one interface, a one policy, and so on.
07:46:29 So, it's not something we discussed today I think they were, they were already some good at production their calls.
07:46:49 Cool organized by swampy in the EMAS time zone and somehow affect time zone and then makin also organized in the afternoon he EMEA and us time zone, just to bring the awareness and also suggest this type of collaboration ship, but I believe if we can
07:46:59 ever form an agreement between the two open source community that will help anybody we've already started this journey. I mean, the alignment between on Etsy, and own up.
07:47:15 I would also suggest that he visible, it will be really helpful to have some kind of automated test for that collaboration between owner, and Cora in the game, just to be sure that at the point where we are releasing all now, or on community can instantly
07:47:32 consume it without any issues.
07:47:38 Yes, we think that would be possible for discussion. But for the moment I'm really trying that the two DNC chair, and co chair in alignment to make it happen.
07:47:51 And when it comes. So we use my audio Okay, so we already gives you here.
07:47:59 cc SDK from, which was published last week.
07:48:04 Some kind of test automation already happens but of course, the whole intent is to bring this more closely together so that everybody is aware of what the other one is doing.
07:48:24 Okay. Any additional feedback.
07:48:29 Thank you very much for your efforts especially
07:48:36 you know feedback I would like to suggest that we move on the TASC to the old topics we were putting on all for a couple of weeks but I really believe we need to take a decision for the following reason I think we, we may have been some suggestion on
07:48:56 the owner Casey meaningless to define also the scope of the TC is not about the priority of the DSC but it's really to determine if the next generation of KFC would like more focus on the execution of this party, because I understand that they are some
07:49:18 TLC members who is more comfortable in the study space than the execution.
07:49:26 And depending on what we do, we might have the new one, or the replacement of some TLC members, and at the same time.
07:49:36 que Hundley.
07:49:36 We are 18, but concretely only 14 as participating, or trying to contribute on the vote.
07:49:52 The opposition, which was made a couple of weeks ago was also to split the whole.
07:49:58 And I have to say over the past year as we we noticed the transformation of the DNC members being more active.
07:50:06 I will not give a lot of details but you will recognize them some of them are leading a subcommittee they have PTSD or helping for the event.
07:50:16 The also helping on strategic initiative from the execution, like the testing.
07:50:24 But we have still a couple of PC, we doing their best, but not contributing that merge. And I think if we continue to split the world between us, we can become more efficient, instead of only relying on 50% of the KFC undercoat right on the good.
07:50:48 So,
07:50:48 first of all the question.
07:50:51 Should we bring you the TSP, because there are four slots, somehow, a news are not really active and and what we want to do, because if you are fine with a given situation.
07:51:06 It's okay.
07:51:08 Yes and no.
07:51:09 You see what I mean. But I think we need to move and decide what we want to do, because maybe the other company we've been active since more than a year they didn't have a chance to be at the table, and they would like to replace these potential inactive
07:51:26 slots on how can you would you like to add anything to what I've just described.
07:51:33 Yeah, it's important to know that for the, for inactive TASC seats right now.
07:51:45 They are all reserved seats.
07:51:49 Three of the members of those reserve seats are
07:51:58 basically over prefer.
07:52:03 If you look at the contributions of all three of those companies over the lifespan of own app. There have been a total of 99 zero
07:52:18 commits.
07:52:22 So, considering that that we've got almost 100,000 commits in own app right now that's not saying much in terms of up screaming, all the companies are doing are doing something with oh now.
07:52:38 But in terms of upstream contributions.
07:52:41 It's been very very minimal and there hasn't been anything since.
07:52:49 I want to say mid last year there haven't been any contributions from those three.
07:52:54 The other company is very active in the community.
07:52:58 Like the SEC is currently
07:53:04 has been occupied.
07:53:10 Those all four of those seats.
07:53:13 As per the community document.
07:53:25 So, that could potentially cause issues.
07:53:31 Also it's worth noting that the original thing around the reserved seats was for Platinum carriers.
07:53:45 And of those, the three of them that are basically inactive in the community, are no longer Platinum members of LFN. So, based upon that.
07:54:10 I need a proposal from the TASC in terms of what it should look like.
07:54:18 If, if how we've got it set up right now is okay with everybody. Um, that's fine we just take it and we start the. We start the election process.
07:54:38 So, we need to your feedback because we have made the phone proposition we never get any, any concrete action plan.
07:54:49 So I guess we reach the point where we need to move into action.
07:54:59 So I think the discussion but perhaps it isn't I mean, do we have specific charter changes or community document changes that we're recommending here that we would then vote on and are those written down somewhere.
07:55:13 No, I mean we're trying to do that.
07:55:19 Jason, I'm sorry.
07:55:21 The.
07:55:24 Originally, that was the approach that I started trying to take.
07:55:29 And there was significant pushback on that approach.
07:55:33 So, the discussion of what is the role of someone on the TLC to start there and see if that needs to be further lashed out is the expectation that somebody on the PFC should be serving on as the lead of a
07:55:58 as as a ptl, or as a lead on a subcommittee or workgroup.
07:56:09 Something like that.
07:56:09 In order to help ensure participation.
07:56:15 Okay, but I mean are we going to document that are we going to require that I mean, it's great to say we don't we don't enforce it somehow it's not going to happen right yeah that that's the question it would need whatever we do would need to be codified
07:56:31 into the community document.
07:56:35 And I was learning documented as a proposition.
07:56:39 But we never get really feedback so that's why.
07:56:43 At one point, we have different option, only stay as we are. Right. And we continue for another year of with to change what we are, and given opportunity to other companies, if they want to be part of the TCN define them from a particular hole so it's
07:57:07 not only.
07:57:09 not only PTA, it's not only focusing on on the execution it's really to look at. There's so much work to do. I mean, we have the staff for the board family of the task force we have this DC we have the Marc Benioff so many functions to cover, and having
07:57:26 a representation of the stack and so having only one of two people trying to play all the whole.
07:57:33 It's the same because if we can bring the whole we can be more efficient and more focused and tackle other great things together, so that was really the request to whoever know Tony, super from the TC for whoop, but also to play a war, considering that
07:57:56 all of us probably Yeah, we have to drop, we have our own job and we will company job and we tried to combine that.
07:58:07 So, we had a, we had a, an email thread about a while ago and there were some ideas expressed just like nobody has reacted. We just need to take those responses and maybe update the original proposal something you're making it sound like nobody's interested
07:58:25 interested in responding which is not the case, I think, well I specifically what you're referring to Randy is, is, I had sent out a couple of messages, specifically around.
07:58:42 What, what should the role of a PSC member be.
07:58:54 There was no response to those.
07:58:49 The previous responses that you're talking about.
07:58:53 Were, we're in my original what I originally proposed, and there was a great deal of pushback on that. So yes, there were absolutely responses to that and opinions expressed, which is why I did help move the conversation forward.
07:59:14 After talking to Catherine.
07:59:17 The, we came to the conclusion that maybe we need to first talk about what the role of a taxi member is rather than what the, the, the composition looked like specifically
07:59:33 fine so get to be pragmatic, can we start with maybe, maybe this email thing people overlook the need got lost in their inbox. Can we start somehow this conversation about the role of the DC member, maybe create the wiki page and have everybody had their
07:59:54 input.
07:59:56 And certainly, I can certainly create a wiki page. Absolutely.
08:00:01 And
08:00:04 we can,
08:00:07 we can go from there.
08:00:12 I can express my personal opinion that I would like to see.
08:00:19 Members of the TLC.
08:00:21 One of the expectations be that they are providing support to one of the work groups, one of the, one of the subcommittee's support in the community as a ptl
08:00:37 something of that nature so that's, that's my personal perspective.
08:00:42 And that's what all lead off with.
08:00:46 Yeah I personally have some thoughts about it but yeah let's have this discussion over some wiki with concrete proposition and counter prepositions instead of just going around around in circles.
08:00:58 Okay.
08:00:59 And to be sure that nothing is lost Kenny and I realized that maybe I was look clear myself on and you clarify to Honey, let's try to consolidate the key items that we have discussed so far what was collected using the previous discussion at the TSP delivered,
08:01:20 email, so people can ever be fresh as a starting point, it does not mean they they need to follow what has been written, but we consolidate everything on the wiki, since we kick over the QC to the discussion.
08:01:37 And then we will be locked up for Bobby a wiki euro done the email change, especially when the mailbox really explode. So, good suggestion.
08:01:48 Thank you.
08:01:52 And your digital. Yes, it may be just, just a question or or just to make sure that we all understand the same thing in your, in your view.
08:02:08 Kenny and anyone who's who's in favor of having PSC members taking on some, some leadership roles in one of the work workforces or committees, or would you feel that that that person elected on the THC.
08:02:19 Is it like in order to be elected on the TASC, you have to already be a leader of one of those things, or once you're elected, you sort of commit to getting involved in in one of the committee's because there are two very different things I think they
08:02:35 two very different things you're right you're absolutely correct. And it my ex. My personal perspective is that would be the ladder. If you're signing up to be a DSC member, you're committing to support the community, in some other passion, as, as a leader
08:02:53 of a work group okay or something like that.
08:02:57 Yep. Okay, thank you for clarifying makes a lot of sense. Thank you.
08:03:04 Well, for an example, I mean we've had the same dedicated folks committing to the events, sharing our, the content for our events, right.
08:03:17 So, those folks that probably like a break so it would be great to see other PFC members.
08:03:24 Step into that role but that's just one example.
08:03:33 Everybody could not do only even, that would be great. We have other boards to fill up by the way.
08:03:38 Okay.
08:03:39 If there is no additional comments.
08:03:42 We consider what has been discussed here.
08:03:53 And I suggest we have 30 minutes.
08:03:57 I will go extremely quick on the stone board.
08:04:02 So, as you know, today it was the kickoff.
08:04:05 We have several hundred people with submitted new equipment. We anticipate that put on 30 some honorably corpsman we will not be ready. My fifth, so it will be still open for the equipment owner who has been working on an interview to resubmit additional
08:04:27 use case spec features, based on, we are focusing on room, but in terms of new requirement.
08:04:38 I think that we should close, what we have received the ED sequence, the requirements have been a review and some comments have been posted.
08:04:50 So, it would be good if the report on the owner of stuff to others the different questions that was posed in the ticket itself.
08:05:08 And then, we had some question where we were not totally sure of all the questions concerning the global requirement and the best practice which was applicable to only do.
08:05:16 Does it mean that by default. We also need to consider them for Istanbul, I believe the answer is yes, but I just wanted to double check the statement.
08:05:27 Your answer is perfectly correct.
08:05:30 Okay, so at least, we will start to move. I think the GR already moved to the beach.
08:05:37 We will start to also add the best practice as well. And then if there are people who are suggesting new best practice.
08:05:46 I believe they need to start to talk to the beat of the ppl code to get familiar with that and get feedback from the CTS, and then they will come back to the KFC to make them
08:06:05 OPI Shan as what right. It is correct.
08:06:09 Yep.
08:06:24 Correct.
08:06:12 Okay, so I think we have the answer to your question we just wanted to validate. So we have a quick question for the TC.
08:06:23 Can you take a look at the new currency equivalent so when I say new, this is not.
08:06:31 I mean it is not depending on the annuities, people have already submitted.
08:06:36 And we would like to freeze the new requirement, when we will still welcome continuity or from requirement which will be the scope forum on early. Is it possible to have a vote today or do you would like to review them offline and we kick off an offline
08:06:54 road with the final decision by a period of seven.
08:07:18 Hold the DSC would like to proceed with the the coupon requirements and maybe we can click on the tombola requirement. Link, so they can have attained there is no use case submitted for Istanbul.
08:07:16 They are potentially feature and spec submitted, for example, at this stage,
08:07:27 Jeff is now coming here, this is funny.
08:07:30 We had the review with the requirements subcommittee earlier this week for at least a couple of use cases. And for one of the use cases because of lack of time.
08:07:43 It was shifted to the next requirements subcommittee meeting with Catherine, but I think the GDS have not yet been created, I think it will be created over this weekend.
08:07:54 So, but I believe that the three use cases that we had in Honolulu, that we will be continuing with.
08:08:02 I won't say big enhancements, but nevertheless some enhancements to all the three use cases.
08:08:10 If it is a continuity of old news, you can still submit, but it's really a new requirement that we see for the first time. Right.
08:08:24 As I was reading the scope.
08:08:27 And if the TLC want to ever look.
08:08:31 They can, but I would like to have a final agreement or final agreement.
08:08:38 By April seven. So at least we know where we are and we are not kicking off the rest of the milestone, we just want to be sure that formal requirements perspective, or the initial checks, which are ensuring we have company committed to develop to test
08:08:57 automation test right, we have enough information. The Epic allocated for each component so when the PDL will be available they can look at it as well.
08:09:09 We want to be sure that you have a Home Depot, you have a meeting set up with the requirements and the architecture, even if it is not yet
08:09:23 met right you need to schedule, even if you don't have finalize it so does the type of things we really want to be sure everything is set up properly to avoid we waste time later, to keep you on the road to have the information that critical for product
08:09:40 team to make their decision.
08:09:42 So I would suggest we will kick off a gypsy road because maybe some of the DNC members may not have a chance to look at it.
08:09:53 We will do with an offline vote to ensure that. Yeah, we haven't highlighted, Catherine is what I have highlighted.
08:10:05 Correct, yes.
08:10:18 Yes. Okay.
08:10:11 Okay. On to suggest something else. Again, it's a purple edition of the stage we propose new requirement, but it does not exclude any requirement from previous really.
08:10:22 Okay. In the test he wants to change the way how we should proceed. If they are welcome it again it's a proposition because we want to move forward.
08:10:34 Any of these enough feedback.
08:10:38 Katrina.
08:10:38 Hey, I kind of lost, I must say.
08:10:44 So, based on the release gatherings that we have a freeze for the requirements should be way later, and not now, when we are at m zero we are basically starting collecting requirements, and that's it.
08:10:59 We are not freezing that global requirements should be frozen at anyone, but requirements for the projects I mean together with review and proposed API changes, those should be free, and to us for us I remember
08:11:25 And because they are missing a lot of information we have a lot of back and forth and he takes two weeks.
08:11:36 So,
08:11:36 I want to say is very complex was on perform integration team working very hard to find your life.
08:11:45 It's not for the PTS to review it's really for the new requirement owner. If they want to submit something.
08:11:53 So, when you understand this. Ok, ok, ok, ok, ok,
08:11:59 I still not not really aligned with.
08:12:03 I think because we are kicking off the release and immediately we are voting on freezing the scope for that release that, that's kind of unfair in my opinion.
08:12:19 Yeah.
08:12:19 I think I need to support crystal here I think what the, what we have written and what we see now and zoom is quite clear.
08:12:27 If this is not what we are asking from the, from the teams that are actually submitting the requirements or specifications.
08:12:39 Features then it's it's it's difficult to to kind of guide them to do the right thing.
08:12:47 I saw that last time I need to look at the mail because when we say kickoff we were hoping to have an understanding about what it is submitted.
08:12:57 So, well I need to look at the notes.
08:13:07 Well, I think what matters really much is that this page needs to be true, because people will go and check what is here on the milestones. And if this is not correct, then we need to correct it.
08:13:21 Like yesterday.
08:13:25 Yeah, I was already checked what we did from the previous previous to be consistent.
08:13:32 Ya know, so this is being updated for changes that we have discussed for, for example. So for example for Honolulu we did not have an end for.
08:13:50 So, so this is kind of in process right now but the the tasks that you see are the same tasks that were deployed, you know, for the projects and requirement owners for Honolulu
08:14:12 So David, I think that there is some mistake because the approval for an impact of the use cases features expects that that's empty.
08:14:24 So for based on the presentation that we've been going through.
08:14:29 In the previous release, there was only a reminder for requirements owner to make sure that they are working on that. But the deadline to get approval from videos, etc that that was me.
08:14:44 Sorry, which which row are you referring to.
08:14:50 So, Yeah.
08:14:53 And the first adult. Get in the requirements owner tasks, get approval and identify impact of use cases features spec, or best practices Christophe I have a small comment on this, I'm already with us.
08:15:07 Yes, hello.
08:15:08 Yeah, thanks. The one problem is that we cannot start all the process. Later on, because by the experience. I agree to Catherine in this that my experience what we have seen is there'll be a lot of going back and forth with respect to the new requirements
08:15:21 which are proposed for a new release.
08:15:23 So one thing is we have to start early maybe the violation of the requirement can be taken at them zero time frame that is fine but it is we should have a paycheck on all the requirements for a given release, otherwise we will be in a situation surely
08:15:37 where we will be jeopardizing complete time of the details, the requirement owners as well as it is.
08:15:42 So I strongly believe that we should have a project. And I think that is a good way to actually start off, or kick off the alarm, because most of us are also doing other.
08:15:54 I mean, we have our own jobs apart from one app so it might happen that we will not be able to have the complete understanding of what has to be done for a given time frame.
08:16:03 So this check can can be there to ensure that we are all understanding on the same page and we have a pre check to ensure that things will be fine on the requirement on the release date on a specific date when we actually fix.
08:16:14 So there is nothing wrong in actually having the date, and that will actually going to help us to make sure that we are well prepared for the coming weeks at least that's what I can think of them to keep everything in the last moment and it will be a
08:16:25 big problem to be with that we have reduced reduced time from six months to three months right now. So we cannot go back and forth on this
08:16:34 date.
08:16:35 Give some comments so but from the other hand if we have, let's say, feature fees to. So of course this is the role of the requirement owner to, let's say, go through the requirements of committee architecture subcommittee to discuss with the PTS and
08:16:49 if the equipment owner will not, not to eat on Titan.
08:16:55 No, it's like, what we are trying to say what we're trying to say here is we don't require the initial list but using all the features will be available right now as you see, we are in firefighting mode some of the projects which are actually dealing
08:17:12 And the requirement will go for another release right, so why to make some initial list of them wait before, I don't know.
08:17:17 with current releases, we may not be having time to discuss all the requirements.
08:17:22 Okay, in that case what will happen, we can at least go with both beetles who are ready to talk, maybe those speakers who are not can be taken data down to put everything on the last moment and then it will not be able to, we will not be able to accommodate
08:17:34 everyone right.
08:17:35 But this is a huge project.
08:17:38 And this is not a problem of the PDF is not, it is not a problem for me I'm not just talking from a legal perspective right Amazon from requirement perspective because as a holistic solution.
08:17:46 We have to think of how our equipment can be gone through with all the inspect instructions which had to be taken again, wherever possible whenever possible, because there are a lot of isn't bias which we see on the process, and like what we had last
08:17:59 time right i mean with Judas Priest of you and me a good friend, so don't make me wrong, but empty was not understood inside me and Sylvia, both of us were very close to you and also never understood at MTC code freeze Actually, I've been you know that
08:18:13 that this was a surprise for me too and even Sylvan also faces issue. So, such surprise are there for us, with respect the process which is good standing and all.
08:18:21 So why should I keep it a last one.
08:18:23 Yes and no. Because if the requirement will impact seven components is sure that requirement ongoing needs to start all the process much to deliver that yeah exactly discuss on time but why to make a pressure on other requirement owners which will impact
08:18:36 maybe one or two components to also do it certainly advance. If you're personalizing on one side you're thinking about the comment owner but other side, the PTO also will be crushed developers will be crushed, because we have to see on the resources required,
08:18:50 the resources required, maybe you go with one estimation that is ok you will find it initially will only fire competence at getting impacted by it can be three can be seven, right, we know that we actually review it on all on all the subcommittee's on
08:19:02 on all the technical experts which has to be deals with just the computers and the architecture subcommittee, the requirements have been to all these things.
08:19:11 So we have to start somewhere. Earlier I haven't seen them to keep it at last moment because I'm sure with the kind of project we are dealing with.
08:19:17 It will be my second last moment if you want to take it everything just before Mr. Andrew.
08:19:23 I mean, in the past, what you say about this issue is still the requirement for the rights. So, if there is a need of something different. It means that the process again needs to be changed, right.
08:19:35 I'm seeing the electoral process be changed if that is what we want to do that the possibly change but we required to actually not keep everything and last woman.
08:19:41 See we never made the target and let's be sure we have given seven releases. How many times have we actually met target on time for every one for every one I mean, all the projects.
08:19:52 Okay, so we should have a project where we at least.
08:20:08 If there is some clarification to be given we can give that if there is someone whom we can discuss at that stage we can still start a discussion so that it actually triggers something.
08:20:12 So, what's wrong in starting that it's not pressures and someone it's actually using the someone's work and that's where I can see off.
08:20:20 So sensory family, make a comment regarding meeting your deadlines, so we're constantly not meeting the deadline because we are trying to keep the software that is not the red and the very basic principle that we've been trying to apply to a new release
08:20:41 process is that we are shipping the software up the software, only that nothing is ready right and if some if some feature or anything is not ready We are not trying to sheep, and the same is for their requirements themselves right so even through the
08:20:54 And the same is for the requirements themselves right so even through the timeframe to submit your requirements and to get them approved is pretty long, all the requirements are independent from each other.
08:21:06 If there is a higher priority and the higher pressure from the company, a on the requirements number, 123, then they will suddenly def jewelry talk with PTO, you'll year, start implementing that earlier and then they will have longer time for for the
08:21:22 development. If someone comes up with the, with a good idea for a small feature and he comes up with that leg, but feature is small enough that managed to go for all subcommittees and with BTS within two weeks, and still implement that in another two
08:21:38 weeks, that that that's also perfectly fine right but trying to you know trying to now push everyone to 70 day requirements before and one, which should be like, two, three weeks from now, that is going to be a real stretch for everyone, both from for
08:21:57 subcommittees for pts for the community.
08:22:00 That would be pretty significant. I would say amount of work to to happen.
08:22:08 Customer not saying it would respect I will not trying to say that we don't require to change the complete deadline of a man to be changed to treat three weeks before what I'm saying is, we still have quite a paycheck, we don't require to check everything
08:22:19 on on the date of Emma, we can actually have a pre check, just to ensure we all are on the same page. If, if someone can move ahead as you said some requirements may be very easy to do some become some very complex, some requirements can be, you know,
08:22:33 span across multiple competence and requirements might be single component. So they have multiple combinations English requirements will be so to keep it generic term like what we are trying to do right now also right we are actually comparing a project
08:22:44 which is just 20 k 30 gallons of cosmetic project which is 300 gallons of code. It's not easy for 300 cancel lines of code to deliver a release within the span of two months maybe a clinical and can be done.
08:22:56 I mean I'm not comparing. I mean I'm not seeing the context into consideration here, but I'm just giving you an example okay for a case. So, such as actually the case so we cannot compare oranges with diapers forever right I mean, this is something which
08:23:09 can happen on cloud so what song to have a paycheck to ensure that we are well prepared for the actual release date which is Emma.
08:23:17 And then we can move on.
08:23:19 We cannot keep everything for last moment, we can actually keep a project just to share the orders of preparedness for us. That's a rehearsal we can call it as a rehearsal or whatever.
08:23:27 Okay, just to make sure that whoever is ready with those requirements like for someone is working from past six months on a requirement. Maybe he started in free sample.
08:23:34 So he's preparedness with much much better than someone who's just come up with a new requirement for the sample itself, that's embedded in the release governance itself, we now do not approve all that is happening at the particular milestone.
08:23:49 I sent her as a feature is ready, which means that he has a green light from you from impacted videos architecture and requirements subcommittee review.
08:24:04 You may go ahead and start implementing that there is nothing that stops you from doing it. So it's already embedded in the proposal as I said, if we have someone who is working on that.
08:24:14 For the last half of the year, then they just create the ticket. Fast forward to architecture requirements subcommittee green lights grown from videos, and they may start implementing that even in the next week, the stove, what you said the three steps
08:24:36 i mean three steps are not just there, because we are dealing with projects we are dealing with the the committee's who are also busy with a lot of things to get a slot on specific artists of committee or income subcommittee. We know how much time it takes even the PTS are also busy with their own work, so that the use case owner will have to
08:24:42 go through the actually agreement all these committees and on and then finally has to come in.
08:24:48 I'm not against the process here again I want to clarify this I'm not against the process but I still see, there's nothing harm in actually having a pre check to ensure that things are fine.
08:24:58 And that is a rehearsal which is required for us to make sure that we don't have suppressed on the DVD.
08:25:03 Yeah, I understand that, but that rehearsal, because, as you said that there are just meetings with subcommittees and the green light from the videos so nothing is probably preventing requirement owner for writing multiple emails to two videos instead
08:25:22 of just one of the final day. Right.
08:25:26 Yeah. But on that specific day we required the people to be free right on on on on freedom to actually have you should have a slot on the requirement, I mean on on the Beatles calendar or the requirements of committee thing or architecture.
08:25:39 Architecture subcommittees thing where we should be able to present our area.
08:25:43 And we know what is happening because you see a shocker right now runs, two hours of architecture subcommittee which will not be able to complete everything to review and our own our projects architecture for a given release he takes at least three to
08:25:55 four weeks, minimum, that is a minimum.
08:25:58 So in that if you are trying to propose a requirement. Well, it takes its own time, right.
08:26:05 So, the process is good I'm not against the process but I'm trying to be pragmatic with respect to the process here, that there is still good to actually have a preparedness, like what we said, Whoever is ready with the requirements they can jump into
08:26:17 can take it forward and they can actually have a review of it faster. Whoever is not will actually come to know where, where they are lagging and that's still good to actually catch up by the time right.
08:26:28 I see that this rehearsal is truly help people to pre sell to prepare themselves for the upcoming thing than to actually drive them on the last moment.
08:26:43 Because, when this when the requirement to be there he has stopped resources, he has to, he has to move many things behind the scenes also right. So, when he comes with all this preparedness and finally we say no to him because he came late or his preparation
08:26:48 is not good, then it's going to have a Jefferson effect on entire effect. I don't want that to happen. So let's keep a rehearsal where people can see where they are.
08:26:56 If they have something lagging we can actually recommend them this is what is lagging, they can come back to.
08:27:01 Right.
08:27:05 Is the intent here was really to a vote that we use to those five months of back and forth but understand that there are divergent opinion, which is nice, right, we should not always be in alignment.
08:27:18 So we will not make any vote I was also putting in the chat.
08:27:23 The main which was sent on October 1, with some indication.
08:27:30 Again, if we don't need to take a look at pre check, and that's fine but the idea was really to avoid that we lose students five months, and then we screen the local hand ancestor, to go faster, but that's okay, we have vote.
08:27:49 We just don't do anything. I think there is another urgency that we need to debate so so so the first column, we will not be able to do your topics today are more best practice and global requirements.
08:28:06 We have feel decision about uuy to be made.
08:28:13 Just to recap, there is here. Again, which was.
08:28:21 There have been some confusion.
08:28:25 Because the the PTA was notifying former release management, that they did not anticipate any change at the M three, and then later on when the they did some testing in particular with related to the internet based network or requirements.
08:28:44 They stopped doing on define some announcement I don't think we are sharing the right items, because I'm referring to the uuy.
08:29:12 So there have been some discussion that became cool I guess and no, we got a request at CSC liver to see if we auto highs or not.
08:29:05 The UI team to.
08:29:11 Yes, I don't know which 199 APR if we auto hide the UI team to have their container.
08:29:19 If we do not, I believe that the income based network, cannot be completed as well. So I hope I've summarized correctly because I had to organize that was not on the call.
08:29:32 I was just exchanging with zoo.
08:29:44 At MP so they didn't need a new container, but based on the, the initial testing. The he realized that the FC zero before the SU. My Sundays, that they might need to deliver Finally, a container.
08:29:53 So, if I've not summarize correctly, feel free to jump.
08:29:58 Because again, I've been not following everything.
08:30:03 And that's my understanding.
08:30:12 Yeah, there was an error in the link I just updated it and I think I'm showing the correct one. now.
08:30:21 If you do.
08:30:21 Thank you.
08:30:24 So, just for the, for the record on the gate on that change is fine, to take technically that the change is acceptable from the om perspective.
08:30:41 The only concern that we had and we felt.
08:30:59 that we are not in a position here, here to judge whether we should include that are not the only concern is that it's a functional change, and it was submitted, four weeks after the deadline for submission.
08:31:00 I discussed with serum that they didn't anticipate that they didn't anticipated that the deadline for submitting new campaigners in, in the release process is up m three, so that's why I did the clothes that they they sound how many center that they say
08:31:20 that they need unders to the tickets.
08:31:24 That was there in in JIRA.
08:31:27 So, I, I didn't want to judge whether we should include that or we shouldn't that's why we are asking for a theist seat default on that.
08:31:38 The pros are that we can accept this change and you I will be able to deliver their features a cost is that it's only to be unfair for for teams that have been significantly reducing the scope, just to make sure that they are able to meet the deadline,
08:31:57 like for example the CPS team who could be quite substantial amount of work and reduce their features to make sure that they're always on time
08:32:26 We have all the questions so now we need to move and I need to drop to my next goal with the honesty. So, the TMC big on Muslims, the standing and and about the process and date.
08:32:41 I lo to provide a weaver have to uui, so they can finalize their in conveys network requirements.
08:32:44 We also consider that, and I hope I don't push for something that is not with a process.
08:32:51 For now we, the om should not accept any new request, if it is not credited to vision of great, which is the final step, when we sign off or documentation or books vaccines.
08:33:06 So if it is not. And I say books, because sometimes we have a misunderstanding between a books and an issue for me to same thing. So book fixing documentation, and you have great of the vision of the container has the end for the sign of the only things
08:33:24 that from no un team should approve. And therefore, do we agree, of not to provide the review to the UI, considering what's happened over the past week.
08:33:42 YouTube to misunderstanding miscommunication whatever.
08:33:49 Just to make sure that we are aligned here so there are few exceptions that we simply know that are coming. And those exceptions are least in the Gary feel fair that you have here because we have some changes that are still pending
08:34:09 apart, apart from those we know that session is going to submit to more patches too so that will change the container version and rename.
08:34:19 Some of the stuff components, we knew that they are coming.
08:34:24 The only reason why he didn't submit that already, is to no joke dice gating resources.
08:34:34 And that's why he's submitting that one by one, making it work, and then suddenly being another.
08:34:48 We do not predict any more exceptions.
08:35:23 Speaking on mute Catherine's initiated devote
08:35:29 the new UI Weezer.
08:36:04 There's a voting process for granting new UI, a waiver for inclusion of that particular you're into at least
08:36:22 give it another 10 seconds.
08:36:43 Where's mine.
08:36:45 Something has grabbed my mouse.
08:36:58 is greed can eat.
08:37:05 Yeah. Okay. Yeah, there's a question I'm not sure we formally very dead.
08:37:11 Zero my stoner.
08:37:13 We have not.
08:37:18 Yeah, so maybe we should.
08:37:18 Yeah, that's, that's correct.
08:37:22 I.
08:37:23 The one thing.
08:37:24 I mean I think we're in good shape on the, the milestone status. The one thing I wasn't sure about was, I was looking at, at the filter that Christophe put together.
08:37:40 And I'm not sure whether any of this is specifically associated with RC zero or if we can all look at this as RC one.
08:37:51 Is there a way to distinguish that mean does Oh pm and integration feel
08:38:00 that we were in a place to approve RC zero.
08:38:12 So, I believe that all those changes that that we have here.
08:38:21 They can be merged later nothing on them is like showstoppers for for the SEC road.
08:38:33 And men okay we will share with them to do it I just met to a tight end PJs will see that we wouldn't put them into another room. So, we could manage them and master later and shaping them into another.
08:38:49 I know, I was looking at this one it looked like it hadn't been updated for a while.
08:38:55 But it looks like there's some activity on it now.
08:39:01 Nicole about it with session today and he promised to talk with the team and come back to me with the details that I requested so it's not a technical issue that prevents us from merging dispatch, I just didn't want to make a blind merge and just ask
08:39:18 technical details about the password that is used here and we are just waiting right I'm looking on it.
08:39:24 This is a functional requirement which has been asked it's not a glitch or something.
08:39:29 So I'll get back to you with more clarification on this stuff.
08:39:34 Yep. All right, as I said, no technical issues on that but just waiting for, for the feedback. And what was the final resolution I know we were going back and forth with Dan
08:39:48 regarding a large merge requested that finally get resolved, or we get there.
08:39:56 I believe so sit down, would you like to comment on this one.
08:40:00 On the as the NC marriage.
08:40:07 So
08:40:07 marriage to external provider. So, I was going to merge it this morning. To be honest, but I saw that we have a failure on the end shake of of one of the twit psychosis.
08:40:22 So I asked, Alexander and that to look at.
08:40:29 As we are quite unusual towards the center of failure there so you shouldn't have this but she's doing some things here.
08:40:36 So, as soon as we have an answer, and if it goes. We like to avoid six whenever some green.
08:40:46 We will be there for a long time. So, We will notice then you have your has been pronounced so we we love it when it's on it.
08:40:59 So I hope that version bump from SDN scene right one that you marriage recently.
08:41:12 Can you repeat the beach.
08:41:22 It was just a cigar that were referencing to the bottom of it was a long patch and this was was morose yesterday after we had.
08:41:31 We are they received a green, as we mandate know so that was Murcia, as a new user before.
08:41:36 Okay, so what I'm versions of the doctor.
08:41:42 If you compare to what we used to have in the meeting, for example, we can see that the project, provide all new versions except what is missing here now, when you see that with most of the project or regarding the readiness state of what is the DVR took
08:42:06 of us do. I think we are fine. And as much as Christopher is no stopping. Yeah.
08:42:06 Must have project that he will tear up there.
08:42:24 So we can start branching on Hulu, creating a daily on Hulu and continue working on this one on master as much as I should actually pick on Hulu when it's accepted in master.
08:42:22 But I think we can can now branch on Hulu and start re installing the staging in Honolulu for the use cases they need. I asked the people who are dealing with a use case so Krishna, but they are doing everything in their own absolutely don't need additional
08:42:42 support for integration, and then we will just be able to start some stability and residency testing on the owner Lulu branch, based on what we just have today.
08:42:53 Okay. All right. So, what I'm hearing then is that the opinion from om and integration.
08:43:03 And based on the status of the milestone tracking that we can make a recommendation to the TASC to approve RC zero. Any objections to that.
08:43:15 Yeah, I believe that the understanding is correct.
08:43:20 As we are talking about RC zero, I would like to also use this up 14 on behalf of CPS team to ask for a weaver.
08:43:29 So, as I said, the team was working really hard and delivered a lot of stuff in the om that we've been asking for. The only thing that they didn't manage to do is to have the year to have their Ingress protected with a certificate, so that they would
08:43:46 like to ask for them for a weaver to keep them HTTP for falling a little with obviously a vision to fix that in Istanbul.
08:44:02 Okay, it's not far away but maybe waiting for that to happen. At this moment is not the right thing to do because it may take some, some amount of time to get the patch right.
08:44:16 And on the other hand, introducing that later.
08:44:21 Questions, our validation so it would be probably best to go with HTTP and switch to HTTPS, you stumble.
08:44:32 Okay.
08:44:34 All right, so that.
08:44:38 Sorry that CPS right here. I'm sorry. Yes Sorry,
08:44:46 guys.
08:44:49 Interestingly, it also applies to CBS.
08:44:53 That's right.
08:44:56 Is the CPS waiver is that documented.
08:45:01 I don't think so because this is the first time that we are speaking about that we fold that we will be able to help them get their comments. Right. During last week, but we failed to do so so that's why we are asking for this Weaver.
08:45:15 Okay, can, can I just ask that they, you know, go into the, the exception table and document that request.
08:45:28 If you can just show me where this word this exception table is I'm more than happy to fill that in.
08:45:35 Yeah, it's if you access the release page.
08:45:42 See, do I have in here anywhere.
08:45:44 Okay so somewhere under the release page. Yeah, if you go to the main release page, you'll see you'll see a reference in for Honolulu you'll see a reference to a milestone exception.
08:45:59 Okay. And so just add a new entry there if you could follow up with them go well.
08:46:05 Okay. All right, great. So, Kenny so I guess we need a boat from the TASC.
08:46:12 We no longer have quorum. Okay. So, can we follow up with an email boat. Yeah.
08:46:19 Rc zero with the, the exceptions that were mentioned. Yeah.
08:46:26 Okay. All right, and we will will come up with a new proposal for the remainder of the Honolulu schedule and probably update the
08:46:41 that that.