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 

07:00:13 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
07:00:19 From SaiSeshu (Huawei) to Everyone:
#info Seshu, huawei
07:01:06 From Srini Addepalli (Intel) to Everyone:
#info Srini Addepalli, Intel
07:01:09 From Jason Hunt to Everyone:
#info Jason Hunt, IBM
07:01:18 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
07:01:31 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
07:01:34 From Yuanhong Deng (China Mobile) to Everyone:
#info Yuanhong Deng, China Mobile
07:02:05 From Fernando (Fred) Oliveira to Everyone:
#info Fred Oliveira, Verizon
07:02:16 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
07:02:57 From Jorge Hernandez to Everyone:
#info proxy Jorge Hernandez, AT&T
07:03:07 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
07:03:43 From Catherine Lefevre to Everyone:
#att, catherine lefèvre
07:03:56 From Morgan Richomme (Proxy Eric Debeau) to Everyone:
#info Morgan Richomme (proxy Eric Debeau)
07:06:07 From Ciaran Johnston (Ericsson) to Everyone:
#info Ciaran Johnston, Ericsson
07:06:58 From Martin Vezeau (Bell Canada) to Everyone:
#info Martin Vezeau, Bell Canada
07:11:01 From Catherine Lefevre to Everyone:
thanks Morgan - that's great !
07:27:27 From Morgan Richomme (Proxy Eric Debeau) to Everyone:
https://gitlab.com/onap
07:39:00 From Catherine Lefevre to Everyone:
last discussion on https://wiki.onap.org/display/Meetings/TSC+2021-07-08
07:48:30 From Krzysztof Opasiak to Everyone:
https://gerrit.onap.org/r/admin/groups/a5a6dac2b013ab522d52f1e7e6d74d7a4fc93c59
07:53:13 From Srini Addepalli (Intel) to Everyone:
https://docs.gitlab.com/ee/user/permissions.html lists down the roles and permissions. I guess we just need to ensure that only patches from signed CCLA members get merged.
07:53:30 From Catherine Lefevre to Everyone:
thanks Srir
07:54:12 From Catherine Lefevre to Everyone:
agreed but we need to have a mechanisl in place
07:54:18 From Catherine Lefevre to Everyone:
there is none today
07:57:20 From Srini Addepalli (Intel) to Everyone:
Agreed. Also, it is good if somebody can map roles (Guest, Reporter, Developers, maintainer, owner) to LF roles. And process to be defined when a member gets the role.
07:57:35 From Catherine Lefevre to Everyone:
+1 Srini
07:58:34 From Krzysztof Opasiak to Everyone:
@Srini that would be awesome but it's not something that we could do on our own as OOM team as we don't have access to LF IAM
07:59:09 From Krzysztof Opasiak to Everyone:
also not everyone already has an account in gitlab so this mapping is not that easy at this point
07:59:27 From Srini Addepalli (Intel) to Everyone:
I am hoping that LF provides this mapping guidance for discussion :-)
08:00:57 From Srini Addepalli (Intel) to Everyone:
Sorry. Need to drop for another meeting.
08:17:12 From Krzysztof Opasiak to Everyone:
IT-22708 - IT ticket for scancode.io resources
08:17:20 From Kenny PAUL (LFN) to Everyone:
thanks.
08:19:12 From Catherine Lefevre to Everyone:
Thanks Seccom & Fabien for the proposal !!
08:30:15 From Catherine Lefevre to Everyone:
thanks for IT ticket #
08:31:57 From Catherine Lefevre to Everyone:
I am sorry I need to drop
08:33:15 From Kenny PAUL (LFN) to Everyone:
you audio is dropping Seshu
08:33:27 From Morgan Richomme (Proxy Eric Debeau) to Everyone:
I need to drop
08:38:41 From SaiSeshu (Huawei) to Everyone:
I need to drop...

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:05:21 Okay recording has been started.
07:05:24 Transcript has been started.
07:05:29 Everybody's muted when you come in please keep yourself muted unless you're speaking.
07:05:34 If you are on a cell phone you can use star six to unmute yourself if you are muted. And if you send me a private chat message. I will simply cut and paste that into the meeting minutes and it will become part of the public record so please be aware.
07:05:53 As usual, what we will always start off all of our meetings with our anti trust policy. You can find this link from the lF and all of the project websites policies important where we've got potential industry competitors, participating in these meetings.
07:06:08 Please review if you have any questions please contact your company's legal counsel, members of the lF may also contact Andrew up to grow the firm Gizmo up Grove LLP, which provides legal counsel to the lF.
07:06:23 Erin. See you came in. Thank you.
07:06:30 Okay, so share screen, this one.
07:06:39 Talk a little bit
07:06:42 about release David's out.
07:06:45 But bathroom we'll cover that for a little bit.
07:06:50 Talk about anything relevant related
07:06:56 food quality improvement proposal
07:07:03 update on enterprise awards and
07:07:09 upcoming events anything else anyone wants to add.
07:07:15 Martin Thank you.
07:07:25 Okay, we've got the maintenance policy here let's open that
07:07:40 all of the necessary artifacts have been released on our end.
07:07:49 So, regression tests, and everything else coming up then.
07:08:01 Integration team any, any comments on that or just that's what's next in the pipe.
07:08:11 No, I think we will restart.
07:08:14 They do know to do, which will include to the recent change, and checks at the there's no regression. So unfortunately over the last 10 days was not possible because we've got a major outage in our Dc.
07:08:28 So I think the DC was in in PTO as well so it took you a few days to understand realism, root cause of the issue but it seems to be okay. At the moment, daily master is just running the test so it was able to go up to the test, power, so I will relaunch
07:08:50 daily oh no no it does not mean that I will lunch every day, it would just do a one shot ear, because we still have some some issue with some resources as our disease used by on a button on not only on our.
07:09:06 Some, some.
07:09:07 Yeah, we do not have enough resources regarding whether what has been required by some projects so we need to clarify it and uncertainties are lots of people that are not there so it's not easy.
07:09:18 So I just run a one shot.
07:09:21 One shot, and I will see what other version of policy, and to be sure that one that Yoga is expecting.
07:09:30 And of course we expect that the results are as good as, usually on this so new branch. Just as a reminder when we run a nun Rutelli we always run the end of branch from Obama.
07:09:44 So if he has been merged in alignment, everything is ready, which is what we mean from from integration perspective. So I said what Jim and on junkie.
07:10:06 If it's in om if there's a new version of the Docker, then it should be part of the supply chain, and then the automatic test you should be able to give the evidence that everything is fine. So I would just trigger a run, and and give back, give some
07:10:25 to the TTC after that.
07:10:43 Okay, if no questions, we'll move on to assemble.
07:10:49 We've got RM three coming up on the 26th of the month.
07:11:02 We've got commitments from multi cloud.
07:11:20 And Seelye for global requirements and best practices,
07:11:14 made pretty good progress on
07:11:20 integration blockers.
07:11:32 Yeah on this aspect it's. We got a meeting yesterday was integration team. So I'm just back from vacation as I say it was mainly dealing with hardware with h in you know DC so I didn't dive very deeply into the issues.
07:11:47 But I think the page is not. I mean, one of the patches very old, and I'm not sure the filter are very good for sure we have this stability discussion that is in the pipe for quite a long time.
07:12:07 But yeah, this is a in progress that it can be blocking but it's more on Honolulu I think that from test we do what we need to do is checks that we really have a Delta on that we start getting some code.
07:12:23 According to the last daily master I observed in DT labs are in the gating.
07:12:31 It looks reasonably stable but I'm pretty sure that the code is not very different from what we have in Honolulu so far. So, I'm not sure that the blocking point today the blocking point that sort of structural blocking point that we address with a waiver
07:12:47 for the security issue so we still have some parts in in wrote with. So that's something we are used to do but that's more we exclude things that's know really change of code.
07:12:56 And there was a question on the GPM v3 issue raised by AI project so I know that Alexander was dealing with Search API v3 shoes answered that. So as I still some misunderstanding on what has to be done by the project.
07:13:16 So, assuming that we don't want you to v3, we must remove some library and we are not sure that this library I really use or not, if they are used and there's a problem and we have to, kind of, complete the let them choose then probably we can, we can
07:13:33 we can remove them that adoption of the baseline image with fixed most of the problem but we know that for a long time it's very hard to to to move to this to this baseline images.
07:13:44 And, yeah, regarding the blocker for the moment.
07:13:48 So, then threes plan for the end of August. As you bear v3 and now Japan.
07:13:53 She will be three here, what. Yeah, sorry.
07:13:57 So, Yeah, I did have time to read.
07:14:02 I think we have daily master which is the sort of stumbled candidate, according to what I saw, especially thanks to feedback from DT lab. I think it, it's okay that one more time.
07:14:17 I think this is tumbled candidate is very close to the current or no do not freeze. So I'm not sure we have lots of difference in terms of code so that's why it's not surprising that we have blocking things, blocking same usually cure when we start integrating
07:14:33 the current is a project. The only thing I can see is a huge work and DCA.
07:14:40 There are lots of patches but I say I do not have enough feedback to be accurate on the topic I know that a lot of work. I'm not sure it's match so that's why probably there's no problem.
07:14:50 but.
07:14:54 Additionally, tell you we need an integration BTL to to to watch us all these issues, or to consolidate the status of the standard. But clearly, Quran blocker page.
07:15:06 It's maybe a little bit misleading So, take it with care and don't take everything for granted. It's maybe find because there's not lots of changes.
07:15:18 So the, you'd mentioned the existing filters might need to be fixed.
07:15:23 I don't know, I didn't check, but maybe we need to review that I'm a bit surprised regarding the, the different issues we have but maybe it's normally just because there's not some issue.
07:15:39 I just wanted to mention that there's about the DC patches that you put there.
07:15:46 So there's a lot of DC patches that are coming to LA and we are constantly reviewing merging them.
07:15:53 But it's important to know that many of those charts that VC is adding, they are not deployed.
07:16:01 So they're not deployed engaging but by by default right. Many of them are deployed on demand by the user and I believe that we do not have scenarios that require deploying them so when the team will start testing we may see new issues arise.
07:16:24 Okay, good, good, I understand the better now because I saw lots of huge pitches and it was still ok so i was expecting failure, to be honest.
07:16:34 And that's because probably as this part is not fully covered by the test today. Okay. Yeah, it's only compile test I would say.
07:16:44 Regarding master just also to mention, Christopher, so we changed.
07:16:50 Today. Today there's only one gate because it seems that one of the two Aisha Gator is systematically fading, or at least the results are very not good and it's very slow.
07:17:00 So, what I suggest is to disable, at least to remove it from the pool to re install, because it also gates seems to be better. So I removed the gate so second lap from the pool.
07:17:24 it means that today we have only one lab for the gate. Just to mention, if that's fine. It wouldn't be possible for you to trigger theory installation of that game because Sylvia link but it turns out, they do not have permissions to trigger you there
07:17:35 for sure I do, I will do that I just wait for the end of the last processing and escape, even if everything is fading. I just want to finalize this pipeline on once the pipeline is finalized, I will trigger installation.
07:17:50 Awesome. Thank you very much.
07:18:02 Thanks, Morgana Christoph.
07:18:13 So, the milestone status
07:18:21 is a bit concerning for him three,
07:18:28 because we've got
07:18:37 quite a few things unresolved yet.
07:18:48 and.
07:18:52 Looks like we're okay with regards to the requirements
07:19:03 for em three but as far as the project status.
07:19:11 We've got.
07:19:14 It seems like we've got a long way to go.
07:19:23 Are we going to be able to close these out by the 26.
07:19:38 That's an important question because
07:19:42 I mean we, we have a long period to finalize this milestone three since my son to was concluded.
07:20:02 A couple of weeks ago before the vacation, we understand that people to vacation in July might take a vacation in August.
07:20:00 The lake was set in agreement with everybody. And since we will be very strict this time.
07:20:08 We would like to understand and that will be a topic for the meeting on Monday with a PDF.
07:20:14 If they feel, or idea of any risk already that they will not complete everything on time.
07:20:24 We know that a lot of things usually happen the day before.
07:20:29 But we, we would like to have a taste, about the concern the challenge that the team is facing to meet the deadline, which is in exactly in two weeks time frame so it will be divinity of topics on Monday.
07:20:46 To start to understand.
07:20:47 If there is an issue stopper. For many projecting.
07:20:59 Any other feedback comments from anybody.
07:21:12 I believe we can move to the next topic Guinea, then maybe just one.
07:21:19 I think I'm just coming for integration for example I know that three free stuff is in progress. one is about a license.
07:21:28 Did we received.
07:21:32 Just came from Steve we slow this time because I didn't see that in my mail on usually this JIRA is based on the analysis of the scanner. So I was just wondering if I'm, I'm wrong in my in my stuffer.
07:21:51 Do you know if.
07:21:51 lf it scan has been has been already shared.
07:22:07 Yeah, no, I don't believe it's been wrong Oh, let me ping him on that I'll take an action item.
07:22:08 Yeah phase one is review license scan. So it's the static review lessons can we agree. Okay, it is a one that usually we is based on under made from Steve.
07:22:17 Okay, because we know that he considers a dynamic license scan, everybody's wrong but we will not be able to fix everything for the ready. So, okay, this one just if you can, yeah, reminded me on contacting Kenny, because I was not able to close it until
07:22:34 I got this notification.
07:22:37 So he found it in end of June. Yep, that's the last one I see.
07:22:43 Yeah, he was discussing with some team members about the liquid base core.
07:22:49 They be known in July, but the last one was end of June. So, I believe we should add maybe an updated one.
07:22:59 based on what has been added in July.
07:23:20 Any other comments, feedback from the team.
07:23:30 Let's move on.
07:23:36 Okay so moving on to release engineering.
07:23:45 Jess, do you have anything.
07:23:49 No nothing from my side. Thank you.
07:23:54 Anyone have anything for Jess.
07:23:57 Yeah, there was the issue of migrating over to Key Club. And is there any update on where we stand on that.
07:24:07 We haven't heard anything regarding the UCLA, to be quite honest, we're still under an impression.
07:24:15 It's due for the end of August, I will know. So, that was, that was the error that or the misunderstanding that we got corrected just so sorry, sorry to hop in the end of the date that I had been talking about.
07:24:34 That was the date that I got from the team, but that's code that's the code complete date.
07:24:40 Not the release date so they still have to run all of the regression checks they need to run all the testing and everything else that goes along with it and get the documentation out there.
07:24:52 So it's looking at the end of September for the, for that.
07:24:57 My understanding is that it may have been set up to.
07:25:06 It may be
07:25:10 copied there I know that there was an issue with trying to get the own app own app.org domain name back because that had been somebody was sitting on that I don't I don't know who.
07:25:27 But my understanding from Trevor Bramwell was we got that back.
07:25:34 And then,
07:25:34 or not from Trevor from Andy Greenberg we got that back. And then, I think, and I will verify and verify this just maybe you can verify it, that the the sink is in place.
07:25:51 Currently, that fact I needed, I need to double check on.
07:25:59 Yeah, so they it recently I was made owner of that name space.
07:26:06 So, Trevor is owner as well. But yeah, we cannot do much, unless is UCLA is completed.
07:26:17 You know, if, if the GitHub repos have been populated at this point.
07:26:25 And no I haven't checked.
07:26:32 Let's see here if we can find out.
07:26:43 No, that was.
07:26:45 That's an old link.
07:26:47 Yeah, it's just a.
07:26:56 It's just slash honor.
07:27:07 How's it coming up with CNC F.
07:27:12 Yeah, let me, let me, let me check on that I received the email that I was made an owner. Let me see.
07:27:20 Oh no I own app would show up there.
07:27:24 I think that that year, you've been looking for that information in the web page about each app itself not not that the inside list of repose remove the about from the link.
07:27:44 I put the link in the chat.
07:27:43 Oh, yeah, that's what I did.
07:27:56 Okay, so it seems that that we have our organization on geek labs.
07:28:02 Is there anything that prevents us from migrating beyond repost here.
07:28:07 The that we do we need to wait for it is LA for also for also that right.
07:28:18 Well there there's, there's two pieces of it first we need to put the sink in.
07:28:24 So that the the repo gets populated. But we can't change any of the tooling over to us get lab until CC, until easy CE, and, and, and, and,
07:28:46 and believe me someplace. Yes, thank you.
07:28:51 And what does it mean for for stupid guy like me that is here ladies in place. Is it some process or two because in Frank Gehry perspective, that was just, you know, attract books on my account.
07:29:07 Yeah, and similar tooling needs to be put in place.
07:29:12 So, Derek was integrated with easy CLA as his GitHub.
07:29:20 So those two things were some of the first deliverables so moving to get lad putting the integration for get lab to support the CLA that's what's. That's what's in the works right now.
07:29:36 So you won't be able to commit to get loud until that's in place.
07:29:42 Is that NLFY dishes so no project can have a CLA.
07:29:47 If it's using good land, right, correct, that is that is that is across the entire entirety of the Linux Foundation.
07:29:59 There it is supported currently GitHub supported currently get lab is not.
07:30:06 And that's what's in going in and a kit is the first project that will be using get lab.
07:30:14 Yeah, there are a few others in your pipeline and closed one of them. Yeah, and and and will probably be second.
07:30:24 See if there are some timeline for that migration and info for adding the support for geek lab to UCLA, yes, code complete for that is expected to be the end of this month.
07:30:36 And then the release of it is expected to be the end of September.
07:30:46 So the date that I had been saying was was was end of August, but that was given to me by the development team, not by the product manager.
07:31:01 So it's like oh yeah well we're done with our stuff. The end of August and my Oh, great.
07:31:06 Well, now there's there's as you, as everyone here knows there's a lot more to to software development, and a release cycle than just developing the code.
07:31:20 Is there a workaround for assigning CLA is, without easy CLA I mean people were signing CLA for me feel I was introduced.
07:31:30 We did not. We did not actually start doing it, I think, and
07:31:38 either Dublin or Ll toe.
07:31:43 Up until them the TASC had provided a waiver for every release.
07:31:53 So, Kenny, looking that, you know, he's a two month timeline to just get these UCLA, probably done another month to migrate that stuff and to make it happen really, we are looking into something like three months, optimistically from now so maybe he could
07:32:20 be another Weaver by the CSC to start experimenting with all Enrico, especially that we are not, you know, expecting thousand or hundred new contributors that are not already signed into the coffin did, didn't sign the CLA over there.
07:32:48 That would be a request from the om team to the TSA.
07:32:57 So, sit down he's not there he's on holidays and he's showing the videos, I don't want to make that kind of actions, without his agreement, but I believe that we can include that as a topic for next year see meeting Can I will talk with him and prevalent
07:33:15 I think
07:33:18 it was the initial request for that.
07:33:21 If we read the first magnet exactly what he was asking for so the two or three others on the quest menu for the M stuffer that you could have access for today.
07:33:33 If you look at the number there are the three people from fit, plus the guy who was a former owner. So adding two people that we already know that are free trusted could add two to go more straightforward especially for that but I think we can we can
07:33:46 put that for the next meeting but it was initial request.
07:33:50 So he you know he was the initial request for certain from Sylvia, I believe from making it happening earlier, the sooner than later, would be only beneficial.
07:34:01 So, Eva TASC could vote to, you know, make the on migration really happen and not wait another three months for that. I believe that will be really thankful for that.
07:35:30 Sir, can you just make sure that we are on the same page. so if we get this Weaver from the TC doesn't mean that the next day, the migration of all I'm repo may happen.
07:35:45 I think that the getting the data there.
07:35:53 I don't think is dependent upon that.
07:35:56 Being able to commit there's is the is the question and, and I don't know the answer to that, to that specific thing. So there's two things here is first, the existing data has to be migrated.
07:36:13 What do you mean by that they mean just, you know, get boo Garrett on up or get push the club on up, etc. Is there some more data to be well, we're still gonna miss the actual automation right the the actual ci, because everything is written to to work
07:36:49 Garrett right now, but is that they own jobs that are needed would also be need to be written to work on. Good love, yeah. That's right. But that's something that.
07:36:51 So again, did I agree that this is something that we can handle.
07:36:56 So, we do not consider that to be an issue and that I believe that without so initially obviously we may push the data from Gary and make it read only on the CI, and then simply a lot of the lot the Gareth repo and you are on the clock right.
07:37:23 Just want to understand what we are doing,
07:37:29 because we had already agree that we will move on. Don't give up, but because of the license concern that TLC cannot over path.
07:37:43 We have an issue.
07:38:02 The DSP cannot approve that over to the good lab.
07:38:02 If the CL is not in place, because it's a violation of the licensing agreement that all the company has with ya
07:38:06 is very know that we bypass this yearly agreement that all the company have with the lF and move on your. I don't feel comfortable, from a legal perspective to authorize that I want to be very clear with you because each company has signed an agreement.
07:38:30 And I don't feel that the CSC from a legal perspective has the authority to do stuff.
07:38:38 Yeah, so I may have missed misunderstood the context but in my understanding was that we already have a corporate life or individual license agreements are written for most of the contributors and contributors.
07:38:57 And now, easy CLA is just a tool that outlines sign that are out there rising people by a designated person from from each and every company, right.
07:39:11 So, my understanding is that if we move to eat if we move on that repo to eat left, and we do not have support for easy CLA.
07:39:23 The only thing that we miss is the outline to prevention of contribution for people who didn't sign this this CLA is my understanding correct Kenny.
07:39:44 Can you can you rephrase that.
07:39:47 So, if we migrate all in repo, to keep it up, without having the support for the club in easy CLA.
07:39:56 The only thing that we miss. So, we have know that there is no legal issues with that. That's the first thing.
07:40:05 second statement is that all contributors. I mean, all our CLA that has been signed wild starting country while starting contribution to Garrett from each and every company, they're still in force, so that they are still involved, it's nothing that violates
07:40:26 them. Do you do migration for and repo to do that.
07:40:30 That's the second thing that we need to have an access control on the good luck.com, if we don't have an access control of good luck.com.
07:40:40 Then we might have an issue.
07:40:41 So it means only the companies, and the paper was been granted to work on own up, or to the can access to it is my neighbor decides to contribute to the league good luck.com, and is not known by the CLA, we might have an issue.
07:41:04 Right. We need access control applied to Good luck, calm, because I don't want that. Any of you or your company is brought to you by dealer, because we violate the agreement.
07:41:19 So, in understanding what Christophe was asking. I believe what you're saying Christoph is correct.
07:41:33 The regardless of the pool in use.
07:41:41 The fact is that if you have made the commit via Garrett, you have effectively signed the CLA associated with your with your company. So that's in place, regardless of what tool that we're doing to Catherine's point.
07:42:03 Yep, someone would.
07:42:07 If someone knew where to make a commit
07:42:14 to Om.
07:42:17 When we don't have the tooling and pray place.
07:42:21 Then we've got a problem.
07:42:22 But if it's somebody who has already made a commit under Garrett.
07:42:28 Yes, that would still be covered by the CLA the existing CLA.
07:42:36 Right. So, now, if we look at this from you know from from the automation perspective, even if we do not have easy CLA in English its support for Deidre easy CLA something that we could do if we have the ability to check if a particular Gary account has
07:43:03 signed the CLA. Then we may have a simple boat that takes you know the identity from comment, and then checks in Garrett whether the CLA has been signed or map and simply both puts a comment on a request, and then that would be it as a temporary solution.
07:43:22 And then simply, provided that you know me and so on are already preventing.
07:43:29 A lot of you know mistakes from emerged. That's just yet another factor that we need to consider before merging get back.
07:44:01 That's that's that that's not a Kenny decision
07:44:09 makers, or any company that the few because we take a wrong decision here So, either. There is a system in place to control the access to the good luck.
07:44:23 So, and the lF accept that they will not pursue any companies, in case of issue or either we don't proceed.
07:44:33 When it's about legal stuff, right, I'm not joking,
07:44:39 right so I just found a way to least, I believe older members that have signed CLA, so there is that group in Gary sampled all knob CLA cc LA. So, I expect that we may have a simple query to get it from some technical account and very easily verify whether
07:45:06 we are dealing with a new contributor to appear, because we move to get up or I contributed to that is already signed CLA agreement.
07:45:23 All we only limit you to eat to you, but we only limit to the OMQ meters. So we can do.
07:45:31 and nobody has access to this repository.
07:45:35 But, but then how people are going to contribute.
07:45:44 So, either we try to be in alignment with the liquid problem that we have. And we know the people.
07:45:59 But we cannot open a breach. But every So my understanding, I'm not a lawyer, right, but my understanding is that there is absolutely no legal issue. A someone else who didn't sign a sec la creates a poor, poor request to all and report that I believe
07:46:19 it's that there is no legal issues, until we marriage that definitely request.
07:46:27 So if the pull request is not merged. It always stays Java pull request.
07:46:33 It's open source so anyone, anyone, even without signing CLA, they may clone the source code, make any modification pop leave them on their own repo, and that's completely legal.
07:46:48 What CCL I went to UCLA, is that require is when we are allowing that new source code to enter to the main three. Right.
07:47:01 So, if we managed to catch new contributors and we have a clear calling, hey, this contributor is not least in our gallery. So, this pull request cannot emerged, where it does not going to merge stuff, and and that's it right and.
07:47:23 But if you want the money you can, but I want to clear statement that the lF will not pursue any companies individually. in case of issue.
07:47:39 If we cannot put a clear access control in place.
07:47:43 I want to protect companies and individuals. If it does not work.
07:47:50 So, either we have a statement from the left, they will not ask you any of us any company.
07:47:57 Any company.
07:47:59 Either we put access control in place.
07:48:03 But I will not take the risk on your way out.
07:48:15 So it sounds like extra stuff is proposing and access control mechanism by querying this Garrett file.
07:48:28 But if we do this, easy, we'll go hide consult we'll do it, we'll do is I don't know who we know them this year SLA and that's it. But the example provided by Christophe which is done with risk of the contributors.
07:48:44 I cannot take the risk to as contributors.
07:48:47 We have not assigned a League One agreement with yellow.
07:48:52 That's my concern.
07:48:57 So, Jesse, please correct me if I'm wrong but I believe that this is the full list of people out there right under CLA to to contribute to all right.
07:49:09 That looks like it.
07:49:12 So, if we have that least. Right. And we have alter information in comics that is being pushed in the pull request by a deep law.
07:49:25 Then simply checking give the name is on the list would be just the full functionality that is the CLA is doing. I expect.
07:49:33 Unless I'm wrong but I believe that, you know, Gareth is a service that is hosting for us right so they may do any modifications that they want.
07:49:47 But when we move to that public service, like geek lab where we do not own the infrastructure. I still expect that the role of easy CLA would be advisor.
07:50:00 So, all what we will get would be a bold colon states hey this person has not signed to cc LA, but that would be it from from the functional perspective, I think, or Kenny maybe you know something more how the easy CLA for Rugby Club is going to work.
07:50:19 Right. Are you proposing an automated check against this list or is this something you would man manually do.
07:50:26 When you do come to my office right also part of the CI that will create for for the repo. If we can do some deal, then there is no issues to just, you know, create an iconic character and simply query that page, much, but I would think we just need somebody
07:50:56 somebody in
07:50:49 the automation you're proposing and push that and say yes this is equivalent to what he's UCLA is going to do anyway.
07:50:56 Yep, yep, yep. Exactly. So that's something that we might prepare it's, it's not a lot of development right, it's like a single w get in the Middle East,
07:51:12 or Kenny Do we know who could have to take this to to have them look at it and bless it.
07:51:23 This would be the real inch team I would think.
07:51:30 I would also change in, in legal or something right yeah exactly I would also want to run it past past legal, for sure.
07:51:44 We have a concrete statement from the lab that knowing David on the on of community new company will be prosecuted there is an issue I have no problem with that.
07:51:56 But we, we are speaking about legal stuff here, we are company a sign of paper.
07:52:02 So we want to be sure that there will be no problem.
07:52:07 Now he can be automated manual whatever.
07:52:10 But we need to have access control.
07:52:15 So, that's really the thing that I'm trying to say here is that for Gary currently easy to easy CLA is preventing contributor from creating a batch. So, if you are pushing a new batch from an account that has no sign CLA, or is not on some kind of the
07:52:35 list of least of outright contributors, you won't be able to create a new review.
07:52:41 But that's possible because we own Gary, where this is happening right we own default infrastructure from virtual machine to the guaranteed service that is around there so we may add, there are some additional checks additional hoops modify UI and do
07:52:54 anything that we want with that just Gareth is open source.
07:53:02 But when we move to get that my understanding, but still can please correct me if I'm wrong but my understanding is that we have no ability to modify a default policy that anyone can provide can can create a pull request.
07:53:19 The only functionality that easy CLA will be able to provide us, would be to check the Create new created pull request from from an account contributor and verify whether this contributor has signed a CLA or not.
07:53:39 And then provide the feedback for the maintainer of a particular repo and in this case, that, hey, this person has not signed the CLA so you should not merge that code.
07:53:47 But there will be my understanding is that there would be no function No, no mechanism that will prevent the person from creating down from creating request.
07:54:12 Oh, I.
07:54:16 So, the
07:54:20 proposal on the tab on the
07:54:27 sleep deprivation guys My apologies.
07:54:32 The proposal on the table.
07:54:37 Is that om team will right within their own ci chain.
07:54:49 The check against the existing Derek list of approved competitors.
07:55:02 That's correct.
07:55:04 So
07:55:08 I think the first thing I need to run that past, legal, so let me do that first.
07:55:19 To make sure that they would be okay with that.
07:55:25 And then, the TLC will need to give that the thumbs up or thumbs down.
07:55:38 Does that sound like are we all on the same page here.
07:55:45 Yep. If we have liquid statement based on what I said, I think we're good.
07:55:53 And we of course need a mechanism because I'm sure develop as a lot of features, but today there is no connection between CLA, and good luck, and so on.
07:56:20 And when we have a clear statement from the left, that there is no legal breach.
07:56:15 Then we will need to move to the technical piece of it.
07:56:33 Kenny I just wanted to make sure that we captured that correctly, we are not going to develop any kinds of competing solution to easy CLA and we are happy to remove that.
07:56:47 As soon as easy CLA is in place for Gary, and we are not going to have our own database or anything like that, just query Gary to verify if the person is on the least that is over the available, provided by easy co life.
07:57:26 better capture the essence that capture it better.
07:57:31 Yep. Okay.
07:57:41 Okay.
07:57:47 That was a very healthy discussion.
07:57:53 So I got the action item.
07:57:55 And I will follow up on that.
07:57:59 Anything else on that topic.
07:58:06 Where do we did.
07:58:10 Yes, thank you need to keep us updated but when we speak about legal and security violation, we always need to be cautious. So thank you to keep us updated as soon as you know the feedback from the legal team.
07:58:25 Okay.
07:58:29 Will do.
07:58:32 Moving on, then. security patching saw
07:58:37 a note from Japan that it's done.
07:58:45 So, the lab should be back up and running the Intel labs should be back up and running.
07:58:53 As far as the new lab goes.
07:58:57 The, there was supposed to have been a finance committee meeting on Friday.
07:59:04 I thought that everyone was back from vacation, starting last week. No, they were not.
07:59:13 I had my calendar was not correct so we are that meeting had to be rescheduled for not next Friday but the Friday. I'm sorry not this Friday, but the Friday, next week.
07:59:29 So that's where that conversation is right now.
07:59:38 And then Dr compliance.
07:59:43 Getting back to that conversation Catherine I were talking about that yesterday.
07:59:47 The question for this was where
07:59:53 was that going to be
07:59:58 run.
08:00:03 So,
08:00:06 it was agreed on pursuing the proof of concept for scan code IO, but we needed some work to implement that.
08:00:18 And that was left in the communities hands to figure out.
08:00:28 an idea, because we could maybe on the BOC on this couple of projects to reduce
08:00:39 to reduce a little bit the size of what we want to accomplish.
08:00:44 Because we were yes so is it when we know when love is not really stable, right until we move on, we need to characterize the release, instead of the BOC is your subscription, fine, but then we need to not have everything otherwise it would cost a lot.
08:01:08 So, we don't know if there is a lot today which is suitable for that now.
08:01:19 So any ideas, where we could do and that is, we can continue to run that where we used to run the preview scanning dynamics come. So, on the weekly in DC so we used to run such scan in this DC so as a ver.
08:01:38 There was a new teacher. So I have to clean that but we will reuse them anyways that's a seminar that we use also for the stability and residency testing.
08:01:49 So we usually we stopped by scanning.
08:01:53 So we used to do that every week for the last two months I think so we have a daily scan here.
08:02:02 Alexander wants to do it through scandal tell you but I think we can reuse this lab for for for for this book.
08:02:08 Okay, so, Morgan, the only challenge and that was there was that scandal IO is a little bit different in construction with that downturn, so it's not only a tool does for us is like
08:02:25 a separate, let's say, web application that stores the stores and caches the results underneath and then allows you also to, you know, make a decision who delivers and stuff like that.
08:02:41 So that's actually get the part where the communication have access and trying to, and currently I don't know how we could integrate that with the results but but if you have any vision, how to do it we can you know, but ok but I was thinking it was submitted
08:02:58 to them but you're right if it's a web server.
08:03:03 Also, in origin, the Nexus. So I don't know exactly, we need another server on some syndicators can do but is it a full assessment or it's something that we have to install on our side.
08:03:17 And so, I believe, it can be so it's not a software as a service. It's something that you deploy.
08:03:24 So, you just need to run that run a couple of doctors and that's it.
08:03:30 Okay, so if you want to have something for one shot that something could run under Wheatley as can we can create a VM when you install everything you need, sir.
08:03:47 I'll create a bunch of posts on the undercard of this poster, but for something, it can, it will last on me as a duration of the lab so maybe we need to find a solution.
08:03:52 So we'll discuss with Alexandra, to be honest, I didn't discuss a lot and that we can probably have some resources, but of course the, if we can have some Victor's resources, it would be also a good solution, assuming that it's closer to, to the next
08:04:24 the CIA chain. So, but we can continue offline for that. Sorry I probably mislead everybody was my proposal because I was not fully. I did not have a full picture on can cut the title, even Alexander try to explain me before my vacation.
08:04:39 But, yeah, we can continue offline, but we need to find a place ok ok I got it.
08:04:45 Yeah. Sure sir.
08:04:59 How we have an agreement from security team to, let's say, create create a short list of people who can, you know, have an open VPN access to do that, but not, you know, fully open for the community as you'd like.
08:05:18 And just because some Victor so capabilities to search capabilities for for this QC.
08:05:28 Every an idea Boulder, so Crisco, we were still on ID, about how much unique storage memory CPU, whatever.
08:05:38 So, we discussed with Alexander that if we start you know with a VM that doesn't have 16 or 32 gigs of RAM, four to eight cores and for the beginning founder, or two gigs of storage that that would be enough.
08:06:04 But he's the mechanic give us an ID to Jesse Campbell, the additional capacity.
08:06:11 I can look into that.
08:06:14 They can you create a ticket on that I can follow up with with information that you need.
08:06:21 Okay. Sure, no problem.
08:06:24 You can share the it ticket so we can follow up on, on the tickets as well.
08:06:30 Okay, cool. well, we'll put that in the chat.
08:06:34 Thank you.
08:06:57 Okay,
08:07:02 moving on.
08:07:05 Then sitcom presentation this. You guys just want me to share the presentation, or does somebody else want to share, like I can share my screen now.
08:07:19 Ok, one moment is over.
08:07:27 Now you go.
08:07:38 Okay, do you see my screen.
08:07:39 Yes, sir.
08:07:43 Okay, this is just an information about somebody to have a nap was a good, and we tried to explain what we tried to do.
08:07:55 So, as you know, as he sees a current status.
08:07:58 We have to change.
08:08:00 One is, people developer or us give it to push the code.
08:08:06 And Gary, send an event to Jenkins.
08:08:10 Jenkins user will demand.
08:08:13 And the resending an event to get it under the face please one and minus one on the right to us to now, but so now we are no really Shall we are we are seeing the.
08:08:27 We aren't seeing the Presenter View.
08:08:30 Okay, he's bit.
08:08:32 Yes, now we can see it wouldn't Yeah, now we're on the next slide.
08:08:38 Yeah, I don't know why.
08:08:41 I don't know why. We can shells as a full screen but
08:08:44 as I as I explained on today. When you push content to give it so now does not analyze the content of the new credit.
08:08:53 And we have only analyzed for day, and on the master.
08:09:00 That mean today is that people will merge occurred, have no visibility of the quality of the code.
08:09:06 And that's the reason we have so strange quality of the code of an app.
08:09:12 And just so gunpoint.
08:09:15 The content of brunch and evangelizing so now they mean you should
08:09:21 attach for book for example for you or for specific feature branch. You have no idea what is the quality of this good.
08:09:32 So what we try to do as the proposal is to use different elements.
08:09:39 We would like to do us a web services on the web book. We book is.
08:09:44 So navigation. So now cloud and web services is, for example, something different by your major wiki.
08:09:53 And in this case, when the developer I push and commit.
08:09:59 Jenkins and stop cadenza and stand out.
08:10:05 Run, and then I have the code.
08:10:09 And we were both post result of the scanner and web services also post comment on every patch user can use correct or not.
08:10:21 And in this case, the people just magic good math on these are good for brunch.
08:10:31 Then mean to do that, we need to add that Jenkins, as a moment. Good job.
08:10:39 We need also on so now to set for analysis or branch on each commit deployed the way book defense according to get of feature.
08:10:52 I just tried to show.
08:10:56 Okay, this is the quality get up so now.
08:11:02 And today,
08:11:04 unsuspecting right of the slide.
08:11:08 We have only one criteria, and symmetric it's a line coverage.
08:11:14 And normally we need to have all sorts of duplicate lines accountability is a secret us but this is a good.
08:11:23 So we need also to charge.
08:11:26 If we run on news equality get feature for the new code of old code. That means we need to clean the historic of the corner. He's a big job.
08:11:39 And we need also to deploy on that website.
08:11:43 wikimedia to adapt our context.
08:11:49 So, today.
08:11:55 What is the next step, we perform QC on the lab.
08:12:14 Done and good nose optimization is performed by LNF was a web services, working progress we create two tickets.
08:12:06 And I notice you go We are waiting feedback on the question from our top.
08:12:13 But the cherries, a 90 day until until this week.
08:12:18 We need to decide or so qZ choice the project and test with vision project.
08:12:27 And again generalize to all project.
08:12:32 These we retreated to do. Hi hope it's a helper, or people on the, on the committee to have a bit of a better quality of the code of honor.
08:12:46 If you have question.
08:12:51 Thank you for being a couple of years.
08:12:55 It's always good to have ID to improve the quality of the code.
08:12:59 Can you go back maybe on screen three think is what what it is not clear hi no we had
08:13:08 a proposal in the past to try to validate immediately the decode submitted is great.
08:13:15 But the concern was, if we have some project we have a lot of commits within the day.
08:13:24 It can generate an overhead.
08:13:27 When the after the fact will be available. So I was wondering if the slide, please. Alright.
08:13:35 The Christmas light is you can come back. Is it images. I mean, a person push, and then you, you have the response of the poem that everything is within the 10 one minute, something like this.
08:13:52 You think is great, because this is the is the chain of Santa Claus is dharma. We are super sweetie to commit directory, because as you can see, 123, it's optional, but normally two same times that's the reason we need to do a QC, which are smaller, smaller
08:14:14 component, and to check those of you have you have Gary tan and web the web services or medium.
08:14:26 Yeah. Yes, go ahead.
08:14:28 I mean the the concern from the picture when we tried to put that in place was really.
08:14:35 I remember my calendar was DC.
08:14:38 Because that's probably one of the biggest projects at the time he was really concerned because he gets a lot of commits within a day.
08:14:46 And there was too concerned that he takes already I don't know how many hours to do the compilation, so each time if somebody submits and we need to wait the 10 hours whatever it was looks easy but that's where are you good feedback you provide to us.
08:15:01 I would recommend only to test it on a small project, but those through a project which is more dynamic to to see if we can have any side effects but I think it's a it's a good way because we have junior senior developer and sometimes you don't realize
08:15:21 that you know that there is something wrong so it's it's and if we could put something like this. Then after one minutes we push the several forgot already the feedback is good or on a good, that will help.
08:15:34 And then my third one request of questions, it's not necessarily a quick request, but it's, again, based on what we have been discussing in the past.
08:15:47 Do we blend and without doing the QC maybe it's a crazy request do we plan to give an authorization to the PTN to bypass the process of not because I guess that will be one of the question of the ppl if they are complete this, can they need to deliver
08:16:06 something in emergency.
08:16:09 Have we disciple, superior or it's everybody had the same level. And again, I just share feedback we got into past when we try to put these things in place.
08:16:21 But I think already we go, we get the results faster, which will probably give a good feeling to the PDF.
08:16:28 And I give the next question would be, what's up burn knife I am in emergency Can I bypass all to go to be.
08:16:42 To be clear, no, no, no, no money. I hope, I hope Web Services is these quickly.
08:16:46 And you have some feedback of liquidity of that could be frozen mountain, very quick.
08:16:51 But if you give the possibility to bypass the quality of the good.
08:16:59 And my feedback is we try to stay on the, on ZCT mommy's a lot of Bergen look scary to spot on.
08:17:10 I don't want to give them to shut this facility.
08:17:16 And again I don't say we, I just put it on possible question you might have a British your eyes, the response time is filed.
08:17:27 I'm pretty sure the response time is filed. The adoption will be very hot. Right. Did you already had an opportunity to share this presentation, with the PTA, because I'm only sharing what I remember from previous discussion, but maybe they have a completely
08:17:41 different opinion that's what I've shared today.
08:17:47 Not yet. Only on the spectrum.
08:17:55 And we are waiting as you play month of the solution by elephant and try to do a demo.
08:18:04 When it's when it's done.
08:18:07 When you feel ready maybe share it to a BTL Cole.
08:18:13 Let's be back feedback. Early in the change but that's what that's supposed to be quite promising so thank you so much to share with you. Anybody have any questions.
08:18:23 So this is only for Java we are doing right now or we are also considering other languages.
08:18:35 I didn't.
08:18:38 So, some more cloud I believe work, so sorry Fabio and I believe it's on our cloud works for both Python, it does work with Java so we can do it for but my question.
08:19:00 It's good to take that into consideration and one one emphasis we have to put this on. I think that's an already talked about it, is extra time it takes for this politician, if that can be given for each of the project for example there are some projects
08:19:12 which are predict huge example is a soul is to CDC.
08:19:17 Some projects which are very small so if we can actually take a sampling of it, and submit that something as to how much time it is taking to the existing will it will be really great.
08:19:26 One of the biggest issue which group faces because during the rush times when we actually have to give releases.
08:19:32 We actually have to wait interns, because the bills are actually going on.
08:19:37 And the extra time which it actually takes for this will be actually add on right I mean, for example, when we try to multiple so bills, because of defect fixes you're trying to do, it actually increases our wait time, and it actually goes into Q.
08:19:51 So that is something maybe we can also take into consideration.
08:19:56 Okay, so far beyond. Sorry Krishna. Let me say this all goes well beyond. Let's.
08:20:04 I think that we need to take some of these comments back to set Come on Tuesday and have a conversation about this.
08:20:11 Maybe there's a way.
08:20:13 I think it's going to change the way I think long term it's going to change the way the PDFs work.
08:20:20 And all the developers work so I think we have to take that into account.
08:20:25 To really get down to brass tacks to figure out to so that they understand how things may affect their work processes, because I'm thinking you know if you're waiting till very late and release to start pushing changes, and now this gates it, it's going
08:20:41 to make everybody very angry at us at CENTCOM.
08:20:46 So I just want us to think through that, Bobby and I do you know CENTCOM fully supports this but yeah, let's let's work out that we're going to have to work out the details of you, I catch but the issue chickens are not these very good so yeah I totally
08:21:08 agree with you but what I wanted.
08:21:14 I don't understand how you can use in a production.
08:21:17 That's the reason we need to cleaner that some developer will help us as a project to Kinzer could, but we need to have the strict Chen to check out the good.
08:21:30 Now, not saying that we should take the chain out. Let's take this back, because I think there are a couple, we probably need to work with a couple friendly PTs and maybe some of the larger project, but one large project to figure out how this will affect
08:21:43 them and and to work out the details of getting the code fit, big to roll something out.
08:21:52 I'm ready to enter so yeah me I want to say this, I'm ready to enter so because I like this idea for sure this is something which is going into the court quality and longer.
08:22:01 And we have to make it production, or if we have to make our net production rate in a court should be really good.
08:22:06 So I like the idea, I should we be happy to actually have as soon as we're not volunteers.
08:22:13 I can say that.
08:22:16 Okay, thank you. We can pilot, we have so much difference actually last, we have divided into multiple projects.
08:22:24 So we do have a Soviet a larger footprint and small print also so we can pilot. This thing on on different combinations if you want.
08:22:44 Maybe we can take it offline.
08:22:44 If you are okay, I know say Congress and contribute makes you it otherwise we can discuss about this in this weekly meeting also.
08:22:44 And we can take it forward.
08:22:44 So that's great too because if some homework is a good one.
08:22:49 We have different type of contributors, different time zone, and a lot of contribution so we even.
08:23:01 It will be difficult to say difficult work with the other projects but that's a good BOC for you.
08:23:10 Yeah so far beyond Does that sound good for you that because this way we'll have a big project you can try this out on and and come up with some of the best practices that the details are going to have to institute on their project so because I'm with
08:23:20 Bobby on.
08:23:38 We've got to clean up the code, and there's no question about it, but we also need to not get in a position where we're, We're SATCOM is constantly set asked to allow somebody to bypass something.
08:23:42 And so that's why that, and. And so I think that we are via or the TLC is going to have to make the decision to say no we won't you know we won't make you do this for this release, which means nothing ever gets fixed so far beyond.
08:24:12 So if everyone you can ping me back separately. We will discuss on how to proceed on this, and then maybe we'll try to present, and present this idea back to the retail call and then second call to because we required to take both their inputs true.
08:24:23 And then we can come back to PC maybe sometime later.
08:24:26 But not before September because I'm sure sure we know Yeah.
08:24:33 Yeah, I know, I know you're responsible you go. Okay, okay, okay.
08:24:47 I'm just for information for people, we need to decide the security area. This is a metric for for the acceptance of the credit. And we need to decide for all for metric, and the value and the quality and the mentality.
08:24:57 And I don't want to decide for her but GCPGL I don't know we decided what is exactly the good.
08:25:07 And what exactly is a good metric comes aquatic.
08:25:14 Yeah, I'm sorry I
08:25:26 think you should make a proposition about your character yeah so we do the DC can review it.
08:25:25 The I need to increase my screen.
08:25:32 Are you already sharing some proposals.
08:25:38 I share my screen Yes.
08:25:39 Okay, let me see if I can use my screen.
08:25:44 You can you pull, pull, pull out the proposal gold on a separate slide.
08:26:00 Oh,
08:26:00 yeah and then and yeah exactly then bump it up so it's just
08:26:07 so funny.
08:26:11 I have one comment and one question.
08:26:14 Maybe let's start with the question so how are we going to calculate the coverage because it's not like, you know, every project these meeting those goals.
08:26:23 So, if we have a master branch that's not making the goal.
08:26:28 If you do not do any kind and kind of calculation for every punch and try to figure out which lines come from that patch and which lines comes from Master.
08:26:43 Then, trying to verify that will resolve on, let's say, My name is Juan all patches that the recurring repo that is not meeting that criteria.
08:26:57 Sorry I didn't catch a Christian.
08:27:00 So if we have a project that has a coverage of let's say 50%. Right.
08:27:05 Yeah, then he's a she's a 5050 It's a recommendation today.
08:27:11 But it's in our, our project is I know it's 80% is not 50 80% 80 80% is the record is what we need for your silver for somebody to get silver badging 55 is what we're asking everybody to do and we've been doing that for release after release after release
08:27:31 because nobody wants to increase, but just understand.
08:27:36 Right. So, we have a project, 60, right.
08:27:50 Let's put it that way. They have 60%, right. And now there is so much coming so are we going to figure, figure out which lines of code are from that new punch and count coverage, only for those new lines or are we going to calculate coverage.
08:28:00 All for for everything.
08:28:05 No.
08:28:06 It's.
08:28:07 Yeah.
08:28:11 Know, we stuck with your code. So if there is a delay, so we
08:28:14 know it's only for new code.
08:28:16 Because today it's impossible to have a good score.
08:28:22 We tried by new card. And I hope, step by step prefix historic, but we stopped on me by your new code on reject only on you could add to begin.
08:28:36 Yeah, that that that's the correct approach that I always support.
08:28:41 I'm just asking about the technical capabilities of solar cloud that if you run that review.
08:28:50 Will we be able to detect the coverage for a patch that is guaranteed. Not for a whole repo.
08:29:00 It's the bonus is upon the fee.
08:29:02 If we can reset for a new card or have you set for Oregon.
08:29:08 We have to possibility.
08:29:16 But we chose to stop. Okay, So how is going to work because if you could go back to this slide number three,
08:29:28 my understanding was that there will be.
08:29:33 So the analyzes in summer cloud is going to be run on every call me, that is coming to Gary.
08:29:42 Yes.
08:29:43 Okay. Okay.
08:29:46 And then sonar cloud is going to figure out on its own, which gold is new. I mean, which one is coming from the Gary patch and we'd run these debates go from from the repo itself right.
08:30:00 Okay. So, I mean, we need to confirm with your peers here.
08:30:05 Okay, so that that's something does come back.
08:30:12 So now, let's say, a comment from from the computer perspective.
08:30:20 So, our experience with with Jenkins and without automated systems at least in om is that they are, let's say, 95% correct, but there's still this 5%, which can last for two weeks, where they are not due to some Jenkins issues due to some race conditions
08:30:44 that we are having in May files are due to some unpredictable circumstances. So, there is a number of cases where we need to bypass junkies and mark this stuff because he worked in gating but it didn't work in Jenkins.
08:31:02 My personal opinion is that commuters should be left with those capabilities is like, you know, with great power comes great responsibility, so
08:31:15 call me terrorists should know that it's not something that they should use by default, but still they if they need. they should have the ability, and based on what I see on the slide, you propose that scan code is going to be verified zero or plus one,
08:31:34 Or actually, minus one probably and last one.
08:31:40 And I just wanted to make you aware that currently coming terrorists may simply remove the verified labels from any account. So that's actually how we are able to make a to merge batches even if Jenkins is failing, right, we just remove verify from Jenkins,
08:31:59 that which is minus one, and then we have last one on our own.
08:32:07 So, unless there are some changing policy on Gary, after implementing your proposals, your proposal gummy bears will still have the ability to bypass that by simply removing the minus one for from your service.
08:32:25 If you're drinking is down or we have no opportunity to as a feedback on Jenkins. We have not feedback from so now
08:32:35 you have a receiver yet. It's not always a problem that Jenkins is down right sometimes there are some race conditions or they're doing so those.
08:32:56 Yeah.
08:32:52 Just. Sorry for interrupting here I mean, the.
08:32:58 You're breaking session, not just
08:33:09 as good as
08:33:14 Friday,
08:33:15 at least
08:33:21 from what we have with today.
08:33:24 I think it is time off right i think i have a heavy load on the network.
08:33:28 Sorry, is it okay now is can you hear me yeah it's it's it's fine now it's not chopping.
08:33:33 Okay.
08:33:35 I'm sorry for this I think this time of the day, my network has the middle.
08:33:39 Okay, what I was trying to say is the very first job which is going right now is taking money compilation, and with this proposal we're going to add on extracting that is actually sonar issues also.
08:33:49 That is a so called sanity I would say in the other way right.
08:33:52 It is good to have. Yeah, tweaking office is possible because even current verify job is not is something which we can tweak with a plus or minus one.
08:34:00 So, that is, I think, is an independent question about how can be managed. then to add on this pillar of feature also as a part of the validation but I think we can, we can still check about the kind of overhead is going to add.
08:34:18 It's a good feature, but we have to actually calculate from the perspective of how much is the Delta change which is going to give in a bit. And also the response time for the next person that's something which we can check.
08:34:29 Coming back to Jenkins job itself about minus one plus one, that is I think a separate topic we can take it as a part of the current elephant in the show that's what I would say.
08:34:39 Yes, sir. You know, my point is, is not to be against of the proposal I fully support it. Right. I love it, I can even say.
08:34:52 So go ahead and implemented, dd common that I had was that several are several times.
08:35:00 We had to bypass Jenkins, or some other automated system because he had some issues, it's not very often but sometimes we need to do that, and we are not doing that every day, those are special occasions.
08:35:14 And those special occasions we keep our, let's say permission to bypass that.
08:35:22 And I believe that the same policy should be applied to this one, right that as an exception, Columbia, I mean, I understand. Okay, I understand what you're trying to say.
08:35:33 I know where you're coming from for that I'm saying we will not try to create a separate job but this, the existing benefit job itself can be added on so that we don't require to break our heads for the winning team, because we already have a very feature
08:35:44 which is only doing the compilation right, we will just add on this also to the very first job to give up this one or minus one. And then that the existing features will be as it is they're not going to change.
08:35:54 And we can still get the benefit of actually taking the court sanity also along with along with the competition.
08:36:02 That's all.
08:36:03 Yeah, that's fine, I'm fine with that I just want to make sure that he's aware of that.
08:36:09 Because there was a discussion with Katrina whether, call me there's have the ability to bypass the mindless verify from from the new, let's say service.
08:36:22 My answer was that not so I'm just letting you know that currently it is possible and personally I believe it should be still possible after we introduce the system.
08:36:37 Yeah.
08:36:35 Yeah.
08:36:40 Just to be clear, if you stop. And then he's of the country so now we stopped in Kingston you match. You take the risk. And you accept the request to have a security a bug or something like that.
08:36:53 And the bedroom.
08:37:02 in this body, they could dump itself record itself may not compiled, you will get a runtime error. Right. But right now, you know I'm we are in a little bit different perspective right Do we have.
08:37:07 Yes, sorry fi and so we just give them.
08:37:15 Right. So by the end the stereo which crystal was trying to say is a special one it's not something which we usually follow.
08:37:22 But there are some certain situations when we do it.
08:37:26 So don't know what the.
08:37:33 And
08:37:36 so he is the son he is a brick.
08:37:40 When we do and he doesn't lose that so he is.
08:37:48 Yes.
08:37:54 Yes.
08:37:56 Yep.
08:37:57 Yes.
08:38:03 Okay. What I'm saying is that we can check that, as a part of our piloting and we can get back maybe far beyond that.
08:38:11 Okay.
08:38:12 Okay.
08:38:14 Yeah, guys, one of the special cases where we had to bypass Jenkins for quite some time was when we broke our CI Joe's it's happening. Come on, even to us.
08:38:26 I know that people believe that no empty we do not make mistakes but come on we do us all of us. We do mistakes and we did mistake in, in ci management repo.
08:38:38 Why modifying our CI job and this make all the reviews, get minus verified from for a week or something. So, this is actually one of the special cases where we had to use that that's right to override Jenkins and just go ahead and Manuel he verified the
08:38:57 bunch. Because development cannot, cannot stand the inner place, because then you're building a huge queue of patches for deal and I believe that no one likes that.
08:39:15 We're almost 10 minutes over.
08:39:20 I have a question. I know that it came up before kind of the last time we saw this and I do not remember the discussion so my apologies, but currently we have nothing involving media wiki in place.
08:39:40 And not yet. The correct two tickets for the FM, and you have so many countries, Jessica and Jessica way to from information from our part.
08:39:53 This is just that use.
08:40:00 OK, so the goal there we then we would be maintaining to Wikis
08:40:08 know we would create a website VCs, and to adapt and our context.
08:40:13 And we get the code.
08:40:15 And we implement it for us.
08:40:23 I'm still confused about that solution because what I was looking.
08:40:30 Didn't it was all needed to be configured so that Garrett reports back on, on the results like similar to how we have the regular runs for center I still don't know where those day wiki comes into place because example that I send long ago is how we can
08:40:49 we can media does the solution, but not. It didn't meant for us to implement a wiki media is just like the way that they did it, but I don't think so.