BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

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

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log 

Zoom 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. 00:06:44    N.K. Shankaranarayanan:    #info, N. K. Shankar, IC
00:11:19    Toine SIEBELINK (EST):    sorry I missed the start of the meeting. Time permitting can we have a quick chat about the use of Zoom for ONAP Project meetings. LastPass doesn't seem to work anymore for me/ONAP4) I got a mail in December with new password and code but I cannot login. Only the 'Claim Host' option still works for me...
00:12:59    Paweł Pawlak:    Sure Toine
00:14:49    Toine SIEBELINK (EST):    Reacted to "Sure Toine" with
00:14:54    Sandra Jackson:    #Vote TSC agrees to proposed release planning schedule for New Delhi?
00:14:57    Byung-Woo Jun:    #vote +1
00:14:58    Andreas GEISSLER (DT):    #vote +1
00:15:02    N.K. Shankaranarayanan:    #vote +1
00:15:04    Paweł Pawlak:    #vote +1
00:15:05    Dong Wang (China Telecom):    #vote +1
00:16:35    Sandra Jackson:    #End
00:39:02    Toine SIEBELINK (EST):    BRB
00:43:39    Sandra Jackson:    #Vote: TSC agrees to remove the requirements committee and combine with ARCCOM
00:43:40    Byung-Woo Jun:    #vote +1
00:43:42    Andreas GEISSLER (DT):    #vote +1
00:43:55    Dan Timoney (AT&T):    #vote +1
00:43:56    Dong Wang (China Telecom):    #vote +1
00:44:03    Paweł Pawlak:    #vote +1
00:44:16    Sandra Jackson:    #End
00:44:40    N.K. Shankaranarayanan:    #vote +1
00:46:46    Andreas GEISSLER (DT):    https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Helm+chart+dependencies
00:46:50    Toine SIEBELINK (EST):    back

...

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. 

WEBVTT

1
00:01:30.780 --> 00:01:33.030
Sandra Jackson: Good morning. Happy New Year, Dan.

2
00:01:37.160 --> 00:01:39.220
Byung-Woo Jun: I can hear you, Sandra.

3
00:01:41.770 --> 00:01:42.839
Byung-Woo Jun: How are you doing?

4
00:01:45.410 --> 00:01:47.059
Sandra Jackson: I'm well, how are you?

5
00:01:47.340 --> 00:01:48.669
Byung-Woo Jun: Good. Good.

6
00:01:50.520 --> 00:01:58.359
Byung-Woo Jun: Okay. Enjoy your holiday break. Did you have a holiday break? Yes, I did, December.

7
00:01:58.920 --> 00:02:06.940
Byung-Woo Jun: But I participate. Tsc, but actually, I'm almost off December.

8
00:02:08.699 --> 00:02:09.880
Byung-Woo Jun: Yep.

9
00:02:16.100 --> 00:02:19.159
Sandra Jackson: okay, give it some time here.

10
00:04:53.020 --> 00:04:57.340
Sandra Jackson: Okay, I think we can go ahead and get started here.

11
00:04:57.450 --> 00:05:05.259
Sandra Jackson: just some are regular reminders up on the board. Actually, I'm gonna change this slide because it no longer needs you to do the hashtag

12
00:05:05.480 --> 00:05:18.800
Sandra Jackson: pound. You're here because, the Pcc. Seems to be functional and picking up attendance. So I'll need to update that. But our regular reminders that the meeting is being recorded

13
00:05:18.890 --> 00:05:43.889
Sandra Jackson: all participants are muted upon entry, and if you are dialed in and need to unmute yourself, please, hit the Star 6 to speak, and then just our regular anti-trust policy. If you have any questions about it. You could reach out to your organization's legal counsel, or if you're a member of the Link Foundation, you can reach out to Andrew up to grove lp.

14
00:05:45.450 --> 00:05:51.609
Sandra Jackson: alright jumping into it. Happy New Year! Welcome back, everyone. I hope everyone is refreshing.

15
00:05:51.730 --> 00:05:53.410
Sandra Jackson: Have some time to

16
00:05:54.280 --> 00:05:59.309
Sandra Jackson: has some downtime to just really collect to collect yourselves and

17
00:06:00.600 --> 00:06:03.000
Sandra Jackson: and rest.

18
00:06:05.380 --> 00:06:11.530
Sandra Jackson: I only have one reminder. Right now we have the Governing Board meeting

19
00:06:11.880 --> 00:06:18.839
Sandra Jackson: coming up on January sixteenth, I believe Kenny sent out an email

20
00:06:19.220 --> 00:06:37.840
Sandra Jackson: the beginning of January asking for inputs. But I dropped the template in here in case. So if we can get that to them. Get back to him as soon as possible. The project. Review just anything in the second half of 2023 that you want the governing board to be aware of?

21
00:06:37.940 --> 00:06:43.489
Sandra Jackson:  so that? And then the project review is January sixteenth.

22
00:06:43.860 --> 00:06:46.119
Sandra Jackson: So that is all that I have.

23
00:06:47.300 --> 00:06:49.629
Sandra Jackson: Can we any questions about that?

24
00:06:52.550 --> 00:06:59.419
Sandra Jackson: Okay. so can we move down to the lease and I'll hand it over to Pablo.

25
00:07:08.620 --> 00:07:13.890
Byung-Woo Jun: How are you on, mute? Let me try to start them until Pablo comes back.

26
00:07:14.300 --> 00:07:24.510
Byung-Woo Jun: So this one David used to set up the release plan, and he put for the new Delhi. but since he left, so we need to.

27
00:07:24.830 --> 00:07:29.000
Byung-Woo Jun: But he proposed it, but it was not approved by TSC.

28
00:07:29.140 --> 00:07:30.919
Byung-Woo Jun: So we need to

29
00:07:31.040 --> 00:07:39.679
Byung-Woo Jun: discuss and then review and update the date and then approve as needed. That's the plan power.

30
00:07:41.180 --> 00:07:46.439
Paweł Pawlak: Yeah, yeah, exactly. So. At the last Pdl score.

31
00:07:46.740 --> 00:07:57.999
Paweł Pawlak: you know. we we have, as we have no release manager, so there was nobody who puts lead the meeting. But this is for some others of people need to address whether we want to

32
00:07:58.010 --> 00:07:59.680
Paweł Pawlak: keep the Ptr scroll

33
00:07:59.820 --> 00:08:02.440
Paweł Pawlak: or being part of the CFC,

34
00:08:03.750 --> 00:08:04.670
Paweł Pawlak: yes.

35
00:08:04.940 --> 00:08:11.750
Byung-Woo Jun: yeah. And that's the next call next will Pt Update same same story, but

36
00:08:11.970 --> 00:08:19.149
Byung-Woo Jun: but new daily is already started unofficially, because a couple of the

37
00:08:19.180 --> 00:08:25.010
Byung-Woo Jun: architecture review or requirement, if you already don't. So that means

38
00:08:25.640 --> 00:08:33.210
Byung-Woo Jun:  Can you click the Sand Sandra? Can you click the new daily release planning the link

39
00:08:34.120 --> 00:08:36.190
Byung-Woo Jun: there? I mean the debt. Same

40
00:08:37.270 --> 00:08:40.130
Sandra Jackson: sure. Hold on. Something's in my way. I'm trying to get it out.

41
00:08:40.919 --> 00:08:43.759
Byung-Woo Jun: And then how we're going to add this view.

42
00:08:49.360 --> 00:08:53.799
Byung-Woo Jun: Yeah, this is what David Mcbride put that before he left.

43
00:08:53.870 --> 00:09:02.000
Byung-Woo Jun: So this is the new daily, and then starting November 30, and then first content.

44
00:09:02.990 --> 00:09:20.980
Byung-Woo Jun: The letter is the release candidate. So may 16, and then sign up is June sixth. That's the current schedule. And then, as we agreed during the Montreal, we don't have any. M. One M. 2, M. 3, m. 4. We simplify, based on the onet streamlining.

45
00:09:21.150 --> 00:09:33.349
Byung-Woo Jun: So each Pto. They have the power to process their project development in azure way. So this is schedule. And then we need to review. And then we need to.

46
00:09:33.520 --> 00:09:36.649
Byung-Woo Jun: What do you think? And Pablo back to you.

47
00:09:38.250 --> 00:09:42.100
Paweł Pawlak: yeah, definitely. Especially, okay, we have.

48
00:09:46.450 --> 00:09:58.710
Paweł Pawlak: we have. Okay, we are now mid of January, right? Umhm. So the looking at what's here and we have no specific.

49
00:10:00.710 --> 00:10:06.039
Paweł Pawlak:  I'm trying to figure out.

50
00:10:07.050 --> 00:10:12.470
Paweł Pawlak: because this is Montreal sign off New Delhi. Okay, Kickoff was

51
00:10:12.830 --> 00:10:17.000
Paweł Pawlak: the November thirtieth. Right? Was it? Was it really the thirtieth

52
00:10:17.110 --> 00:10:29.099
Byung-Woo Jun: ye? Yeah. So so he stay. And because architecture committee already got review of the requirement, China telecom China mobile. So we put that. And then

53
00:10:29.210 --> 00:10:34.350
Byung-Woo Jun: so within that gap November 30, and may 16.

54
00:10:34.420 --> 00:10:37.949
Byung-Woo Jun: And we you know, Pto, they

55
00:10:38.020 --> 00:10:51.259
Byung-Woo Jun: whenever they have the new you know. Item to add in, and they can contact Ourcom and other Co, you know, subcommittees and Tsc, and then they what they gonna do so and then add in to

56
00:10:51.590 --> 00:10:58.420
Byung-Woo Jun: release content the Wiki page. II don't think we create for new daily, but I look at the

57
00:10:58.490 --> 00:11:10.930
Byung-Woo Jun: Davis under these content letter from Montreal, and then probably copy and then create Wikipedia. And so Pto can start filling up the information. Yeah, I can do that if you want, if you want.

58
00:11:11.340 --> 00:11:15.840
Paweł Pawlak: Yes, if you could be great. Thank you. Being for this proposal.

59
00:11:16.110 --> 00:11:16.790
Byung-Woo Jun: Okay.

60
00:11:17.060 --> 00:11:28.279
Paweł Pawlak: yeah. At the second site, we will also produce the Wikis for the new Delhi right. If somebody has no access from Gp. Else please submit the ticket

61
00:11:28.420 --> 00:11:35.010
Paweł Pawlak: to to get access to the restricted wiggy where we put the vunabities per project.

62
00:11:38.670 --> 00:11:39.430
Paweł Pawlak: Yeah.

63
00:11:41.190 --> 00:11:45.020
Paweł Pawlak: okay, so do we need to vote officially on on those dates

64
00:11:45.310 --> 00:11:46.760
Paweł Pawlak: as of today

65
00:11:49.210 --> 00:11:52.559
Paweł Pawlak: in the in the comments on this.

66
00:11:53.210 --> 00:11:57.260
Byung-Woo Jun: I think we can vote cause we use the board for this.

67
00:11:57.490 --> 00:12:00.890
Byung-Woo Jun: So I think we have a quorum today.

68
00:12:01.220 --> 00:12:03.609
Byung-Woo Jun: 5 people.

69
00:12:04.940 --> 00:12:06.360
Paweł Pawlak: no quorum. So

70
00:12:06.390 --> 00:12:18.190
Byung-Woo Jun: no, no, we have coral. I think we have. Okay, yeah. Cause the NK. Andrew is is, yes, he's connected. Yeah, yeah. So I think that we are cool.

71
00:12:20.330 --> 00:12:21.599
N.K. Shankaranarayanan: And I'm here.

72
00:12:22.380 --> 00:12:24.749
Sandra Jackson: So you're gonna put the language and chat.

73
00:12:25.190 --> 00:12:33.039
Paweł Pawlak: If we have a call room, let's do the vote right. It's important to have the community good visibility on the start and end date

74
00:12:33.800 --> 00:12:34.990
Paweł Pawlak: of the

75
00:12:35.760 --> 00:12:38.690
Paweł Pawlak: of the release and and efforts. Time.

76
00:12:40.700 --> 00:13:07.480
Byung-Woo Jun: I think the for your already mind. The last time we mentioned will only have streamlining. This is initial on date and based on the the Pto. And then progress. So this Rc. Date can be changed and sign up. They can be changed. That's the way our agreement. So David. Therefore, once you're here, just to Rc, and then sign up so. And anyway, so for today. This is a date.

77
00:13:15.890 --> 00:13:18.380
Sandra Jackson: So tfc, it hold on.

78
00:13:19.640 --> 00:13:22.939
Sandra Jackson: What's the language? Tse agrees to

79
00:13:25.790 --> 00:13:29.089
Byung-Woo Jun: release planning for new Delhi, maybe

80
00:13:32.020 --> 00:13:36.819
Sandra Jackson: to propose release planning

81
00:13:38.760 --> 00:13:40.319
Sandra Jackson: release planning schedule.

82
00:13:42.550 --> 00:13:45.160
Sandra Jackson: Is that right? Let me put that in.

83
00:13:45.610 --> 00:13:48.580
Sandra Jackson: Let me put it so you could see. Hold on so you can.

84
00:13:49.660 --> 00:13:53.009
Sandra Jackson: so you can see

85
00:13:55.340 --> 00:13:56.760
Sandra Jackson: it will help if I edit.

86
00:14:10.950 --> 00:14:12.619
Sandra Jackson: Do you dare to be dirty

87
00:14:14.170 --> 00:14:16.469
Sandra Jackson: for? Oh, sorry

88
00:14:16.960 --> 00:14:20.199
Sandra Jackson: release. Let me schedule. Sorry for new daily.

89
00:14:26.410 --> 00:14:27.140
Sandra Jackson: Yeah.

90
00:14:27.340 --> 00:14:28.550
Byung-Woo Jun: Yep, I think.

91
00:14:29.330 --> 00:14:31.870
Sandra Jackson: okay, so I will drop that in chat.

92
00:14:55.470 --> 00:14:57.600
Sandra Jackson: and the vote is open.

93
00:15:11.370 --> 00:15:20.969
Paweł Pawlak: I think it would be good to to have some short summary at the beginning of the release, right? When we start working on the release on what we expect to deliver.

94
00:15:21.160 --> 00:15:25.699
Paweł Pawlak: And then by end of the release checking okay, what we deliver it.

95
00:15:26.860 --> 00:15:42.620
Paweł Pawlak: Hmm! I guess this. This is part of the architectural subcommittee where you collect the requirements for the release. Right? Yes, that's my job to us. That's what I'm trying to create a Wikipage copying the David Mcbride

96
00:15:42.620 --> 00:15:59.830
Byung-Woo Jun: as a release content under, you know, content. So I'm going to put the Arctic just subcommittee. On what feature, and also Pto can add the feature they are going in going into under new dally, then around the Rc. Date that we know.

97
00:15:59.970 --> 00:16:10.399
Byung-Woo Jun: we see the Wiki page, and we see the older collected features. And so we can create the lease content and also time to time we look at the Wiki pages, and we know

98
00:16:10.440 --> 00:16:13.350
Byung-Woo Jun: which feature are going to be in

99
00:16:13.420 --> 00:16:22.350
Byung-Woo Jun: new daily. So that's that's my view. But anyway, so first of all, I'm going to before before Monday. I'm going to create the dead page.

100
00:16:22.430 --> 00:16:26.260
Byung-Woo Jun: and then we can next week, and we can start

101
00:16:26.330 --> 00:16:29.339
Byung-Woo Jun: filling up the contents for new daily.

102
00:16:29.610 --> 00:16:33.660
Paweł Pawlak: Yeah, it's also valuable. Yeah, yeah, sure.

103
00:16:34.450 --> 00:16:35.819
Paweł Pawlak: Yes, Sandra.

104
00:16:36.620 --> 00:16:39.009
Sandra Jackson: sorry. Okay, carry on.

105
00:16:39.250 --> 00:16:46.840
Paweł Pawlak: This is also valuable. When I produce some. You know marketing materials, summary for the release, and so on. So worry where

106
00:16:47.030 --> 00:16:54.030
Paweł Pawlak: all this information is stored so easy, accessible for everyone. Right?

107
00:16:54.600 --> 00:17:06.280
Byung-Woo Jun: We can change it format as needed. But I just for now I could. I'm gonna copy as this and change the the release. But since you gonna provide your your

108
00:17:06.430 --> 00:17:12.519
Byung-Woo Jun: you know. Stop. So maybe we can. Change to. you know. Content format, whatever we need.

109
00:17:12.910 --> 00:17:13.660
Byung-Woo Jun: Okay.

110
00:17:18.819 --> 00:17:19.640
Sandra Jackson: okay.

111
00:17:22.099 --> 00:17:27.590
Sandra Jackson: any other. Nothing else further with it with the new Delhi release.

112
00:17:29.700 --> 00:17:33.749
Sandra Jackson: So they will move on to Ptl. Updates.

113
00:17:35.940 --> 00:17:40.100
Paweł Pawlak: I've seen twan make a comment. So twan

114
00:17:40.210 --> 00:17:42.030
Paweł Pawlak: would you like to to share some.

115
00:17:43.580 --> 00:17:57.999
Toine SIEBELINK (EST): Yeah, this falls on the desk. That's great. Thanks Pavel. It's just now I realize I haven't been. I've missed a few meetings over the the holiday period just before Christmas. There was a mail sent about, if you own up.

116
00:17:58.220 --> 00:18:01.829
Toine SIEBELINK (EST): So zoom accounts being deleted, I think

117
00:18:01.920 --> 00:18:13.419
Toine SIEBELINK (EST): open up, for the one I'm using is is one of the ones being kept. Now the mail said something about the password changing now. I never had access to the password before I use last pass.

118
00:18:13.800 --> 00:18:34.270
Toine SIEBELINK (EST): Which kind of kind of worked sometimes with a bit of a few extra clicks, I was able to log in using Last Pass. But now this year I had my first meeting, and I was trying to use the the owner for account, and it it didn't work for me. Also the password I was in the mail didn't work, so last Pass didn't work for me.

119
00:18:34.470 --> 00:18:58.239
Toine SIEBELINK (EST): The password was in the mail didn't work I actually eventually got blocked out while there was a half-hour block. So I presume that was released. I was able to join the meeting as somebody else, and then claimed the host, using the new PIN code that was in the mail. So yeah, I'm basically asking, is, is there a change that I'm not aware of, or other people having issues, or is there? Is there a more serious problem?

120
00:18:58.340 --> 00:19:12.379
Byung-Woo Jun: Did you get the email from Kenny Paul? I think he sent the email the new zoom, that's the mail, and that mail had a new password and a new PIN code. But that password didn't work for me.

121
00:19:12.590 --> 00:19:14.150
Byung-Woo Jun: Okay.

122
00:19:14.260 --> 00:19:22.320
Byung-Woo Jun: And then also, he sent separate email for a host key to yeah, the host, the host, Id. I did use that for

123
00:19:22.860 --> 00:19:27.709
Andreas GEISSLER (DT): applying to get to be the host also in my own meeting.

124
00:19:27.800 --> 00:19:33.750
Andreas GEISSLER (DT): So using that and querying for the host and then using this

125
00:19:34.310 --> 00:19:40.040
Andreas GEISSLER (DT): this pass code with the the host, the zoom host. Id

126
00:19:40.380 --> 00:19:51.589
Toine SIEBELINK (EST): that that worked for me at least. Yeah. Yeah. Same for me, Andrea. I could do that, but that means we can't cancel reschedule meetings or anything like that.

127
00:19:51.660 --> 00:20:14.710
Paweł Pawlak: Stop working. And

128
00:20:14.710 --> 00:20:33.000
Paweł Pawlak: yeah, it was never the best tool for for me. It worked up to that mail that we got at Christmas, so up to then I was able to use Last pass as I said, sometimes a bit tricky, but I used to be able to get in, but since that mail I haven't been able to log in

129
00:20:33.040 --> 00:20:36.349
Toine SIEBELINK (EST): either with last pass or with that password that was in the mail.

130
00:20:36.940 --> 00:20:55.889
Byung-Woo Jun: Okay, I don't know who's handling the last pass, but start working full outcome. So that's why I'm I'm using the second meeting Zoom Meeting. Yes, anyway. Discontinued for a while we've been on. I believe this call one password

131
00:20:55.990 --> 00:20:58.030
Sandra Jackson:  at.

132
00:20:58.150 --> 00:21:04.459
Sandra Jackson: I wanna say, last passes, probably discontinued here sometime last year. So

133
00:21:05.280 --> 00:21:18.369
Toine SIEBELINK (EST): that's good to know. Yeah, okay, I'd like to get rid of it on my laptop. It really annoys me. Actually, okay, that's good to know. But then why does the password that was in the mail? Not work? That's the question. Then

134
00:21:18.740 --> 00:21:20.880
Toine SIEBELINK (EST): same problem. Yeah.

135
00:21:25.010 --> 00:21:30.989
Paweł Pawlak: Well, we simply haven't explored the the the passport capability right yet. So.

136
00:21:31.230 --> 00:21:39.179
Paweł Pawlak: but if it doesn't work for you, I'm I don't think it would work for us. Right? So probably we need to raise a raise a question to Kenny

137
00:21:39.240 --> 00:21:41.759
Paweł Pawlak: as a response to this email pet

138
00:21:42.290 --> 00:21:44.899
Paweł Pawlak: that do you have this problem.

139
00:21:45.270 --> 00:21:52.819
Toine SIEBELINK (EST): I did that yesterday to be honest with you, but I presume Kenny is is off off, maybe on leave. I don't know.

140
00:21:53.460 --> 00:22:06.879
Sandra Jackson: No, he's not only he. He had a conflict this morning, but I will. I'm just putting a note here, so I'll follow with him. Let me double check my mail again. I didn't. I've had a few other meetings. I might have got a mail from him in the meantime.

141
00:22:07.160 --> 00:22:15.500
Toine SIEBELINK (EST): but I didn't think I saw anything. No, I didn't get a reply from him, and I sent him a mail about 24 h ago, but a chance to look at it

142
00:22:18.020 --> 00:22:22.420
Toine SIEBELINK (EST): because of us passwords and stuff in the mail. I didn't. I didn't. CC, anybody else.

143
00:22:24.480 --> 00:22:25.300
Sandra Jackson: Okay.

144
00:22:25.630 --> 00:22:28.749
Sandra Jackson: so I'll follow up with you about that.

145
00:22:32.440 --> 00:22:55.970
Andreas GEISSLER (DT): May. Yeah. May maybe another question regarding passwords. We enabled, or Lf. It enabled the 2 factor authentication on Garrett. Right? And I had I had my Microsoft authenticator running, and it was integrated. But

146
00:22:56.040 --> 00:22:58.720
Andreas GEISSLER (DT): unfortunately, my

147
00:22:58.970 --> 00:23:06.040
Andreas GEISSLER (DT):  my mobile has been completely wiped out.

148
00:23:06.050 --> 00:23:08.090
Andreas GEISSLER (DT): How can I

149
00:23:08.250 --> 00:23:15.550
Andreas GEISSLER (DT): get? Let's say the code again to get a new entry on another phone or a new phone.

150
00:23:15.880 --> 00:23:22.199
Andreas GEISSLER (DT): So I haven't found that anywhere in either in garret nor in the lf.

151
00:23:22.290 --> 00:23:29.700
Andreas GEISSLER (DT): Whatever web pages where I could. We established then. or reconnect my authenticator, then to

152
00:23:30.520 --> 00:23:31.410
Paweł Pawlak: hold up

153
00:23:33.090 --> 00:23:38.300
Andreas GEISSLER (DT): to yeah, to the to the garret, so is there any

154
00:23:38.380 --> 00:23:41.099
possibility, or is there any

155
00:23:41.280 --> 00:23:45.139
Andreas GEISSLER (DT): thing which I would need to reply for, or

156
00:23:45.210 --> 00:23:50.179
Andreas GEISSLER (DT): a request for. Jessica? Do you know anything?

157
00:23:52.430 --> 00:24:00.919
Andreas GEISSLER (DT): II even don't remember how I got the old. Let's say authenticator entry for

158
00:24:01.530 --> 00:24:03.420
Andreas GEISSLER (DT): a little. N,

159
00:24:03.820 --> 00:24:06.049
Jessica Wagantall: I'm not sure. Actually

160
00:24:06.280 --> 00:24:07.240
Andreas GEISSLER (DT): okay.

161
00:24:07.920 --> 00:24:11.000
Paweł Pawlak: Kevin. Maybe you. You have some. You know something

162
00:24:13.890 --> 00:24:15.919
Paweł Pawlak: how to get the authenticator

163
00:24:16.440 --> 00:24:19.340
Paweł Pawlak: working on the new new Mobile.

164
00:24:23.520 --> 00:24:26.120
Paweł Pawlak: Mr. Kevin. are you with us?

165
00:24:28.430 --> 00:24:30.260
Kevin (LF): I'm sorry, guys. Can you hear me? Now?

166
00:24:30.280 --> 00:24:31.969
Paweł Pawlak: Yeah, here you will.

167
00:24:32.050 --> 00:24:33.700
Kevin (LF): can you repeat that question, please.

168
00:24:34.450 --> 00:24:48.820
Andreas GEISSLER (DT): so yeah, sorry, II lost my my phone with my account for so with my, my, my Microsoft authenticator. Entry for the 2 factor, authentication for get it

169
00:24:49.020 --> 00:25:00.579
Andreas GEISSLER (DT): and I wanted to re-establish the connection. So usually you have a co-r code or something which you can scan but I haven't found anything on

170
00:25:00.670 --> 00:25:07.290
Andreas GEISSLER (DT): when I locked in into get it, or wherever how to re-establish or reconnect a new

171
00:25:07.540 --> 00:25:11.880
Andreas GEISSLER (DT):  whatever phone or authenticator.

172
00:25:12.160 --> 00:25:15.979
Andreas GEISSLER (DT): To to to use the two-factor authentication!

173
00:25:16.140 --> 00:25:18.410
Do you know anything? How to do that?

174
00:25:18.670 --> 00:25:37.279
Kevin (LF): Actually, this is the first time I hear something like that. But I can do some quick research I personally use different than Microsoft authenticator that allows me to have a in case I lose my phone. I don't know how it works for Microsoft authenticator, but

175
00:25:37.440 --> 00:25:45.139
Kevin (LF): let me check it. From which side we can rest or or try to link a new. a new authenticator app.

176
00:25:46.290 --> 00:25:50.159
Andreas GEISSLER (DT): Yeah. So it was working for the Microsoft authenticator. No problem.

177
00:25:50.360 --> 00:26:01.630
Andreas GEISSLER (DT): Yeah. I had an entry, but I lost the entry. But III don't know how to reconnect then my authenticator. Actually, that's the only issue. So it worked for me. No problem.

178
00:26:03.110 --> 00:26:12.199
Sandra Jackson: I was gonna say, it didn't give you an option to usually, when I use the 2 factor authentic here, and if I have to switch phones or whatever it is, say.

179
00:26:12.350 --> 00:26:20.449
Sandra Jackson: it gives you an option to authenticate a different way, maybe email or whatever. And then you can go in and remove the old phone. It didn't give you that option, either.

180
00:26:22.930 --> 00:26:29.609
Andreas GEISSLER (DT): Yeah, I mean I as I said so I I'm I can. Let's say log in via my

181
00:26:29.680 --> 00:26:44.620
Andreas GEISSLER (DT): Let's say your laptop, of course, to to get it, and so on. That's not an issue, we answered, but I think I had some times where II was asked for to authenticate myself again, and then, of course, if I don't have the authenticator and the access, then of course, I cannot do that.

182
00:26:44.920 --> 00:26:49.290
Andreas GEISSLER (DT): So. But as long as I have my my.

183
00:26:49.370 --> 00:27:04.009
Andreas GEISSLER (DT): let's say laptop working, that's that's at the moment working for me. But you know, for the future when I ever have to re authenticate. Then, of course, I'm I'm in trouble with that. So yeah, kind of reset would be good or re authenticate, or something like that.

184
00:27:04.560 --> 00:27:11.460
Paweł Pawlak: Andres. But have you re installed the new new Microsoft authenticate on your new mobile new Mobile already?

185
00:27:11.530 --> 00:27:20.280
Andreas GEISSLER (DT): Yes, I have that. But it was not so. Let's say the initial or the accounts have not been stored

186
00:27:20.460 --> 00:27:28.460
Andreas GEISSLER (DT): in Microsoft. Unfortunately, yeah, in in the cloud. So otherwise you would have been. Let's say you would get that

187
00:27:28.840 --> 00:27:41.610
Andreas GEISSLER (DT): from Cloud again. So that's right. But as I was with my private or with my with my company phone. I was not using the cloud here.

188
00:27:41.810 --> 00:27:44.690
Paweł Pawlak: Okay, so let's let's

189
00:27:45.460 --> 00:27:55.899
Paweł Pawlak: let's Kevin to take a look. If not, then I suggest maybe to open. Lf, it tickets. Right? That's how to get it re established for you.

190
00:27:55.960 --> 00:28:00.249
Paweł Pawlak: Norman. The the account for Links Foundation, Sso.

191
00:28:00.280 --> 00:28:04.350
Paweł Pawlak: Uses our email addresses that we,

192
00:28:04.510 --> 00:28:09.869
Paweł Pawlak: you know, are using for lf, it for lf, id, right?

193
00:28:11.240 --> 00:28:12.180
Paweł Pawlak: Hmm.

194
00:28:13.200 --> 00:28:14.030
Paweł Pawlak: so

195
00:28:15.860 --> 00:28:39.210
Andreas GEISSLER (DT): and maybe check.

196
00:28:39.320 --> 00:28:40.960
Paweł Pawlak: Okay, okay.

197
00:28:43.540 --> 00:28:48.309
Paweł Pawlak: I'd like to share with you guys some good news right, we have

198
00:28:48.490 --> 00:28:49.530
Paweł Pawlak: free

199
00:28:49.870 --> 00:28:54.630
Paweł Pawlak: sub sap vice chairs right so

200
00:28:55.270 --> 00:29:01.909
Paweł Pawlak: to Dong Wang and take one. Heung also joined. So

201
00:29:02.200 --> 00:29:04.619
Paweł Pawlak: I'm really happy that we have for

202
00:29:05.050 --> 00:29:09.940
Paweł Pawlak: such a high rate of of supporters for for the

203
00:29:10.210 --> 00:29:12.019
Paweł Pawlak: you know, governance. And

204
00:29:12.290 --> 00:29:17.659
Paweł Pawlak: and so, yeah, I'm really happy to to work with you guys for the for this year.

205
00:29:18.410 --> 00:29:25.689
Paweł Pawlak: So thank you for submitting your proposals and thank you, Tsc community, for approving and accepting the those proposals. I'm really happy.

206
00:29:26.630 --> 00:29:29.470
Byung-Woo Jun: Thank you, Paulo. I do my best assist you.

207
00:29:29.490 --> 00:29:34.119
Paweł Pawlak: And along with

208
00:29:34.940 --> 00:29:37.329
Sandra Jackson: yes, congratulations following you.

209
00:29:38.280 --> 00:29:47.549
Paweł Pawlak: And as we have team also, maybe maybe viewing. You would like to share also some some updates Portimo would like to think of

210
00:29:47.870 --> 00:30:02.290
Byung-Woo Jun: requirements. Requirements, subcommittee understand? But before we go there the how how to manage Ptr meeting to have.

211
00:30:02.420 --> 00:30:03.440
Paweł Pawlak: Yeah.

212
00:30:05.300 --> 00:30:11.149
Paweł Pawlak: So the question is, do we need to have release manager to to have Pts meeting?

213
00:30:12.660 --> 00:30:29.710
Byung-Woo Jun: I my opinion I don't think this should be one of the Pto. Should lead a Ptr. Meeting to me. because it's their decision. And then they you know, they exchange their their the information, and then they we can. We can attend

214
00:30:29.900 --> 00:30:40.480
Byung-Woo Jun: Ptr. Meeting, but they should drive to Ptm. Meetings one of the Pto. You know, one of the Pto. So if we don't have any volunteer, maybe

215
00:30:40.510 --> 00:30:44.039
Byung-Woo Jun: that we can discuss the next week. But I think the

216
00:30:44.080 --> 00:30:49.310
Byung-Woo Jun: to me one of the Pts should and do this. But anyway

217
00:30:50.120 --> 00:30:53.299
Paweł Pawlak: And this could be shifting. Roller doesn't have to be like

218
00:30:53.380 --> 00:31:12.489
Paweł Pawlak: every time just one person that is responsible, we could do it but Co. Per quarter, for example, II think the key question is, and this should be us through the Pts. Right is having this meeting valuable, that we have this opportunity to discuss operational things, and you know how to manage projects. What is the impact

219
00:31:12.660 --> 00:31:17.179
Paweł Pawlak: of the certain function functionalities, or, or, you know, changes in the

220
00:31:17.320 --> 00:31:30.010
Paweł Pawlak: in the Lf. It, and so on. Right? So there are different topics also, sub so subcommittees can come and and present some latest, latest achievements or questions to the Vtl, so

221
00:31:30.260 --> 00:31:31.760
Sandra Jackson: who's energy during

222
00:31:32.860 --> 00:31:35.720
Paweł Pawlak: Sandra? You want to be, maybe on mute?

223
00:31:36.030 --> 00:31:36.690
Andreas GEISSLER (DT): Okay.

224
00:31:36.830 --> 00:31:51.159
Andreas GEISSLER (DT): II think it's useful. I think we should keep it, although I'm I'm also not often participating but I think that's for discussing all these technical dependencies and the things. I think it's useful to have that

225
00:31:51.270 --> 00:31:56.319
Paweł Pawlak: half an hour right. But I think it's it's worth to keep it

226
00:31:56.420 --> 00:32:02.140
Paweł Pawlak: to ensure that whenever we have any question point, or you know something to be discussed.

227
00:32:02.230 --> 00:32:06.539
Paweł Pawlak: We have some quorum of of few pities that can show some.

228
00:32:07.010 --> 00:32:13.950
Paweł Pawlak: some some takeaways right? And we can, as a as a other on up contributors, we can consult

229
00:32:14.010 --> 00:32:17.840
Paweł Pawlak: with the Ptl's. Certain things right.

230
00:32:18.230 --> 00:32:30.460
Byung-Woo Jun: I fully agree with their address in you, and because they have to exchange technical dependency and and findings. So they should share, you know, among Pto. And then, if there is no volunteer.

231
00:32:30.590 --> 00:32:59.680
Byung-Woo Jun: and maybe we can use what Andress did. You know oem model, I think, before Oem has Pto and Andress. You know, they have a lotate meeting. So every week they have different the, you know. Intern. Right? So, pto, so they just. But we can use that model if if no one wants to dedicate this meeting, this meeting. But we can use them. Anyway. I agree. We need this meeting. Yeah.

232
00:33:01.110 --> 00:33:05.449
Paweł Pawlak: okay, so any feedback from the Ptl. Score present. So

233
00:33:05.520 --> 00:33:07.520
Paweł Pawlak: guaranteed Thomas.

234
00:33:07.980 --> 00:33:18.219
Paweł Pawlak: Yeah. Sorry. Above all, I actually had to propose for a minute there had somebody at the door here. So we're agreeing to to keep the meeting. Reduce it to half an hour.

235
00:33:18.670 --> 00:33:29.250
Paweł Pawlak: for example. Yes, just to give, to keep it, to give opportunity to both. Ptl's to discuss certain things, but also other community members to to consult things with.

236
00:33:29.430 --> 00:33:31.020
Paweł Pawlak: With. Ptl's right.

237
00:33:31.780 --> 00:33:37.470
Toine SIEBELINK (EST): Yes. And do you want to? Always have it on? Or do you want to have a more like an on demand thing?

238
00:33:38.090 --> 00:33:51.480
Byung-Woo Jun: I think we consider having it always on hoping that details could come right, because that's the better model, because on demand and it doesn't work. Well.

239
00:33:51.670 --> 00:34:05.129
Toine SIEBELINK (EST): yeah, I think Liam was. He's not here to day. But I think Liam was proposing to combine it with this meeting. II do find there's a lot of overlap between these meetings. I use either meeting to bring issues up like like this who I had to day?

240
00:34:05.750 --> 00:34:20.580
Toine SIEBELINK (EST): I know historically. And then there is probably some separation between the 2 meetings. Well, it's yeah. I would prefer if it could be combined to with this one, and it would be only one meeting per week, and I know that would be Liam's preference as well

241
00:34:20.929 --> 00:34:26.949
Paweł Pawlak: depends on depends on yeah, that's good. But depends on the discussion topic. So

242
00:34:27.010 --> 00:34:37.539
Byung-Woo Jun: Pto could tend to technical discussion. You'd be talking about the dependency and findings. Okay. But Tsc, we not necessarily going into that deep?

243
00:34:37.620 --> 00:34:51.129
Byung-Woo Jun: So that's why Andres, he said. You know any dependency between Pto and then projects. And and then, after that, you know, reporting to Tsc, Csc, just need to know high level, not to

244
00:34:51.310 --> 00:35:07.709
Byung-Woo Jun: detail level. You know, that's that's why kind of separation. So you know, there was the purpose of the Pta meeting, or originally, if you combine it, we have to end up listening to all the technical detail, or someone not interested here. So that's my my preference.

245
00:35:08.000 --> 00:35:15.380
Toine SIEBELINK (EST): Yeah, you want to keep the separation. And maybe we just need to wait and see how much need to risk for the Monday meeting.

246
00:35:16.080 --> 00:35:21.890
Maybe we can scale it back further to every second week, or something like that. If if we find simply not enough

247
00:35:22.110 --> 00:35:41.730
Toine SIEBELINK (EST): need for it. We we can always, you know. Just yeah. Let's let's let's take small step at a time. So maybe reduce to half an hour for now and see what happens. See if there's uptake. See how how much is needed, and see if we have somebody to volunteer to pull it. I'm I'm not jumping.

248
00:35:41.740 --> 00:35:45.820
Toine SIEBELINK (EST): I have to admit. So yeah, let's see what happens. Maybe

249
00:35:46.320 --> 00:35:54.709
Byung-Woo Jun: let's see, for now let's did you study me and see what happened. If the discussion content, just update. And you know no separation. But

250
00:35:54.760 --> 00:35:58.030
Byung-Woo Jun: I hope there's some technical discussion, you know. So okay.

251
00:35:58.310 --> 00:35:59.650
Toine SIEBELINK (EST): okay, thanks.

252
00:36:00.570 --> 00:36:01.530
Paweł Pawlak: Okay.

253
00:36:03.020 --> 00:36:07.890
Paweł Pawlak: So, to conclude, we keep the meeting, but we we make it 30 min. So

254
00:36:07.960 --> 00:36:11.490
Paweł Pawlak: we would have this opportunity. And we can then address, based on the.

255
00:36:12.080 --> 00:36:16.050
Paweł Pawlak: you know. Take aways we have from few meetings at least. Right?

256
00:36:17.020 --> 00:36:20.249
Toine SIEBELINK (EST): But who's gonna lead it the the next time? Pavel?

257
00:36:21.270 --> 00:36:31.109
Paweł Pawlak: Some good leader we are we? Are. We are asking for volunteers. Okay? So we need to volunteer between now and next Monday.

258
00:36:31.140 --> 00:36:36.640
Toine SIEBELINK (EST): Yes, yes, I saw that Ptl. Means leader.

259
00:36:36.650 --> 00:36:40.889
Byung-Woo Jun: I know. I know. I know. I know, I know, I know, I know.

260
00:36:41.110 --> 00:36:49.179
Paweł Pawlak: But yeah, definitely, okay, this could be rotating role as we discussed, right? Doesn't have to be like the like. One person have to

261
00:36:49.320 --> 00:36:53.550
Paweł Pawlak: do the job. But maybe we can try to

262
00:36:54.120 --> 00:37:01.279
Byung-Woo Jun: rotate the role rotate. And this this one, I think, Andrew, you know another option is

263
00:37:01.300 --> 00:37:07.530
Toine SIEBELINK (EST): They'll just see who shows up. And then then, you know, then then agree together with Who's there? Who's gonna lead it that week.

264
00:37:08.790 --> 00:37:10.310
Byung-Woo Jun: Yeah, okay.

265
00:37:10.960 --> 00:37:15.349
Byung-Woo Jun: sounds good. Yeah. I think. Also, that's the best solution. So

266
00:37:16.620 --> 00:37:17.300
Andreas GEISSLER (DT): yep.

267
00:37:17.550 --> 00:37:25.079
Toine SIEBELINK (EST): motivating to come.

268
00:37:25.570 --> 00:37:31.190
Toine SIEBELINK (EST): Unfortunately. But when I'm there I might, I'm I'm happy to leave at your time.

269
00:37:35.500 --> 00:37:36.400
Paweł Pawlak: Okay.

270
00:37:36.840 --> 00:37:39.219
Byung-Woo Jun: okay, next one. Okay.

271
00:37:40.390 --> 00:37:41.420
Sandra Jackson: okay.

272
00:37:41.520 --> 00:37:55.419
Byung-Woo Jun: Okay. Next one, though. Timo. And I discuss about this as a background. So currently outcome is handling both requirement and architecture reviews. And there's no problem. And we have done during the Montreal

273
00:37:55.510 --> 00:38:07.920
Byung-Woo Jun: and Timo as a photo enhancement. And then, since there's no activity to require subcommittee, and we just retire or remove the required subcommittee officially.

274
00:38:08.040 --> 00:38:11.019
Byung-Woo Jun: and then archive all the wiki pages.

275
00:38:11.120 --> 00:38:23.500
Byung-Woo Jun: And then that's the idea. Just the currently functionally outcome already took over of the requirements subcommittee. So that's why, Timo, I suggest to remove it. Timo so is use.

276
00:38:24.220 --> 00:38:31.900
Timo Perala: Yeah. Hi, so yes, thanks. You know, I think this is in in a nutshell. Exactly

277
00:38:32.010 --> 00:38:33.860
Timo Perala: my my proposal. So

278
00:38:34.900 --> 00:38:40.629
Timo Perala: Tsc. Last year May decided that we will

279
00:38:40.660 --> 00:38:48.189
Timo Perala: experiment as further streamlining effort to combine this this reviews

280
00:38:49.130 --> 00:38:51.040
Timo Perala: for the.

281
00:38:51.100 --> 00:38:56.699
Timo Perala: for the release that was starting, and that already. Then we said that, depending on how

282
00:38:57.020 --> 00:39:05.499
Timo Perala: how this works, then we might want to take further streamlining steps, and there has been absolutely 0.

283
00:39:05.990 --> 00:39:07.940
Timo Perala: Reach out

284
00:39:08.370 --> 00:39:13.880
Timo Perala: to to Requirements subcommittee during

285
00:39:14.110 --> 00:39:20.110
Timo Perala: this time period. So between end of May last year and today.

286
00:39:20.330 --> 00:39:33.419
Timo Perala: which kind of led me to conclude that maybe we are now in a place where one committee, one subcommittee of Tsc can handle both requirements and

287
00:39:33.720 --> 00:39:35.570
Timo Perala: and architecture issues.

288
00:39:36.620 --> 00:39:39.230
Timo Perala: And and we, we can make it simpler.

289
00:39:39.780 --> 00:39:59.310
Byung-Woo Jun: Yeah. Okay. So last year, as the team would set, the requirement review happened at the outcome, not at the required of some company. That's why you have no activities there but activities. So anyway, now the you know, we need to officially retire. We require committee. So

290
00:40:00.190 --> 00:40:04.799
Timo Perala: yeah, that the reason why I raised that there was no activity is that there

291
00:40:05.300 --> 00:40:09.309
Timo Perala: originally there were other topics

292
00:40:09.980 --> 00:40:15.200
Timo Perala: or other responsibilities for requirements subcommittee

293
00:40:15.220 --> 00:40:25.689
Timo Perala: in in the early days. But they have been more or less dead letter for quite a few years already, so

294
00:40:25.890 --> 00:40:31.890
Timo Perala: there is nothing will be lost if if the requirements of committee is, is no longer there.

295
00:40:36.290 --> 00:40:43.939
Timo Perala: or rather, if all those things that are necessary from the requirements point of handling point of view, will be handled by the arcom.

296
00:40:45.430 --> 00:40:46.889
Timo Perala: I think it works fine.

297
00:40:49.780 --> 00:40:56.800
Byung-Woo Jun: for now the since there's no deployment subcommittee activity and then hander by the outcomes. So maybe Tsu can both

298
00:40:56.820 --> 00:40:59.529
Byung-Woo Jun: remove required subcommittee officially.

299
00:40:59.590 --> 00:41:11.089
Byung-Woo Jun: and then, if, as needed some, you know, at the beginning of the only place a lot of, you know, require a new feature, new, you know, testify, we creating quite subcommittee now, only this mature and then on.

300
00:41:11.220 --> 00:41:21.109
Byung-Woo Jun: So anyway. So we can recreate, you know, if you, you know, demand is high, but for now, since no activity, so why not remove it

301
00:41:21.460 --> 00:41:22.350
Byung-Woo Jun: anyway?

302
00:41:24.820 --> 00:41:32.049
Byung-Woo Jun: So Sandra also agree on that. So should we need we? Do we need to vote for that? Or is that an agreement which can be done?

303
00:41:33.870 --> 00:41:43.549
Byung-Woo Jun: Tsc. Already agreed to? Functional merging? And for the time and up the Requirements subcommittee. Maybe we won't vote it. Agree this team or once.

304
00:41:43.590 --> 00:41:57.649
Byung-Woo Jun: and once the Ts agree that, I defined the selection point, which is suggest by Timo. So that means we're gonna either archive requirement Wiki pages under Tsc sub, currently and or move to under our outcome, Wiki.

305
00:41:57.820 --> 00:42:12.489
Byung-Woo Jun: And then any difference, we're gonna move to under outcome. And then I'm going to update outcome description to, you know, embed the requirement review function. So that's the action point. So for that action point. I hope the

306
00:42:12.690 --> 00:42:14.249
Byung-Woo Jun: yes, you can vote

307
00:42:15.950 --> 00:42:17.689
Byung-Woo Jun: team only stayed year one? Right?

308
00:42:20.520 --> 00:42:22.760
Timo Perala: Yeah. I think that's exactly correct.

309
00:42:23.700 --> 00:42:24.430
Byung-Woo Jun: Thanks.

310
00:42:24.920 --> 00:42:25.740
Timo Perala: Yes.

311
00:42:27.160 --> 00:42:33.299
Paweł Pawlak: So let's vote. And again, thank you, Timo, for for leading requirements. Subcommittee.

312
00:42:36.650 --> 00:42:37.600
Timo Perala: Thank you.

313
00:42:37.900 --> 00:42:41.639
Paweł Pawlak: and thank you. Viewing for hosting it

314
00:42:41.940 --> 00:42:44.650
Paweł Pawlak: as well within the Architectural Subcommittee.

315
00:42:44.760 --> 00:42:48.549
Byung-Woo Jun: My pleasure. Thank you. Team will help me a lot. So.

316
00:42:49.140 --> 00:42:53.549
bayon, can you say that one more time you said that you're gonna embed the

317
00:42:55.230 --> 00:43:03.619
Byung-Woo Jun: I think, though, that the agreement has been done last year already functional. So for now we just Tsc. Agree to remove the requirements subcommittee.

318
00:43:04.650 --> 00:43:07.130
Byung-Woo Jun: and then, you know, can

319
00:43:07.710 --> 00:43:11.389
Byung-Woo Jun: outcome took over takeover. So yes, sir.

320
00:43:15.280 --> 00:43:19.369
Sandra Jackson: is that right? Okay, I just wanted to make sure.

321
00:43:21.940 --> 00:43:22.870
Sandra Jackson: Okay.

322
00:43:23.020 --> 00:43:27.050
Sandra Jackson: alright, I'm gonna drop this in. Hold on. Give me a second.

323
00:43:40.010 --> 00:43:41.740
Sandra Jackson: and the vote is open.

324
00:43:54.680 --> 00:43:57.670
Sandra Jackson: Okay, I lost count. Let me get. Can't hear.

325
00:44:07.870 --> 00:44:09.860
Byung-Woo Jun: Got it.

326
00:44:10.230 --> 00:44:12.279
Sandra Jackson: We have it. Okay? So

327
00:44:12.520 --> 00:44:14.890
Sandra Jackson: we're going to go ahead and

328
00:44:17.910 --> 00:44:20.870
Sandra Jackson: alright. thank you. All for voting.

329
00:44:30.900 --> 00:44:31.680
Sandra Jackson: Okay.

330
00:44:32.270 --> 00:44:47.959
Byung-Woo Jun: okay. Next one this is kind of a announcement and advertisement. And don't want. And, Jenny, they are going to provide the proposal for data service announcement of intend driven network for New Delhi.

331
00:44:48.070 --> 00:45:01.189
Byung-Woo Jun: So this is a requirement review and then, pass through some architecture also so, and and don't want Zen, could you provide more detail as so we can have a more audience in the outcome next Tuesday.

332
00:45:01.670 --> 00:45:04.860
Sandra Jackson: Do you need to share anything?

333
00:45:06.270 --> 00:45:11.750
Dong Wang (China Telecom): Yeah, we will join the meeting. that's the Tuesday.

334
00:45:11.770 --> 00:45:12.950
Dong Wang (China Telecom): Thank you.

335
00:45:13.950 --> 00:45:15.359
Byung-Woo Jun: Okay. Sixteenth.

336
00:45:24.780 --> 00:45:27.130
Byung-Woo Jun: okay, okay, okay, good.

337
00:45:27.200 --> 00:45:30.450
Sandra Jackson: Thank you. Bail. Thank you, darling. Okay.

338
00:45:31.370 --> 00:45:33.229
Sandra Jackson: I don't think they have any house.

339
00:45:33.480 --> 00:45:36.669
Sandra Jackson: No andres andress a one oem update

340
00:45:37.190 --> 00:45:50.180
Byung-Woo Jun: and coupled Master Helium chart

341
00:45:50.460 --> 00:46:01.689
Byung-Woo Jun: from the project, Helen chat. So we can we allow the the CD based deployment. But we at that time, once you we agreed to have the

342
00:46:01.740 --> 00:46:09.100
Byung-Woo Jun: same Master Rosen and and Andress that's the background. Go ahead this year's now. Voice. Yes.

343
00:46:09.330 --> 00:46:14.260
Andreas GEISSLER (DT): yeah. I would like to present something, Sandra, if you can give me presentation rents.

344
00:46:17.040 --> 00:46:21.469
Sandra Jackson: Sorry I was on mute. I'm just gonna stop sharing. And you should be able to present.

345
00:46:23.220 --> 00:46:24.870
Okay, thank you.

346
00:46:24.980 --> 00:46:41.600
Andreas GEISSLER (DT): Yeah, so basically. Iii put this in in some slides or in some some page last year already. I will put this into maybe the chat so that we can have that link here.

347
00:46:41.990 --> 00:46:43.240
so

348
00:46:45.120 --> 00:47:04.280
Andreas GEISSLER (DT): what? What we what we did so in former times, as you might remember when we had in O in Om. So M. We will. We we are using for deploying and and and the the help charts all, all help. Charts are included in that.

349
00:47:04.390 --> 00:47:17.069
Andreas GEISSLER (DT):  that Om project, as you know, and we have a kind of umbrella own up chart still, which we also still using in the

350
00:47:17.220 --> 00:47:43.250
Andreas GEISSLER (DT): in the gating tests and in the daily tests, rounds, and so on. And in, let's say, in the official documentation or deployment guides which we are using. Yeah. So this one is basically a kind of umbrella project which has a chart. And in the chart we have basically the dependencies to all of the components. Basically, which

351
00:47:43.470 --> 00:47:49.779
Andreas GEISSLER (DT): which are deployed. And as you see in the master branch, we have

352
00:47:49.960 --> 00:48:11.840
Andreas GEISSLER (DT): these kind of white cards here. So everything which starts with 13 will be taken for that for Montreal. And that's the reason what? And the procedure we used to have was, okay, we created an Om, basically a branch. Let's say,

353
00:48:11.840 --> 00:48:34.350
Andreas GEISSLER (DT): In London we have a branch. And here it was the twelfth. Oh, and then we all in the master. We changed every every helm chart to the next release. So 13 and so on, and everyone starts with 13 again. So this we did also for for for Montreal.

354
00:48:34.360 --> 00:49:02.669
Andreas GEISSLER (DT): And we decided beforehand that we want to decouple that so every component should be, let's say, able to select their versions as they want. But it has, of course, drawbacks. Yeah. And this is what I wanted wanted to show a bit in that page where we had these chart dependencies. Yeah, if you see your components, let's say, help charts, as I'm talking

355
00:49:02.670 --> 00:49:22.560
Andreas GEISSLER (DT): always about help charts has, for example, a component master component chart like cps. Yeah. And this has sub charts and the the sub charts. And the master chart has sub dependent dependencies to their own sub charts, using as well these kind of white cards. Yeah.

356
00:49:22.890 --> 00:49:49.249
Andreas GEISSLER (DT): and it uses, even from other components, like common component chart or database charts, which are also from another chart, using them as well, using wildcards with the same kind of versioning here, and finally, the job, or when you install and compile the charts, they would be then stored in

357
00:49:50.190 --> 00:49:54.939
Andreas GEISSLER (DT): type of nexus or in your own. Let's say, hem repositor.

358
00:49:55.340 --> 00:50:11.479
Andreas GEISSLER (DT): So what? What we actually do not want anymore, actually. Or that was the decision that we do not want to bind these kind. Or let's say, release dependent versions and change everything.

359
00:50:11.480 --> 00:50:28.980
Andreas GEISSLER (DT): Every component version on update to a new version number because it does not show as well the progress of the component itself. So and we wanted to to leave the components owners, to choose their

360
00:50:28.990 --> 00:50:39.140
Andreas GEISSLER (DT):  their version numbers. Yeah. Now, now, that means in master, at the moment, as you see.

361
00:50:39.500 --> 00:50:46.729
Andreas GEISSLER (DT): I have not updated here everything to 14. So I left it as it is. Yeah, that means

362
00:50:46.940 --> 00:50:50.720
Andreas GEISSLER (DT): whenever they would be a component deciding

363
00:50:50.830 --> 00:51:19.849
Andreas GEISSLER (DT): to update. Now to 14, I would need to update this as well it to have, let's say, always the latest version to be tested. Yeah. I would need to update, or it has to update as well the Mo. The master chart. Currently, yeah, because I'm using this as as still in in our, let's say, as I said in the in the and the integration team in the daily. testing. And in the gating. Yeah, in the

364
00:51:20.330 --> 00:51:42.520
Andreas GEISSLER (DT): what I did in actually in Montreal. To make this a bit more stable and fix, I change this to fix dependencies. That means it. It uses a certain fixed numbers, like, for example, Cps, had already updated their version number to 1301. I

365
00:51:42.810 --> 00:51:56.249
Andreas GEISSLER (DT): choose that one. Yeah. So that means, if Cps is now changing their numbers, that would not be indirectly included in the in the Cp. In that Montreal release. Yeah, even if it's then 13. 2.

366
00:51:56.300 --> 00:51:57.330
Andreas GEISSLER (DT): Yeah.

367
00:51:57.540 --> 00:52:17.729
Andreas GEISSLER (DT): That's that's one possibility. What we would need to do. So, Maria, to be galera. I did updates other. The other ones are still in 1,301. So I'm not 100% sure how we would continue would be would be the best method, but definitely it would be good. If then, further

368
00:52:18.200 --> 00:52:28.240
Andreas GEISSLER (DT): changes are done in components and they should, and they would not be, let's say, part of, or they should not

369
00:52:28.700 --> 00:52:37.949
Andreas GEISSLER (DT): cause any updates on the under, my, on the on on the Montreal release. They should change their version numbers actually in their

370
00:52:38.610 --> 00:53:02.450
Andreas GEISSLER (DT): main chart, and possibly also they have their their sub charts. Yeah, that would be a recommendation. But I'm also not 100 sure how we do that, especially if it comes to this kind of of, let's say, shared or or template charts, like the common chart, or the the the Maria dB. Or the gala chart, and so on. How we do that.

371
00:53:02.450 --> 00:53:25.289
Andreas GEISSLER (DT): I think we cannot force here, whenever a a change in the in the common chart has been done, that every other chart which is using the common chart has, or also to update their version numbers. That means we have this kind of semantic versioning rules here with the with these kind of white cards, and I think they should.

372
00:53:25.380 --> 00:53:29.059
Andreas GEISSLER (DT): Still work it will.

373
00:53:29.110 --> 00:53:38.419
Andreas GEISSLER (DT): It will cause maybe some hiccups, partly if we don't change the number and but

374
00:53:38.530 --> 00:53:47.660
Andreas GEISSLER (DT): if there is, there's a recompilation, and we have this white card. It might take then, even newer number newer versions, even if we compile.

375
00:53:48.100 --> 00:53:50.229
Andreas GEISSLER (DT): let's say, the charts of

376
00:53:50.240 --> 00:54:04.889
Andreas GEISSLER (DT): montreal, for example, yeah, with that version. So, but generally the rule would be, you should update your component charts if you change anything

377
00:54:05.210 --> 00:54:07.650
Andreas GEISSLER (DT): and depending.

378
00:54:07.890 --> 00:54:34.719
Andreas GEISSLER (DT): and you ha! Just have to take care that these kind of umbrella chart in the master branch if if you if you change a major number, basically that would need to be updated as well. So if you decide to change to 14 something, you should update this here, otherwise it would not be included in the in a kind of gating or in a daily result. Yeah, which we still want to have. Right?

379
00:54:34.980 --> 00:54:37.460
Byung-Woo Jun: That would be my my suggestion

380
00:54:37.960 --> 00:54:38.890
Andreas GEISSLER (DT): or the moment.

381
00:54:39.190 --> 00:54:52.739
Byung-Woo Jun: Okay? So the question so if I think this is good topic in Ptr meeting, too, this is a really good topic. Yeah. So Ptr meeting, you know, we can discuss photo anyway, for question is.

382
00:54:52.920 --> 00:55:02.850
Byung-Woo Jun: if the project, Pto, they said, no major changes in new daily and just maybe minor maintenance, you know. So

383
00:55:02.860 --> 00:55:10.549
Byung-Woo Jun: in that case, do you prefer they change to 14 anyway, or just leave 13. So what

384
00:55:10.860 --> 00:55:22.289
Byung-Woo Jun: what kind of option they have? I mean, preference is probably moving to 14, and because they simplify all the dependencies. But changing helm charts is not a big effort either. But

385
00:55:22.450 --> 00:55:23.670
Byung-Woo Jun: anyway, so

386
00:55:23.970 --> 00:55:24.640
no.

387
00:55:29.260 --> 00:55:32.019
Byung-Woo Jun: no, we can. Yeah, go ahead.

388
00:55:32.510 --> 00:55:34.210
Andreas GEISSLER (DT): So

389
00:55:34.950 --> 00:55:37.250
Andreas GEISSLER (DT): yeah. So

390
00:55:39.920 --> 00:55:51.619
Andreas GEISSLER (DT): I think we just need to decide that. So but changing everything to 14, let's say as we did it before, of course, does not really show

391
00:55:52.020 --> 00:55:53.930
Andreas GEISSLER (DT): let's say

392
00:55:55.650 --> 00:55:59.980
Andreas GEISSLER (DT): let's say not changed projects. Let's say

393
00:56:00.180 --> 00:56:03.870
Andreas GEISSLER (DT):  that means the

394
00:56:04.470 --> 00:56:12.939
Andreas GEISSLER (DT): whatever. If that what we, for example, know homes is not changing. Let's say but we change to 14

395
00:56:13.140 --> 00:56:20.120
Andreas GEISSLER (DT): It will not reflect. That there is no change in in homes right? And

396
00:56:20.820 --> 00:56:25.800
Andreas GEISSLER (DT): II would not do that in that way. So I would leave that on 13

397
00:56:25.880 --> 00:56:27.290
Andreas GEISSLER (DT): and

398
00:56:27.360 --> 00:56:31.279
Andreas GEISSLER (DT): just that. Let's say, do do do do

399
00:56:31.510 --> 00:56:44.600
Andreas GEISSLER (DT): the integration team. And basically, as long as we do the the OM. Let's say, deployment via this. This this helm charts, master charts, we should just need to be prepared.

400
00:56:45.180 --> 00:57:03.589
Andreas GEISSLER (DT): that that this has to be updated as well. So whenever you do that a major change you will need to take care that this kind of umbrella chart name number, is also changed. That's that's for you just to make you aware. But maybe that we can discuss also in the in the Pta meeting. That's right.

401
00:57:03.750 --> 00:57:24.609
Byung-Woo Jun: Yeah. And and last year we defined this, the Montreal we did short term the you know the decision. We gonna follow this rules and then in the future. The you know, real future is, every project can have the different major. If there is only no major changes, they don't have to change it. But it

402
00:57:24.690 --> 00:57:54.010
Byung-Woo Jun: can create some headache for gating and an oem perspective. So that's why we need to do further discussion at the Pto. How much headache oem team gonna have without, you know, following the rules? Or is it time to? We just thought we gonna support this in the future? But this new daily is the future. So that means the Pto meeting. We gonna make decision. And then you put back Tsc, you know. Desk. My preference. Okay, that's good. Thank you. Andres, yeah.

403
00:57:55.440 --> 00:57:57.889
Byung-Woo Jun: Good. Good. Good point andress.

404
00:57:58.310 --> 00:57:59.010
Andreas GEISSLER (DT): Thank you.

405
00:57:59.360 --> 00:58:00.080
Byung-Woo Jun: Okay?

406
00:58:01.750 --> 00:58:03.459
Andreas GEISSLER (DT): Alright, that was it.

407
00:58:13.660 --> 00:58:16.859
Sandra Jackson: Okay, thank you.

408
00:58:19.130 --> 00:58:28.140
Sandra Jackson: I think the next thing was just housekeeping. We didn't have anything listed, so I guess I will ask if there are any questions, comments, or last minute

409
00:58:28.680 --> 00:58:30.370
Byung-Woo Jun: I have

410
00:58:30.420 --> 00:58:32.879
N.K. Shankaranarayanan: Sandra, I have a comment, yeah.

411
00:58:33.040 --> 00:58:34.240
Sandra Jackson: go ahead. Go ahead.

412
00:58:35.120 --> 00:58:40.489
N.K. Shankaranarayanan: Yeah. During this till about March or so

413
00:58:40.520 --> 00:58:46.510
N.K. Shankaranarayanan: this Rtsc. Call conflicts with the Osc. Call.

414
00:58:46.980 --> 00:58:53.100
N.K. Shankaranarayanan: And so I'm and I'm actually on that call as well. And statues there, there's a lot

415
00:58:53.230 --> 00:58:59.590
N.K. Shankaranarayanan: things happening there. And so I just wanna let people know I'm gonna keep track of that.

416
00:58:59.920 --> 00:59:05.280
N.K. Shankaranarayanan: And the problem will go away in march, I think, because I believe

417
00:59:05.900 --> 00:59:06.690
N.K. Shankaranarayanan: one of

418
00:59:07.310 --> 00:59:09.700
N.K. Shankaranarayanan: in one of the calls changes.

419
00:59:09.710 --> 00:59:15.180
N.K. Shankaranarayanan: That's when the Us. Changes time zones daylight savings.

420
00:59:15.270 --> 00:59:27.969
N.K. Shankaranarayanan: but yeah, it's things are happening there. There's there's discussions about how Nephio is used in Osc. And and Smo, and all that is is also connected with

421
00:59:28.630 --> 00:59:34.109
N.K. Shankaranarayanan: all the things we have been discussing or the use of own app for Orlandi.

422
00:59:35.250 --> 00:59:44.780
N.K. Shankaranarayanan: Just thought I would let you know. Yeah. And then quick update on the Lfn Tac. Meeting. I think it was a short meeting yesterday. Some description number security.

423
00:59:46.450 --> 00:59:48.619
N.K. Shankaranarayanan: I think it'll pick up more later.

424
00:59:49.440 --> 00:59:54.759
Sandra Jackson: Yeah, there was really. There really wasn't a discussion on security.

425
00:59:54.790 --> 01:00:13.210
Sandra Jackson: it was left off to whatever they last discussed. I think the sixth of December. So they're gonna come back and and revisit that. And I think that they are going to schedule a meeting to discuss that in in more detail. So you didn't. There was really nothing to update

426
01:00:13.230 --> 01:00:15.209
Sandra Jackson: as far as the security

427
01:00:16.280 --> 01:00:17.460
Sandra Jackson: on tackle.

428
01:00:18.180 --> 01:00:21.619
Byung-Woo Jun: What scope of the security discussions they are providing.

429
01:00:23.990 --> 01:00:29.589
Sandra Jackson: If you're looking for a name name, just tap at type at Nk, and it will show up.

430
01:00:30.470 --> 01:00:40.370
Sandra Jackson: Oh, okay, I'm just like, I'm curious about the scope of this security discussion in the tech.

431
01:00:40.510 --> 01:00:44.090
Byung-Woo Jun: So that's why? And then, second may wants to,

432
01:00:44.450 --> 01:00:46.180
Byung-Woo Jun: you know. Understand?

433
01:00:46.640 --> 01:00:47.300
Byung-Woo Jun: So

434
01:00:52.220 --> 01:00:55.230
Sandra Jackson: so who was it? Is it, Amy?

435
01:00:55.570 --> 01:01:14.439
Sandra Jackson: I think Amy? And I believe she's she's yeah. Yeah. So so it's the same thing. And it's just mainly, I guess, getting the other elephant project in line with it. I think I wanna say, and I don't wanna see you gotta turn, but I'm pretty sure onap is in line with it already, since a lot of that

436
01:01:14.620 --> 01:01:17.059
Sandra Jackson: started here but

437
01:01:17.340 --> 01:01:26.039
Sandra Jackson: But getting like the the security badges and things of that nature and and pushing that forward in the other Lfn projects to.

438
01:01:26.430 --> 01:01:28.820
Sandra Jackson: you know. Give that

439
01:01:29.200 --> 01:01:40.069
Sandra Jackson: insurance. That open source is secure, or whatever. But Amy covered a lot of that here and on that. So that's why I think. You're pretty up to date on it.

440
01:01:40.120 --> 01:01:49.639
Sandra Jackson: And I think the efforts to get that push throughout the el other elephant projects is what they're going to meet on and and things of that nature.

441
01:01:49.940 --> 01:01:53.040
Sandra Jackson: And hopefully, I didn't miss anything. Did I cover that right?

442
01:01:53.070 --> 01:02:00.509
N.K. Shankaranarayanan: Yeah, no, that that's right. It it was not that much. The there wasn't that much impact on on app. You know. I think it's more

443
01:02:00.740 --> 01:02:09.299
N.K. Shankaranarayanan:  trying processes for other other elephant projects. I think Amy's leading on that. And she and Amy would be the best

444
01:02:09.590 --> 01:02:11.179
N.K. Shankaranarayanan: person to touch base on that.

445
01:02:11.550 --> 01:02:13.360
Byung-Woo Jun: Okay, you're gonna contact me.

446
01:02:13.560 --> 01:02:14.240
Byung-Woo Jun: Oh.

447
01:02:24.050 --> 01:02:26.889
Sandra Jackson: any other comments. Thank you for that shanker.

448
01:02:27.320 --> 01:02:40.949
Byung-Woo Jun: One comment about the following of the interest point. So I think it's good topic for Pto. So I'm not sure andress you gonna bring this

449
01:02:40.960 --> 01:02:44.929
Byung-Woo Jun: the topic to Pto meeting next Monday.

450
01:02:45.090 --> 01:03:01.539
Byung-Woo Jun: and I don't know who's gonna volunteer for next week Pto meeting. But anyway, so I, if possible, Andrea's putting up this issue to Ptl and we discuss and and possibly make some decision and then update to Tsc

451
01:03:01.870 --> 01:03:04.519
Byung-Woo Jun: next week or so, is that, okay.

452
01:03:04.730 --> 01:03:08.579
Andreas GEISSLER (DT): yeah. Andres, okay, yeah, we can do that. Umhm, okay, yeah.

453
01:03:11.070 --> 01:03:12.519
Sandra Jackson: Excuse me.

454
01:03:13.840 --> 01:03:22.919
Sandra Jackson: Okay. well, if there's nothing else you all actually get some time back again. Congratulations to

455
01:03:23.090 --> 01:03:28.279
Sandra Jackson: they on for the

456
01:03:28.540 --> 01:03:29.510
Sandra Jackson: rice.

457
01:03:29.980 --> 01:03:31.910
Sandra Jackson: Thank you. Chair.

458
01:03:31.970 --> 01:03:39.749
Sandra Jackson: I know they call it different things in different community. So I'm trying to get myself together. Vice chair for ownat, we appreciate you stepping up

459
01:03:39.860 --> 01:03:48.940
Sandra Jackson: looking forward to working with you all and you Happy New Year to everyone again, and I hope everyone's refreshed, and

460
01:03:49.160 --> 01:03:52.380
Sandra Jackson: you have a good day. We'll see you same time next week.

461
01:03:52.670 --> 01:04:02.610
Paweł Pawlak: Just a small comment. Next week I will be on this business trip, so we'll not be able to attend. Do you see meeting in the week after I'm taking one week of winter holidays.

462
01:04:03.140 --> 01:04:12.519
Paweł Pawlak: So, unfortunately for the next tst meetings I won't be here, so I hope, beyond Eggwang. And and don't you could leave those meetings.

463
01:04:12.820 --> 01:04:14.620
Paweł Pawlak: Sure we're doing. Thank thank you.

464
01:04:14.640 --> 01:04:17.689
Sandra Jackson: That's that's very nice. I'm so jealous.

465
01:04:17.930 --> 01:04:27.300
Byung-Woo Jun: Yeah, yeah. Enjoy your time of power. Enjoy enjoy your time.

466
01:04:27.420 --> 01:04:28.990
Byung-Woo Jun: Sandra. 1 one more.

467
01:04:29.130 --> 01:04:36.120
Sandra Jackson: one more. So next week towine twine he agreed to run the Pto meeting next Monday.

468
01:04:36.280 --> 01:04:45.180
Byung-Woo Jun: so that means he will record the meetings, and then Andrews will bring up this issue to the Pta meeting. That's the kind of

469
01:04:46.080 --> 01:04:54.420
Byung-Woo Jun: I don't need any access to any.

470
01:04:54.550 --> 01:04:59.600
Toine SIEBELINK (EST): Oh, who? What's the story with the zoom call for this? Anybody can run us. Yeah.

471
01:05:00.990 --> 01:05:04.570
Toine SIEBELINK (EST): When we joined it was already auto recording. Right?

472
01:05:05.550 --> 01:05:13.889
Paweł Pawlak: Yeah. Recording. Then the point is to attach that push the recording to

473
01:05:14.470 --> 01:05:23.419
Paweł Pawlak: the wiki right? So I think this is the only one, or maybe do some small scenario of the meeting. If there are some certain points, a address addressed right

474
01:05:25.960 --> 01:05:31.070
Paweł Pawlak: on the wiki that are already, is there. or make a copy of this? Wiki?

475
01:05:31.390 --> 01:05:37.700
Toine SIEBELINK (EST): Yeah. But what's the story with the host? Blaming the host.

476
01:05:39.120 --> 01:05:56.149
Sandra Jackson: So I believe the Pto meeting is now run out of Pcc. Twon, and I could. I'm pretty sure that was before David left, he said. He set it up in Pcc. So there is. No, you don't have to claim the host. Yeah. Once. Once you log on

477
01:05:56.150 --> 01:06:24.799
Toine SIEBELINK (EST): once you log on, you should be able to share and do whatever anybody can share at the moment.

478
01:06:25.160 --> 01:06:30.349
Byung-Woo Jun: Okay, I'll give you a reminder to you to one. Okay, thanks, Bill.

479
01:06:30.650 --> 01:06:33.960
Toine SIEBELINK (EST): Okay. You volunteer. You need to help, though, as well.

480
01:06:34.110 --> 01:06:42.110
Byung-Woo Jun: Okay, I do. I do. I send you. I send the email before the meeting.

481
01:06:42.460 --> 01:06:44.079
Paweł Pawlak: Okay, thank you, guys.

482
01:06:44.160 --> 01:06:47.420
Sandra Jackson: thank you. Bye, bye.

483
01:06:48.070 --> 01:06:49.469
Sandra Jackson: bye-bye. Have a good one.

484
01:06:49.540 --> 01:06:50.980
Byung-Woo Jun: You, too, bye.