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

Passcode: 209247

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

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log

 06:57:22 From  Alla Goldner  to  Everyone:
    #info Alla Goldner, Amdocs
06:58:42 From  Fred Oliveira  to  Everyone:
    #info Fred Oliveira, Self
06:59:21 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT
06:59:58 From  Matt Watkins  to  Everyone:
    #info Matthew Watkins, Linux Foundation
07:00:01 From  Yuanhong Deng (China Mobile)  to  Everyone:
    #info Yuanhong Deng, China Mobile
07:00:16 From  Dong Wang (China Telecom)  to  Everyone:
    #info Dong Wang, China Telecom
07:00:22 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #info N.K.Shankar, STL
07:00:34 From  Amy Zwarico  to  Everyone:
    #info Amy Zwarico, AT&T (proxy for Catherine Lefevre)
07:00:35 From  Ranny Haiby (Linux Foundation)  to  Everyone:
    #info Ranny Haiby, Linux Foundation
07:01:26 From  Magnus Buhrgard  to  Everyone:
    #info Magnus Buhrgard (Ericsson)
07:01:37 From  Bruno Sakoto  to  Everyone:
    #info Bruno Sakoto, Bell Canada
07:01:43 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
07:02:56 From  bin.yang@windriver.com  to  Everyone:
    #info Bin Yang,Wind River
07:03:43 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
07:15:21 From  Amy Zwarico  to  Everyone:
    +1
07:29:07 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    Kenny,
07:29:26 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    Kenny, here is the link to the email re. OOF and GPL
07:29:27 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    https://lists.onap.org/g/onap-tsc/message/8587
07:31:21 From  Thomas KULIK (DT)  to  Everyone:
    https://wiki.onap.org/x/w4IEBw#
07:39:26 From  RAJEWSKI Lukasz (Orange)  to  Everyone:
    https://wiki.onap.org/display/DW/Super+Committers
07:39:28 From  RAJEWSKI Lukasz (Orange)  to  Everyone:
    :)
08:01:57 From  Jessica Wagantall  to  Everyone:
    Regarding the SuperCommitters group, please use "Release Engineering Team"  to add as reviewers. ( FYI. the group name was taken from ODL for consistency but if people want to change the name to easily remember it please let me know)
08:06:09 From  Fiachra CORCORAN (EST)  to  Everyone:
    https://gerrit.onap.org/r/gitweb?p=ci-management.git;a=blob;f=jjb/externalapi/externalapi-nbi.yaml;h=6bda3cba0d37b32a04ecb02257b363536419078b;hb=5f3332793cb2c6596b7bcf8ca06fbaa51004fef5
08:07:46 From  Fiachra CORCORAN (EST)  to  Everyone:
    https://jenkins.onap.org/view/externalapi/

Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative!   Information as to why .
They are included here as a time stamp cross-reference for the recording only!  The notes above this line and the actual recordings are authoritative. 

07:02:06 Okay. Good morning. Good afternoon. Good evening. Good night, wherever you may be in the world.
07:02:10 It's a bit of a Glowy drizzly day here in the San Francisco bay area.
07:02:15 The sun is almost peaking up over the east hills.
07:02:19 I am on My second pepsicola and let's get rolling, meetings being recorded. You all will have seen the little pop-up.
07:02:35 Everyone comes in muted. Please keep yourself. muted unless you're speaking, and if you're coming in on a phone line, you can use Star 6 to unmute yourself.
07:02:44 If you happen to send me a private zoom message the chat window, it will become part of the public record, because I simply cut and paste all of that into the meeting minutes, as always we'll start off by mentioning our
07:02:59 company's our company, the Lfs anti trust policy.
07:03:07 Notice. This is important where we have different companies, including potential industry competitors participating in these meetings.
07:03:14 Please review it. If you have any questions, please contact companies, Legal Council members of the Lf.
07:03:20 May also contact Andrew up to Grove, the firm. Gesmer, Upthrough, of Llp.
07:03:23 Which provides legal counsel to the linux foundation on today's agenda.
07:03:35 We'll be talking about jakarta cover our normal railing stuff.
07:03:43 Talk about super committer rights. discussion here on external Api and discussion on reviving Gitlab.
07:03:58 Just got gitlab integration archiving a repo.
07:04:05 Oh, M. Committer, Magnus has a new liaison statement to cover, and then we have some of our normal business and housekeeping anything else that needs to be added. Okay, Eric.
07:04:22 See you came in. Thank you and and been Thank you. Okay.
07:04:30 If not, I will go ahead and turn it over to David, and thanks Kenny.
07:04:39 Stop sharing where's Button got covered up there we go Okay, Thanks.
07:04:49 Kenny sent out my usual weekly update yesterday.
07:04:59 There's a link there in the agenda if you have an edge to read that just a few things that i'd like to highlight.
07:05:12 We have our release candidate coming up on April 20 eighth.
07:05:18 And I wanted to mention that you know we've had this unmaintained projects.
07:05:30 Group working group meeting on mondays and we've proposed a process for tracking the mediation of dependencies on unmaintained projects, and we want to track it using a global requirement.
07:05:52 So let me show you what I mean. Find it here. Okay, Hopefully, everyone can see that
07:06:19 So what the process would look like is that we would identify dependencies on unmaintained projects that's a whole separate issue, and to itself, which we will discuss at a later date.
07:06:36 Then, what we want to do is propose a global requirement for each unmaintained project for which active projects have dependencies.
07:06:48 So an example of that would be aaf, for example. so we would follow our normal requirements.
07:06:56 Process create an Rq. epic jira, then create individual tasks in each project that has a dependency on that unmaintained project.
07:07:10 And attach those to the the requirement epic, and then track to completion.
07:07:18 So you can see that this looks very much like other global requirements.
07:07:26 That we have similar process. The exception, though, is that our normal global requirement requires that we go through a best practice phase.
07:07:39 Now, if you think about it, it doesn't really make sense for and then maintain project dependency for it to be B to be a best practice and initially right, the best practice means new software.
07:07:53 So i get I guess it's possible but unlikely that we would have Projects initiating dependencies on a on an unmainted project.
07:08:05 And so what I'd like to do is for for this one particular case of creating global requirements to track dependencies on that maintain projects.
07:08:20 I'd like to request an exception from the global requirement process of first going through the the best practice phase.
07:08:35 Hopefully, that that makes sense. Does Does anyone have any questions on what I'm asking for here?
07:08:41 Did that make sense? he Yeah, I clicked the link that's in the minutes, but I it didn't seem to go anywhere for me.
07:08:59 Which link are you referring to the gr exception for dependency removal?
07:09:08 Well, that's a document that's the document that I just showed.
07:09:19 Yeah, I mean I I tested it last evening so it should yeah I'm: i'm getting i'm getting nothing when I when I go to it.
07:09:33 Okay. well, I can see if I can fix it later.
07:09:40 Yeah, Not sure. Yeah. needs to be attached if if this is being put forward as any kind of vote or anything today. we needed attached to the minutes directly.
07:09:56 Yeah, I'm not sure I I tested it when I set it up. I don't know.
07:10:01 I I know this page was edited later, so maybe something happened during the editing.
07:10:09 Let's say, yeah, I don't know there's no attachment on the page, though.
07:10:30 Yeah. okay, Well, it may have happened when I when I copied it over from because this this was originally on last week, and then we canceled last week's meeting.
07:10:43 So that may be the issue. Anyway, i'll i'll take care of it.
07:10:51 Okay, So sorry for the interruption, David, on on the procedural issue.
07:11:03 Is this something that you wanted to put forward for a vote today?
07:11:06 Yes, I have a question, David is this: I had an action that was, and I had this discussion with Krishna on the Os Gpl.
07:11:22 3 requirement. is this directly related to that or different issue?
07:11:29 Because yeah, Catherine added some notes in here. after I had set up this section, and i'm not be honest.
07:11:39 I'm not sure what that what that refers to yeah I don't think that's directly related.
07:11:43 Yeah I don't think it is because with it's not it's not as if it's unmainted.
07:11:48 It's just that. there is no technical to to meeting that requirement. But I think sophisticated it's something else. Yeah.
07:11:58 So okay, maybe we should not have that under that blog.
07:12:03 It is misleading. so canny that
07:12:10 I think she put it there. this because it was part of the Buddy status going to be discussed.
07:12:16 Sorry, Marshall. I didn't fully hear marshall you know Marshall said, that she he thinks that Catherine put it here because it's just part of the overall least discussion that's that's fine as long
07:12:29 as we and since we're on the topic I think both pdl, I think I checked with Krishna, and he was responded to the email friend.
07:12:41 That it's it's not straightforward meeting that requirement because of dependency on the code work needed, and then finding people to do that.
07:12:56 And then he has documented that and he's there so there's an email thread on that as well, so there's no easy answer there.
07:13:07 Okay, is the could you drop a link to the email thread?
07:13:15 Okay, yeah. with the chat window for me, please. Yeah. Okay, Kenny.
07:13:28 I fixed the the file length there on the page. Okay, so show is linked, because sometimes that goofs up and where it's a link. I can open it in the new tab.
07:14:06 Okay, So this is v one. The more Tsc. discussion on this before we put it to a vote.
07:14:19 And has this been shared with the ptls Yet because that would be Catherine's first question?
07:14:28 To be honest, I can't really remember we didn't have meeting this week.
07:14:34 We had. We We discussed it in the then Maintain Projects meeting, and agreed to take it to the Tsc.
07:14:43 But I can. I can present it to the details on Monday.
07:14:48 Yeah, cause I mean i'm just going by what I know about Catherine.
07:14:54 She would not as chair I don't think she would let this go to a vote without first being run past the ptls for comment.
07:15:06 Okay, I will put it on the agenda for Monday.
07:15:10 Then, Tsc. members, do you? Does anyone agree with my assessment of the situation?
07:15:22 No, I think it would be the best way. Okay, Amy gives it a plus one.
07:15:29 Okay, all right, and we already discussed the waiver at the bottom.
07:15:39 There. Oh, yeah, there was another note that catherine ad edge she's concerned about the Jakarta release key updates.
07:15:50 This is in the tasks assigned for release candidate, milestone.
07:15:59 Next week, and she said that the no information has yet been uploaded to the key updates page from subcommittees or the use cases.
07:16:15 So if you're a use case owner or you are on one of our subcommittees, please visit that page and update it with you know your activities and accomplishments in the the Chicago release unless there are
07:16:39 any questions. That's it for me. kenny Okay, thanks, David.
07:16:48 So just just on the see just wanted to ask for people.
07:16:56 I just wanted to maybe sound of no precaution we've had a lot of problems.
07:17:04 The last week with infrastructure. Firstly, we had this really Db.
07:17:11 Issue, which means that nobody can build I think it's resolved today.
07:17:16 Now, but up to now nobody's been able to build an or an owm release, I know when lab either locally or in the you and hitch because of the because of the red Db.
07:17:31 Issue. So that means that no pairwise testing has been done at all.
07:17:35 Yes, in most certainly not for the policy we can't do it because we can't get owe him up also.
07:17:41 Then Jenkins was down in. Well, Jenkins was stacking all bills and failures for the last, I think, for a period of 1 one and a half days there, and now I am.
07:17:53 I I was on. I was on time off from Friday.
07:17:58 That international security this week. But looking at it now, I personally in the public framework, anyway, I don't think just as any chance I was making or see.
07:18:09 Next week. I was just talking to one or 2 other pts as well.
07:18:11 I think they I Don't want to support another smells. but i'll be interested in hearing what other 200. what other people think about next Thursday from ptl point of view Think one information is about these
07:18:30 this failing jobs in the verification. I think that was related to issues we have with the helm linting of 3 helm, 3.6.
07:18:44 I think that's a stick snap yeah and I think this is but this is more an issue on the let's say job configuration.
07:18:50 I think it patches. I think ongoing but I don't know when it will be fixed.
07:18:55 So at the moment, from the O. M. team perspective, we are reviewing the the or really having a closer look on the on the patches which we which we which are in the pipeline and need to be
07:19:12 merged, and we are trying to do that. really looking in details.
07:19:17 So this this, if it's just this one failing a job, basically. But, for example, the end-to-end health checks. and to end tests are fine from our perspective, we are trying to to merge them as soon as we can you
07:19:36 know. Okay, of the Oh, yeah, yeah, I I know everyone's doing their best.
07:19:41 And it it. but it's just I think I think the talk is going to be just on on this.
07:19:47 Yeah, I see It'll probably take another week or even 2 and just to get all the o in reviews.
07:19:51 True. You know anybody else is just me or no, I agree with you.
07:20:00 Oh, and backlog is, is going to cause an issue with next Thursday.
07:20:05 I would very safely soon, which i'm more closely with Lf.
07:20:13 Guys to try and get touch out fixed. And okay, Well, my suggestion is that we review status again on Monday in the Ptl meeting and decide on a on a recommendation for the Tsc.
07:20:38 Yes, yeah, with the peer-wise, testing is one of the requirements for or c.
07:20:49 So just to be aware that it's yeah just say that I I think the amount of china's left won't be enough.
07:20:57 Okay, Okay, look. Thanks for raising the issue there. Linen.
07:21:12 Thank you. Okay. Just then, popping back to the issue here with Gpl.
07:21:30 3. so I guess this will be a request for an exception from a waiver for the the release to the Tsc.
07:21:41 Next week. So Jenny, I found that email in my you won't.
07:21:59 But you wanted a link on the website right yeah from the group's I O Link.
07:22:07 Yeah, and it's not it's not by and date that that email was approved.
07:22:14 But I guess I had to find the date of the original friend.
07:22:17 Let me do that because I get email of day goes on April the seventh, and let me let me find.
07:22:26 But but you're right I think the question is to for the exception, which seems to make the most sense.
07:22:45 There was no colonel from March thirtieth.
07:22:56 The exception request paperwork's been filled out I believe so.
07:23:13 So so I see the original email. but krishna's response went to own app That's Tsc.
07:23:20 But it's the most not on that on the website the list of messages on the website on the Web Portal.
07:23:28 I don't know why. you know what let me forward the email to you, at least so that in Uscc on it, Kenny.
07:23:37 But I I don't know why it's not showing up there. So I'm: i'm going to forward this now.
07:23:45 An email. If, yeah, if you could just forward it back to the Tsc.
07:23:49 List. that's probably the safest thing to do Oh, okay, okay,
07:23:58 I guess we will go ahead and move on from that Then i'll cut and paste that in once.
07:24:08 It pops in my inbox, and I got the link moving on to real Lynch.
07:24:17 I am very pleased to introduce Matt Watkins, who is our new Eu release? engineer?
07:24:27 I know there's going to be a round of applause for that.
07:24:32 Matt, You want to take a minute or 2 to introduce yourself.
07:24:35 Yeah, thanks, Kenny. I appreciate that. yes. So my name is Matt Watkins.
07:24:41 I joined the next foundation just 2 weeks ago. still very much finding my way around, making sure I got access to all systems and learning the ropes.
07:24:52 Very pleased to be here i've got over 20 years experience in the it industry.
07:24:58 Earlier in my career, primarily networking later more system administration and some build and devops stuff i'm kind of new to large-scale software development that is obviously the bread and butter for the Linux foundation and the projects we host But I'm very
07:25:12 much looking forward to getting some to know you all, and obviously as a higher here in Europe.
07:25:18 I think this project and a number of others have been crying out for additional help and attention.
07:25:23 In this time zone and that's what i'm here to do so.
07:25:26 Bear with me while I get up to speed and i'd like to meet you on one-to-one basis.
07:25:33 As we as we get down the tracks. So thank you for the introduction.
07:25:35 K. appreciate it. very happy to have you here with that moving on I don't think there are currently any show stoppers that i'm aware of.
07:25:57 Didn't see anything where we're specifically waiting on the community.
07:26:03 There was some sort of emergency Jira update yesterday.
07:26:11 I think anyone we a comment on that, I think, was a pretty issue. I think that was a major vulnerability.
07:26:18 And Gera that we had to engage in a fairly urgent round of patching.
07:26:23 I know that my colleague vanessa was very busy last night.
07:26:27 So yeah, there's a number of systems that needed to be updated as a result of that.
07:26:37 In fact, I think it was all hands on deck as fast as saying, Okay,
07:26:54 Would that have had any no Gera wouldn't have had any ripple effects on on Jenkins jobs or anything like that? that would have been more at the commit level.
07:27:07 So. No. yeah, as I think through it, I was like is a dumb statement.
07:27:12 Okay, anything else. Brilliant related i'm not sure if it's worth mentioning.
07:27:23 Anything related to the Q cow 2 images, and I think the banks might be on this call.
07:27:29 Do we want the same thing about this and some of the challenges we found around that I only know what that we have had lots of challenges. That kind of kill the whole system from vex point of view. when we're trying to get
07:27:44 rid of. go away from the Q. Rov. form of but we're still having some issues with it.
07:27:50 Yeah, I think that's been an underlying problem with some some images, some images that are being built We might be quite sure what it's being introduced for. but it may be upstream images coming in in a format that puts
07:28:04 extra stress and strain on the openstack infrastructure at vex host which runs the Jenkins and Garrett environments for own app.
07:28:13 Well, I think we're still digging into it but it could be that actually something happening upstream of us.
07:28:19 But it has caused that. There was a problem. with Jobs getting backlogged last week, and the root cause was essentially that the openstack infrastructure of vex.
07:28:29 It's no longer hanging the ip addresses to the end. So basically it's overloaded, and that meant we're spinning out lots of Vms to clear the backlog of jobs.
07:28:35 And they were basically hum and frozen. So we're aware of what the underlying issue is.
07:28:39 How this end up Getting into the machine builds the Vm.
07:28:43 Images is some yet to be determined. but there's a customer ongoing work in that area that we're looking at behind scenes.
07:28:52 Okay, Unsure not. Why unsure where issue is being injected?
07:29:31 Shankar. Thank you. Okay, Those should probably be probably be cloned under there.
07:30:06 Okay. Thanks for the clarity on that. It sounds like this.
07:30:12 Might get back to the to the issues that you were talking about Liam I'm.
07:30:21 Guessing. assuming cosmic, Ester: Okay, moving on. then the moss.
07:30:33 Are you online? Yes, yes, I am. okay. So first let me give some comments on the upcoming Shakanta release.
07:30:44 So. I really asked the teams to create their branches as you saw set like for the mail that a lot of projects have not created.
07:31:01 The branches. I know that this is part of the Rc.
07:31:05 But if they do it earlier, i'm quite happy and then also a comment to follow is a procedure that we have provided in the Wiki.
07:31:18 I can share the link to it. That procedure describes the all the important steps to create documentation. for as a for the upcoming release, and especially creating the branch and very important change configuration files in the
07:31:43 new branch. and this is better, because only changing files once in the branch, and maybe also do a slide change to an Rsd file. in this new branch.
07:31:58 2 will create the documentation in in orthodox.
07:32:02 Otherwise, if you only create a branch, the documentation does not show up and read the docs.
07:32:09 But please go through the procedure, and it takes takes a while to load this page because it has a some mark horse in it.
07:32:20 That show source code. So okay, we are so it's quite comprehensive.
07:32:27 I really like to ask for feedback on it. It describes what you need to do in the master branch, and and also in the new branch.
07:32:40 Change the configuration files, change your main documentation, and also take care about always about about the latest version of configuration files.
07:32:52 We are now current. We are now providing, because we have a lot of changes or not a lot. But we have major changes in configuration fights, for example, in the requirements.
07:33:10 Docs dot text, which is important to to update also in your project to create proper documentation.
07:33:15 Otherwise you we will end up in not good looking or no documentation at all.
07:33:25 So please, please, please go through it and branch as early as possible, because branching at Rc.
07:33:33 Is a hard thing for the documentation team because that's not coming to the other point.
07:33:42 The documentation team is quite, quite low, very, very low on resources.
07:33:46 So Eric is supporting Andreas, supporting and definitely Cedric Olivia supporting which is the great.
07:33:57 But they have a lot of other priorities so it's often a very hard time to reach out to them, and to to ask for a review and submit at least or only smaller patches.
07:34:15 So it's sometimes more work to reach out to people to submit or review than to create this patch.
07:34:21 So that it's the reason why i'm asking for yeah to to remove, if possible.
07:34:31 They they self-submit and self review checks for the documentation project.
07:34:38 I'm not asking for as a zoo committer rights. but if this is the only way we can solve this issue here.
07:34:47 Maybe then it's okay to have The super commuter rights, but I definitely do not need it.
07:34:54 But I need a more need. The the possibility to also do changes in the documentation ripple by myself.
07:35:06 Otherwise. yeah, it i'm blocked a lot of times yeah, and that's yeah.
07:35:13 This is some somehow also, sometimes a little bit frustrating so I'm not blaming the team.
07:35:20 The team is doing a hell of a job, and they are doing whatever is possible.
07:35:25 But, as I said, they have sometimes other priorities. And yeah, I really like to ask that the Tsc.
07:35:36 Are not sure who can decide on it to remove the self, submit and save review rules in in.
07:35:48 But is it in in the system for for the documentation project?
07:35:54 Yeah. Okay. So for challenge folks just check my understanding here.
07:36:05 The self-commit rules are at the global Jjb level.
07:36:09 Correct. Correct? Hi: Jess. Okay, And so not not on a on a per project.
07:36:20 So the that sounds like the proper course of action here is, is probably super committed.
07:36:26 What would be your guy's perspective on that super commuter will be best. I know that we have several people in the Super committer list, including myself. so I can definitely help and others.
07:36:41 Yeah, but if I read it, that would be the cleanest way.
07:36:44 But if I read it correctly, so, a catherine wrote this morning a mail, and it includes also some documentation that means, even with supercomputer, you need a second person to look to review and do things and
07:37:02 that's a that's the main issue there are there are of that many, many people that can do this. And yeah, So if one other person so as long as whoever is approving, your change is different from the outdoor you only need
07:37:26 one person that approves your change you shouldn't need more than one person.
07:37:33 Yeah, and this is what i'm asking for to remove and what the problem is.
07:37:40 I think that go ahead. No, I think what you, what what? what? what what is mentioned is that I think the problem is, it cannot be removed as it is on a global level.
07:37:53 Right this rule. Yeah, only only the only possibility would be to either. Give Thomas the supercomputer rights to do it by himself, so that it's not he's not affected Maybe on that.
07:38:07 But I'm not sure if supercomputer would be able to to sign its own changes.
07:38:12 No, no, they they would, even if they are possible. Okay, yeah.
07:38:17 Then I then then Super Comato will not help. Yeah, no. but I mean there are several super commuters that can help you out.
07:38:26 So as long as another super commuter approves your change.
07:38:32 And, for example, if you push your change and I I can approve it, and I can merge it.
07:38:37 Yeah, do we? We We don't have a super committer list. I think we did in the Wiki somewhere somewhere in the Wiki, but I don't recall many people.
07:38:53 The only people that I recall were there was Morgan myself, and I honestly cannot recall.
07:38:58 But there is somewhere in the in the Wiki. Okay, can can somebody take and action?
07:39:09 Item. Yeah, but then send some. but somebody in real end what what i'm proposing you know.
07:39:17 Let me flesh this out here, what i'm proposing is is that we create a mailing list the super committers.
07:39:27 And so when help is needed, an email can go to that list rather than one that just goes out into the look guys, Thank you.
07:39:44 That's modified by me. Oh, okay, you think that Guy would might know something.
07:39:51 Yeah, there we go. Maybe we should set up a set up a mailing list, actually.
07:39:59 So when something is needed, an email can be sent to that mailing list.
07:40:06 Does. That makes sense to folks expect this happen often if if it goes to the end of the release.
07:40:20 So. But then then it would also be only okay, if I at Morgan, Lukash, Jess eric bin or Kannash to the list of reviewers. or, Yeah, that's actually the best way because we will get an
07:40:41 email of your review request. So yes, I think that is a good idea.
07:40:46 So, but that that means that I do not need this super commuter rights, because I can add those people here in the small list, anyway.
07:40:57 And But yeah, it would be good to to let them know what what resource issues we have, and that they understand why they are now should react on a change in documentation, right correct.
07:41:18 So, looking at this list, we know that morgan is rolling off the project, or has rolled off the project so that doesn't help us much.
07:41:33 Also know that oftentimes kind of garage is unavailable.
07:41:42 So we might want to look at how how we're we've got this stuff distributed from, and and administrative overhead.
07:42:04 Perspective. How often, Thomas, do you think this will? You will be sending out requests for super committer assistance?
07:42:17 I think. and in the in the weeks before I release, quite often, several times a week, maybe sometimes several times a day, or depending on on yeah, the changes we are doing slides slide changes even requires us.
07:42:38 Then yeah, So so based upon that. And and I know that the right thing here is that the people should be added as reviewers.
07:42:54 But I think that is going to introduce a lot of additional overhead for Tomas which is why I was thinking making a mailing list instead.
07:43:14 Thoughts on that from folks that are on the super committer list.
07:43:18 So on the call. I think we've got jess obviously you Lukash.
07:43:25 Obviously you're you're here and then you're on the line.
07:43:41 Well, if this is just merging and that's not a vacation right?
07:43:45 Yeah, i'm just i'm i'm just thinking of when to Masas having to go through as we get close to a release, and and all this stuff is is coming in having to go every time he has one of these and
07:44:01 add everybody as the committer versus. just sending a mail to mailing list, saying, Hey, I've got this merge needs to be committed.
07:44:13 Please help. I think that there's a garrett native group. so in that case he probably can just add the group, and the group will add all the the commuters.
07:44:31 Okay, that that's that's a much better solution. Yeah.
07:44:34 But the middle is also a good idea i'm in favor of either.
07:44:41 No, I think I I think the proper course of action there if there's a group that can be added as a reviewer.
07:44:49 That should be that that would be the right thing to do i'll take you to access. Then i'll email Thomas, and let him know which is that and make make sure there is a group that first of all yeah, because
07:45:04 in in terms of process and overhead you're already going to be in the thing.
07:45:09 If it's. just adding a single single group name that's that that's a lighter lift than than sending an email out to a list.
07:45:19 Yeah, I could check on that. But from the other hand, requesting supercomputer to march something to sort of an exceptional situation, right?
07:45:28 And in opposite. I received a bunch of males from garrett about the request and other things. so i'm afraid I will not notice that somebody's waiting for my review that's a special one Okay, Well, the best thing would be
07:45:53 to have more people contribute to documentation. So that is the right answer.
07:46:03 We immediately can and stop the discussion here. But please join the documentation team as a committer as a contributor.
07:46:13 Your support is required. Okay, so okay, But We would have an hour let's say an intermediate solution.
07:46:29 So whenever I'm or maybe eric is not answering fast enough, at least you have a possibility to try to to to check whether Ukraine or Jessica would help you I mean if I'm not at the place at the
07:46:45 moment. So I think that's anyway, a possibility so I think I hope that the taps for the time being, and hopefully,
07:46:54 As I said, I will be how fast enough to check it.
07:46:59 Okay, I I , Yeah. We also faced a program because I was.
07:47:05 I was a way for to to 2 weeks. but yes, I see.
07:47:10 Maybe a solution or so, if we can rely on some super commuters that accurately mistakes could be great.
07:47:16 But we need to update also this list and i'm not sure that they are the design.
07:47:22 I'm not sure it's valid no mind work So also, just to mention, if we are gonna go the super commuter route, we need to determine a start date on when we should enable the super committers and
07:47:38 an end date on when we should disable this super commuter.
07:47:41 So that is also part of the super commuter procedure.
07:47:45 So kenny, I don't know if we probably need a formal boat on, When should we enable and disable the supercomputers?
07:47:54 Because they say disable by default. Yeah, I thought we could set up kind of a standing thing that once we hit a certain point in the release cycle.
07:48:09 Am I, miss, remembering that no I think you're right might be mentioned in that wiki that we were looking earlier.
07:48:18 But yeah, I do remember that that we said at a certain point in the release we assume the super commuters should be enable. But I just wanted to double check.
07:48:26 So at Code freeze, so does not require a Tsc. vote.
07:48:35 So as soon as we hit code freeze which is 4 David I'm afraid that the cemetery that's correct.
07:48:57 I'm sorry It's M. 3 Okay, so I probably should just the winner.
07:49:09 Jc. ticket just to to track me the When was it requested, and when was it enable, etc.
07:49:18 Yeah. So from our from a release process, David, I think this would be your responsibility to open the the ticket to turn on super committers.
07:49:41 Ok, is there a template or No? Just yeah, you can just put that in the description and wish should know what to do.
07:49:55 Okay, all right, and we want to tie that to m 3.
07:49:57 I guess so. do we need that right now, yeah I think So all right, i'll take that action right because we're we're coming up on Rc: So we're already. there.
07:50:19 Right. Yeah, Yeah, I wasn't sure if something had already been done for Jakarta for that, or not.
07:50:28 So That's why I was asking Okay, it's it's still required for Jakarta.
07:50:34 Yeah, I can go ahead and do that? Okay, that means i'm beginning with what was it?
07:50:41 M 3 i'm i'm allowed to or super committers are allowed to commit also changes for the for documentation, and I can reach out by this list, and or maybe I can mail or add them to the to the to
07:51:08 the change, and and I also do not need any super commuter rights to do so.
07:51:14 Right right. I can contact you with a name of the group that you can add.
07:51:21 As a reviewer in your change. So you have to add in Google, Yeah, Okay, yeah. that would be great to have some support here from this list of people.
07:51:36 Just when you get the group. If you could just drop it into the chat window, plump it in the minutes, or if you want to plunk it into the minute yourself, you can do that.
07:51:45 Yep: Okay, good discussion on that. I think that we should probably move on.
07:52:01 I've got about over a half hour left in the call okay.
07:52:12 Let's talk about external api nbi repo So Andy did.
07:52:26 A merge like the gets us gets us there because the repo has been unlocked.
07:52:32 So what is what's needed next to hela yeah hi, Kenny!
07:52:45 So the now the changes are available in the master branch.
07:52:48 Right, so it needs to be included in the Jakata release.
07:52:51 So. so it needs some activities to be taken care of by the project team.
07:52:58 So like kind of releasing the image and adding the release version to the oem charts.
07:53:06 Those things needs to be done so that we might require support from Andy Mayor or Eric.
07:53:17 Yeah, but I think we i'm not sure but I think we first to program, you know, because as a project number 10, we i'm not sure how we can create a dedicated branch for that So we need to decide if
07:53:30 we create this branch, and after we need a yes, to have to create a new new imagine, to push it in the next year, then to have date Ohms, which maybe not complex.
07:53:44 But think we need to clarify the the global process in such such case because it's not.
07:53:52 We are in this French situation there. Oh, so currently the snapshot images are being built at it, maybe, for the release version.
07:54:03 I'm not sure what is the procedure and what we should have. Yes, we need.
07:54:10 We need to create a image to be pushing in the nexus.
07:54:17 Yeah can can be done for the matter. But after we need also to to update around with the name of the imager.
07:54:29 So that's that is not very complex but we have the question or so for the closer for the release.
07:54:41 It's do we do we want to create a checkout block for an Api, while you're protecting the moment enters 2.
07:54:49 That's a difficulty from 1 one comment on this issue Erik and Kenny David, and it's related to Yeah.
07:55:04 No, no, no. I just you know. and we just yeah Well, I I I heard the word image, and we need to mention our update.
07:55:15 The release version in the oem charts. Yeah. Yep.
07:55:26 I just while I was typing I heard the word image and that's what ended up on my fingertips.
07:55:34 Sorry. Thanks, Eric. Hello, Kenny! Can you hear me?
07:55:43 Yes, sir. So yeah, it was a mute so it's somewhat related, but good.
07:55:51 This is the note there that we are also looking for a solution.
07:55:56 So since i've seen some emails I talk to Aila and Kevin and as to so we can find a home for this report, and then we won't have this problem that it is not actively maintained But
07:56:09 I. I think we probably discussed that in maybe the next meeting after we get feedback.
07:56:22 And and I let you know if that yeah that's that's about a long-term solution right shankar, maybe for for a while, like for the short term solution.
07:56:31 Maybe like this, the things what are a type? I can write.
07:56:35 So those things needs to be taken care. Exactly. Yeah. Yeah. So we need to do that.
07:56:41 Okay, Yeah, yeah, correct. Okay. So the request, then, I guess, is specifically to you, Eric, for for the short term.
07:57:01 Is that something that you can do? Sorry so the the we've got the question of the branch which if we have made any updates, I would think that we would need a branch pulled
07:57:26 I am, but also we need I mean we yeah we got to be careful, because if we we need to sort of check all the security, and so on in this component I don't know finds, Eric.
07:57:43 I don't, Eric, I thank the the commotion try to go ahead.
07:57:47 As it is, I mean, because it's I think the components in terms of security, is going to go out as it is because the it had been, I believe it had been removed from all of the Jenkins jobs so in terms of
07:58:02 security scanning for, you know, vulnerable packages.
07:58:06 We? Probably we Don't have anything and There were no tickets open, so nobody did anything with the repo is that that is my understanding of what happened here.
07:58:16 Kenny, Is that correct? that it was it had all been removed since it was unmaintained. and now it's being pulled back in as far as I know.
07:58:27 So there's yeah, you know it it was unmaintained for the for this release.
07:58:32 It was discovered late that we still needed it we are where we are with it, but somebody but going forward either this is gonna either the the project that requires it is going to need to find a replacement or they're going to have to adopt
07:58:49 it and be the ones to maintain it but that's the long-term solution.
07:58:56 I'm just focusing on short term we are where we are.
07:59:02 Yeah, yeah, I mean, like a long time solution. Yeah, we are discussing offline with the other project ptls.
07:59:10 But as Shankar set like, maybe we will discuss in the upcoming weeks.
07:59:15 But the the topic. What we are discussing is about the short-time solution Exactly.
07:59:20 But I was addressing something that that Eric was saying.
07:59:22 Because, Eric, I do agree with you. a 100% on.
07:59:26 Unfortunately, there's not a ton we can do at this point in terms of the security impacts on the release.
07:59:33 Okay, and which isn't a good place. to be but I think we just have to face reality.
07:59:42 Okay, So the answer, though, is we've got to have we've got to address this very, or we've got to start addressing this as soon as possible, so that we we aren't in the same position with cone okay maybe in that
08:00:10 case, Shankar. Maybe we need to rush up on the long term solution. I think we do.
08:00:20 I think the long-term solution is something we've got to come up with that solution.
08:00:25 I'd say within you know by the end of the by the end of May, otherwise otherwise we will be facing this again.
08:00:34 And, by the way, I'm not speaking as catherine right now, and speaking and behalf of Sitcom.
08:00:43 From this perspective, because eric's point eric's point about security is dead on Okay, Yeah. I hope something we'll get a better.
08:00:52 Answer, Yeah, I mean, we may create an image on the product in the in the next series.
08:01:04 But with all the wanting we may we may have about the fact that we don't check the security, and so on.
08:01:12 So it's it's up to the tsc to decide that.
08:01:32 Well, it sounds like we cannot do the release without without bringing external Api back, or without bringing this.
08:01:38 This repo back right correct that's my understanding otherwise we wouldn't have been doing this that's kind of what I was thinking.
08:01:56 If this was an academic exercise. I think we've just kind of missed the boat there.
08:02:05 So need, I mean believe, from a process perspective, a branch is needed right, and we need the the oem update.
08:02:26 And so that was the specific question to eric now if There's if there's no jenkins jobs doing anything.
08:02:38 How does this end up getting done? What needs to be done, I mean is, is, do, do, are there Jenkins jobs for inclusion in this release?
08:02:57 Are there Jenkins jobs that need to be created recreated or not release release versions?
08:03:12 I'm not sure, Kenny, but for the snapshot build.
08:03:17 What I have done is like in the ticket. I have asked them to enable the Jenkins job as well when they are reactivating.
08:03:24 The report so enabled the job Jenkins job as well.
08:03:30 So as a result, that we are getting the snapshot image.
08:03:33 But for a release version. Maybe the process i'm not aware yeah nor am I.
08:03:44 That's my question, Eddie. maybe you have any I don't remember how to present them.
08:03:59 Maybe I think we need to create a to define 2 and that one I wasn't sure about that, because I didn't do that in the past.
08:04:10 But maybe, Lucas, you can, or other people know how to
08:04:17 Do you need a release to create this freezing? You need to reduce Job.
08:04:21 Meter is rubbish Fine? Yeah. Yeah. So you need to create also this freeze job in the project.
08:04:33 One after 4 or M is quite easy, and to update, to improve that.
08:04:37 And so very simple on the police. the nbi code is still in the Olympics.
08:04:45 It's not a big issue. Okay, So what is being requested then, of the specific request to Eric is from from from the from the network slicing use case team.
08:05:20 The request is, Do the branch do the chart update and create the Jenkins job?
08:05:36 Yeah. think the job needs come first now. But but all 3 of those things. What?
08:05:46 The end-to-end network slicing team is asking Eric to do. Yeah.
08:05:56 But I i'm not able to I mean the creative job is not true.
08:06:03 I may I go to the that time we need to work, create?
08:06:06 I think what can I do personally yeah yeah no no no i's true to to no programmer, but for the jobs, and but sure that i'm the best one to do.
08:06:21 Yeah, i'm i'm i'm understanding that i'm trying to verify what the specific request is and if the specific request is to Eric to do that and eric's saying no because he's got a full
08:06:44 plate, not the right guy. And that's a very different request than just merging a commit who has the responsibility for creating that Jenkins job.
08:07:06 Can we just use the master, Joseph on this project?
08:07:11 Do we need to create a dedication? Yeah, my nut time, because the master once already exist.
08:07:23 So we don't have to do anything okay so i'm not sure.
08:07:31 The records are really made has been created yet. Okay, So So my point here, and the reason that i'm not moving on and i'm sticking here is because we keep just kicking the ball down the road.
08:07:55 I don't want to be every tsc meeting we have coming back into what's the next step for getting this done so?
08:08:10 So kenny that's that's exactly the problem we are trying to solve, and they didn't want to I'm waiting for some email responses to figure out if it if it can be part of some active project in which
08:08:24 case of these issues will be much simpler, okay, so So if you could next week.
08:08:32 Well, that's one next week we might have an answer but I would suggest, at least, if you could, we're on that bullet.
08:08:37 Can you just capture exactly what needs to be done right it's it might be just testament just because it's not your cut.
08:08:51 So the branch needs to be created. okay there's a bunch of stuff that's being cut and pasted into the chat when Sorry I just said, that's the link to the jacket jobs as liquid said, their master master jobs are there, already.
08:09:26 So Okay, thank you. I really suggest to one and 5 the project to then push changes to the master branch and then just release the image.
08:09:48 Okay, So there are some things that have not been so it's there's stuff that's still there and hasn't been removed.
08:10:03 Okay, Well, that's I guess good that we didn't clean all that up.
08:10:32 Okay, So I guess shankar there's your there's your list. Okay, so.
08:10:44 But can you? I can, if you want I kind of dead the ram, because I know It's not very complex for me to do it so I can.
08:10:50 Once the image is created, can do the omb data. Okay, thank you sir.
08:11:17 Okay, Well, i'll fix that later. we spent a lot of time here.
08:11:20 Okay, so we've got i'm gonna go ahead and move on.
08:11:25 We have several things on here. don't think that we're going to have time for all of these Magnus.
08:11:45 How time critical is the liaison statement now it's It's not time critical or something.
08:11:54 You know I needed to tell people so just wanted to make the sort of racial statement available.
08:12:03 I don't know the equality the uptake or the nor the the impact of this new focus group.
08:12:14 So I don't know I need to say anything more about that anyone who's interested in sort of test test bed federation can can have a look in and making an assessment whether they want to engage in this there is no
08:12:35 specific request from my ut here. it's just for information Okay, thanks.
08:12:47 Thank you so much. Probably my topic will take not longer than 3 min, I believe.
08:12:56 Go, sir. Thanks, Maybe it will be helpful if I can share a screen to Okay, Okay, just leave it in A. also how we are running tests.
08:13:14 Okay, we'll be granted. thanks Okay, are you able to see my screen.
08:13:25 Yes, sir, to run tests. we are using Github Ci.
08:13:30 And the project developed by Orange, the chain Ci, which is a part of the Orange open source.
08:13:38 Group in that project. We are running dailies and weeklies and gating tests.
08:13:44 We have also we also running Dt. and tests on the change.
08:13:48 Ci Fork on our internal Dt. Github.
08:13:54 Local instance, the idea is to create a subgroup on the on-up group of Github gone to run daily tests.
08:14:05 The University in New Hampshire lab, because we need to create Github runner on the University, New Hampshire Lab and integrate with it with an Github project.
08:14:24 So the idea is to create the subgroup here, the integration, subgroup and and create a fork of the Change Ci Project.
08:14:32 To be able to run test daily tests on the University, New Hampshire lab, and also weekly in the future.
08:14:42 And I believe also gating. And yeah, this is this is this is my idea.
08:14:45 And this is what I asked for and there's needed Dsc.
08:14:50 Decision is needed to create the subgroup here and I believe the integration commuter could be a maintainer's or developers, at least in that sub group.
08:15:09 That's all I wanted to share is there is there and so does do we?
08:15:16 As Tsc. need to approve this i'm absolutely positive for that I mean.
08:15:24 Yes, I got a response for Kenny for for a second. Yeah.
08:15:29 So the the the the issue here that the Tsc. had approved.
08:15:35 Oh, O. M. i'll do a pilot yeah get lab we can't be in an environment.
08:15:43 The point here is is we can't be an environment where we have a split, a split responsibility where some of the the the stuff is is being handled one way, and some of the stuff is being handled another way.
08:15:59 So the oam was a proved as a pilot, but that pilot was never put into use.
08:16:07 Hmm. So this would be a pile this would need to be a pilot, and if successful than the the the intent here would be that all of own app would move to get lab So that's the that's the critical piece of
08:16:30 this, Kenny, but we we don't plan okay, sorry, Yeah, Okay.
08:16:38 The technical issue of doing it is is is is a no-brainer.
08:16:42 It's it's more the long term support issue Yeah, but but, Kenny, I mean what what Mikhail is suggesting is just to put stuff which is already in github and only in Github and not
08:16:57 in Garrett for the end of the integration team.
08:17:01 To put this now in under the owner umbrella to let's say, have a separate one which is not in the orange open source. environment.
08:17:14 Let's say in in github but it is under own up you. So that means we don't have a conflict at the moment with with the with the projects we have in get it.
08:17:24 Yeah. So what what now? make? always suggesting? So they have not never been in?
08:17:29 Get it so far. What what me? How wants to let's say move at the moment to to get lap or in this gitlap folder or group?
08:17:40 Exactly as a remark. So yeah we Don't plan to move any repository from Garrett into Github mit ctl.
08:17:48 And we want to just tests on up tests running under the ownup group in on a github, because currently it's under orange.
08:17:57 And if we plan to run, new pipelines we I believe it's a good idea to run them under an on-up would say umbrella or group under on up group on a github.
08:18:11 It's already in Gitlab but on the other place on the Orange group, and we just wanted to run them the same on Github.
08:18:22 But on the on-up. Okay, so i'm going to punt the ball over to revenge folks.
08:18:33 What are your thoughts on this? We have we have work that is currently in?
08:18:42 Git lab outside of anything that we're doing in own app and the desire is to bring that work that is currently being done completely outside of own app into the own app gitlab Org.
08:19:06 How does that? What What are your perspectives on that internal support?
08:19:12 Profile going forward at this point, I will say no from my end, since the git lab we had was just a small pilot.
08:19:26 Nothing more than that, and at the end of that pilot they also admitted that they haven't tested everything on their end.
08:19:33 So it's remains a lot of things to be done before we can start using it.
08:19:37 If that's the decision we want to do Okay, So what We've got here account. what i'm gonna do is i'm gonna put this on the agenda for our staff meeting this afternoon.
08:20:09 To discuss it, because I I I I totally understand the request I see what's being asked.
08:20:23 I I just have to have a better understanding of that in terms of what it means to the Lf.
08:20:31 From a support standpoint. Does that make sense? Why did I give myself an action item?
08:20:48 Oh, you fool, Why do I do that? Okay. kind of garage or you online?
08:21:17 No funk historyo will be archived, circulated an email.
08:21:37 Find anyone having interest contributing no interest. so they want to mark Znfsdk funk test Repo as read-only
08:21:57 Hearing no response, Kenny, and you're not showing the agenda.
08:22:01 Oh, sorry, thanks, Magnus. i'm sorry about that so there it is request went out on to the discuss list on the tenth.
08:22:34 This is basically in information to the Tsc. that this is taking place.
08:22:43 I don't think from memory I don't think There's any action that is required on the part of the Tsc.
08:22:53 Since this is within a project, and not a whole project being archived.
08:23:04 So information only in that regard. Okay. Moving on, Oam Committer, we got about 5 min left.
08:23:16 Roughly. Oh, I am committed Magnus, and for car I think Faker can.
08:23:24 Yeah, I guess there was a question there's a question yesterday in relation to so there are a few of us still attending the O.
08:23:32 And weekly and kind of rotating, hosting the meeting. There was a question in relation to how we How do we promote new committers to the project without Ptl?
08:23:43 So yeah. Is there a formal process around that?
08:23:49 Or the yeah, they're yocto There's not a formal process around that but a a vote of the existing committers.
08:24:03 Can can simply do the trick I I can take a look. but I don't.
08:24:11 I don't think that there is since it is a vote of the committers.
08:24:14 Any committer can always nominate another committer to be promoted.
08:24:23 So in the absence of the Ptl conducting a a formal vote, the discussion could just take place.
08:24:30 Somebody else can feel in the form. Okay, Thanks. Okay. interns, interns interns. time to get your proposals in proposal guidelines same as last year.
08:25:04 Pretty much if you need to propose a new project, please do it.
08:25:10 There. the timeline I don't remember what the timeline is, I think I sent an email out on that.
08:25:22 If I didn't I will look but I don't want to go digging for it right now.
08:25:28 Anyways, if you have an interim proposal, please follow the link.
08:25:33 Go there, fill it out as ip community awards votes in progress.
08:25:43 We have the developer and testing Forum coming up in the Eu Portal portrait, June the thirteenth, through the sixteenth.
08:25:51 Please register for the event. please start putting your please start putting your Where's the link to the wiki?
08:26:13 Please go here. Look it over. add your topics. Start doing that so that we start building out the agenda.
08:26:25 The The program committee is starting to meet for that and kind of we need to get ramped back up to doing live events versus virtual events.
08:26:38 So please do that, and we've got to save the dates for the other stuff that's upcoming anything that I glazed over that somebody wants to dig down into more of or Kenny.
08:26:56 I just wanted to raise something from Catherine about the awards.
08:27:00 If you could scroll back down. Yeah, she just pointed out that apparently that they're one vote shy.
08:27:08 So people have been very slow to vote on this so we're shy in terms of the voting.
08:27:12 So this is really to encourage people to please vote because we're shy to actually be able to award any anything at this point, and as a reminder that's the only the tsc is voting on this so
08:27:30 please go in and and do the vote on on that. Thanks, Amy.
08:27:47 Oh, yeah, the other thing is I sent for the community's knowledge the next update on app update to the governing board is coming up on May sixteenth.
08:28:07 The template has been distributed to all of the Tsc.
08:28:10 Private lists, so that we did not spam 17 gazillion people with a Powerpoint template.
08:28:19 That they may or may not care about the expectation is that any discussions around. that will all take place in the public lists, and that's there.
08:28:32 So work needs to be started on that. this is the communities opportunity to share with the governing board what is working?
08:28:42 What is not working, what the community is accomplished. and help.
08:28:49 That is needed from from the governing board, so before this has been done. once a year following last year's presentation in October.
08:29:02 The board expressed a desire to have it done twice annually.