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:22 From  Timo Perala (Nokia)  to  Everyone:
    #info Timo Perala, Nokia
07:00:31 From  Eric Debeau  to  Everyone:
    #info Eric Debeau, Orange
07:00:35 From  N.K. Shankaranarayanan (STL)  to  Everyone:
    #info N. K. Shankar, STL
07:00:53 From  Andreas GEISSLER (DT)  to  Everyone:
    #info Andreas Geissler, DT
07:01:19 From  Yuanhong Deng  to  Everyone:
    #info Yuanhong Deng, China Mobile
07:01:30 From  Ranny Haiby (Linux Foundation)  to  Everyone:
    #info Ranny Haiby, Linux Foundation
07:03:05 From  Magnus Buhrgard, Ericsson  to  Everyone:
    #info Magnus Buhrgard, Ericsson
07:06:35 From  Martial Ngueko(AT&T)  to  Everyone:
    @proxy Catherine Lefèvre
07:07:31 From  Martial Ngueko(AT&T)  to  Everyone:
    #info, Ngueko Gervais-Martial, proxy ATT(Catherine lfèvre)
07:38:42 From  David McBride  to  Everyone:
    https://www.trumanlibrary.gov/education/trivia/buck-stops-here-sign
07:54:50 From  Kenny PAUL (LFN)  to  Everyone:
    Award nominations: https://wiki.onap.org/x/lgdHC

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:39 transcript started.
07:02:51 Folks come in. you're muted. on entry please keep yourself muted unless you're speaking if you're on a phone line, you can use far 6 done. Meet yourself if you send me private chat messages.
07:02:59 They will just become part of the public record when I dump them into the
07:03:05 The chat log into the meeting minutes as always we'll start our meeting by talking about our anti trust policy. You can find this linked from the project, and all of the lf websites.
07:03:18 This policy is important where we have multiple companies, including potentially potential industry competitors participating in these meetings.
07:03:24 Please review. If you have any questions please contact your company's Legal Council, members of the Lf.
07:03:29 May also contact and drew up to Grove. the firm.
07:03:31 Gizmer a probe Lp which provides legal counsel to the Lf.
07:03:36 And this policy is in place, whether there is a member of staff in attendance at a meeting or not.
07:03:44 Okay, let's see Magnus, thank you
07:03:56 Okay, agenda today. we're gonna start off talking about infrastructure.
07:04:06 We have some discussion of ptl updates. Catherine is not here, so either Randy or I can give a quick summary of the call.
07:04:20 Talk about some of the life cycle stuff and then normal upcoming events.
07:04:27 David's posted his weekly update and as a reminder.
07:04:31 September first is when we hit m 3, so please be ready for that.
07:04:41 I asked. lincoln the voy to from unh to pop on the call, and just give us a quick summary of where we are with the openstack issues with the lab.
07:04:58 So i'll start there, and Then We'll go and talk about what's going on with jenkins. Okay,
07:05:04 So there was an issue. and I will apologize I don't have full details of what was the root cause of it, because I don't have access into the actual systems under openstack that are there I just have like the openstack login wind
07:05:19 river does the Cis admin There are actual starling acts based deployment.
07:05:25 There But there was an issue with their system, or the system and the openstack where apparently Seth data store managers became unsynchronized, and that caused a data loss of essentially the backing storage.
07:05:41 Underneath the pods that essentially run openstack.
07:05:45 That configuration had 2 out of the 3 managers running.
07:05:50 That should have been there when it was deployed and there was no way to basically then reconcile what was like the true state of things when you don't have that kind of a a deployment scenario
07:06:00 so that was discovered. believe a or weeks ago at this point whenever did that kind of quick investigation said there there isn't a way back from this and that the reinstall was going to be needed they did that
07:06:16 reinstall Stephen did that over this past weekend.
07:06:20 I then re-imported all of the user accounts.
07:06:23 Into the system. and everyone who was a system user should have gotten an automated email with an updated password for that system
07:06:37 And so that way you can log in and then rebuild anything that was there, and as far as I know, and can see from like the openstack horizon interfaces and stuff like that or the openstack api
07:06:50 everything on the cluster now looks back up and healthy and back to you.
07:06:54 Essentially the state that it was before
07:07:03 Okay, just a full of question to Lincoln: Yeah.
07:07:10 So I did record this in my email, just wondering, I mean, how do we avoid this situation again?
07:07:15 Right. Is there some sort of backup strategy going to be implemented?
07:07:21 That because this is almost like a complete rebel from the project teams who were using that lab.
07:07:28 So what what data we had is lost. I mean that's Why, I wanna make sure we don't get into the same situation I mean.
07:07:34 So ideally we should be in better state now my understanding like I don't know the root cause of what caused the Seth backs the stuff stores to become like essentially on sync.
07:07:48 In the first place, but I that kind of compounded with the problem that there was only 2 instead of 3 at where 3 is the normal H. A.
07:07:58 Configuration. right? And so this is the This is the bits of the Kubernetes underlying openstack. right?
07:08:03 So like the Cf data stores there. that are actually keeping that available.
07:08:10 So ideally we're already better than we were in the it's now a true h a configuration.
07:08:16 On this I can work with Wind River to find out what the options are for backing up either running vm images or other.
07:08:30 You know it's of the cluster beyond just the H. A.
07:08:35 Algorithms. Yeah, that that would be helpful. Yeah, Thanks. thanks.
07:08:45 I mean we still I mean I just I know we Stephen responded to my mail Yesterday I haven't had a chance to check, but I think Jack was trying to attempt some validation.
07:08:53 He still Cc issue. So so we're still not going completely out of the woods.
07:09:00 So will you pretty able walking through the emails and see if you can get the issues with all the yeah, any help Link and you can do the expert from your end that will be much appreciated.
07:09:12 Thank you. I saw like jets email. So push up on that chain.
07:09:18 I think he was asking about like if there's ports that were defied, you know, provided or port resources, they were but divided by default compared to just floating external ips.
07:09:31 And I don't remember and I don't think that we had provided those in the previous instance.
07:09:37 I thought we had just done everything with either allowing tenants to build, you know, networks between instances or grab floating allocations on the public
07:09:53 Right. Okay, yeah, I mean I have to check I I don't remember off, and how we did that previously.
07:09:57 But yeah, we'll i'll check since I have to change my VPN.
07:10:01 I'll have to check a little later afternoon and that i'll get back if train get past that issue.
07:10:06 If not, yeah, maybe we need to see what what can be done from the open side.
07:10:10 Yeah.
07:10:17 Okay. any other questions from the Tsc.
07:10:26 Okay, Lincoln. Thanks so much for hopping on the call on short notice.
07:10:31 If you want to drop I think we're done with this
07:10:40 Feel free to ping me with email if anything else comes up. I'm looking in right now just to make sure that the networks and everything are healthy and trying to solve whatever is a jacked issue so Okay, cool Thanks.
07:10:55 So much.
07:11:00 Okay. Let's now shift to the vex house issue this morning.
07:11:07 Sorry Kenny is magnificent. Sorry for interrupting you, but this the release status status.
07:11:14 Will we say something more about that? I I have some comments there.
07:11:20 We can take it later as well. But I was, too.
07:11:25 I was too slow there, too yeah let's hop back to that after we get through yeah I see David's on the call, so we didn't cover
07:11:44 So vexhost. Kenny, would you like me to take the lead on this.
07:11:52 Well, since you're the first one that spoke up absolutely Okay, so I think being in Europe, I wasn't entirely aware of what was going on yesterday evening.
07:12:04 But I did notice this morning when I came in and checked my slack messages.
07:12:09 That have been some discussion last night about various performance issues with the vex host infrastructure.
07:12:14 On which we reliance is openstack it's a shared platform, and this seems to be just some generic performance issues that are affecting some of our infrastructure.
07:12:24 So my colleague Vanessa, raised a ticket with with vex.
07:12:27 Turns out today, obviously issues ongoing. When I did some digging back to close the tickets.
07:12:34 That's problem solved and clearly going so we have we open the ticket.
07:12:41 I've open a second case visit before own app because I believe sometimes there are knock on consequences.
07:12:47 Whenbex has these type of issues we end up burning through additional compute, and the jobs end up running longer, which can feed, I think, into some of the financials I wasn't aware of that.
07:12:54 But some I think if we raise it to grown up then obviously that's covered
07:12:59 We haven't engagement from the vex on the underlying problem.
07:13:03 It could be that it's partially relying on the network performance or the H devices, because it could be one of the providers, is having some performance issues with seeing kind of general past.
07:13:12 These sort of performance, but things like access to external package repositories which a lot more build jobs are obviously heavily reliant.
07:13:20 We're seeing very slow performance to them and that's meaning that the jobs take much longer, or they're hitting the time out limits and the jobs are failing just because they're not even getting the data in time.
07:13:28 So it's clearly affecting more than one project i'm not no exception.
07:13:32 And we do have engagement. with effects. Now including I think they've actually escalated It's almost seen a tech guys who's looking at this. So I would like to think we'll have some resolution in the next 12 h.
07:13:42 Or so, but the Us. is just waking up into my colleagues over that side.
07:13:46 We'll pick this up and run with it if anybody just any further questions.
07:13:49 They might meet you on so I can try but some it's it's in progress.
07:13:53 I hope you'll get some traction on on again this result shortly
07:14:08 Okay, Any questions?
07:14:15 Nope: Okay, cool. Thank you, Matt. Welcome. Okay. bouncing down.
07:14:26 Do we have a update on the status of the C code for the the Get lab implementation update us in no news And Won't be news for a couple of weeks since people are not available.
07:14:47 Yeah, yeah, I do, answered also banked thanks for the reminder I I've not seen the the the issue.
07:14:52 But It is partly related to our personal situation here in Dt.
07:14:58 Also, so we have at the moment I told yesterday to Miko.
07:15:05 So The one who it was in charge for doing all this stuff is unfortunately on sickly even, might disappear completely on the Dt.
07:15:15 Project, and unfortunately Miko is just today started his vacation.
07:15:24 For 2 weeks. Hopefully we can clarify and more when he's back from vacation.
07:15:29 So hopefully that we can more check the C code.
07:15:35 I would try because I was will be also only next week. here, and then also start my vacation at least only 2 weeks.
07:15:41 Maybe I can try to support. but let's see if I have time next week for the for doing that.
07:15:52 But definitely, I will try that to figure out, because I was the whole week working with me.
07:15:56 How about the next topic, which we have seen here? which is below?
07:16:05 Yep, so I I know this was on the horizon.
07:16:09 It was discussed in detail last week. which is why I brought it forward this week.
07:16:14 So that's also going to be basically pending holidays.
07:16:21 So the migration. So No, no, the the the Kubernetes and helm updates are finished.
07:16:26 We did that yesterday, finally, before michelle was going to vacation.
07:16:35 So it's it is working so the the helm linking now takes It's not optimized, but it takes at least now 50 min instead of 10 h so that works.
07:16:53 We have updated the gatings. they are also now running on the newer kubernetes, and how releases?
07:17:03 And i'm Now at the moment let's say rebasing the existing change requests, so that they are then we executed because they have been failing of course, due to the fact that we are in the over in that transition
07:17:21 phase. I will do that then in the next, or up till tomorrow, so that we have all the open and changes.
07:17:33 Then on the new make file changes. We updated both the jacotta and the master release.
07:17:40 So for call. So both gatings will run on the new home chart and home releases and kubernetes releases, and we will, of course, update them accordingly.
07:17:52 Also the documentation for that well, this is finished
07:18:02 Cool.
07:18:06 That's I mean unoptimized is now down to an hour versus 10 h. that's I think we can make it for 20 min.
07:18:17 I'd say the performance of the of the Github runners actually.
07:18:23 Yeah. So that was a that's a pretty good win right there.
07:18:29 Okay, thank you so much. andres anything else.
07:18:35 Oh, well, i'll touch on on something else in a in in a little bit when we get to another section
07:18:41 Anything else related to infrastructure
07:18:48 Okay, let's pop back to discussion of release status Magnus.
07:18:54 You had a couple of questions. Yeah, I was approached by one of my colleagues saying that he suspected that there was some late requirements coming in, that that maybe not all Ptls have been aware of and haven't been
07:19:07 able to to look at or or to to the react on.
07:19:11 He? he wasn't specific on what that was thought maybe it was some additions in and a global requirements, or or yeah, some of the mandatory requirements
07:19:36 I don't know if David is someone has to comment on That's yeah. I I can go back that's that's a little bit of a problem.
07:19:46 That we have with a process, because the if I don't become aware of the the requirements that I can't get the because I assigned the the tasks for the requirements, and and M.
07:20:02 One, and if they come in after that, then unless someone flags me and says, Hey, there are some new requirements here.
07:20:10 Then I don't I don't know about it so I can go back and look to see if there's anything that's been added recently.
07:20:21 Because I recall m 2, which was in July.
07:20:27 Is the you know, kind of the closing date for any requirements for the current release.
07:20:34 But i'll go back and look to see if there's anything that was added prior to them. too. yeah, any, and certainly any in terms of any global requirements or or practices that would have had through by
07:20:52 the Tsc. right So i'm not I would be aware of.
07:20:57 Yeah, exactly. no, I I appreciate If you if you can look back and see if there is some that may not have been recognized by by some of the details.
07:21:11 If they've been in sort of early on then and then check back.
07:21:16 Okay, no problem. All i'll take an action. to go and check that out and report back to the Tsc.
07:21:25 Thanks.
07:22:16 Well, i'd get daily I guess we'd want that by the ptl meeting, but we'll market for next week.
07:22:26 Anything else on release
07:22:39 Okay, let's talk about our ptl situation so, starting with integration.
07:22:48 To the best of my knowledge there was no response to the call for an integration.
07:22:54 Ptl which leaves us in a situation of what do we do?
07:23:03 Their provisions in the technical community. document to appoint someone. But I think that we also have a challenge with the actual number of folks that are committers on integration.
07:23:23 Pop over there real quick.
07:23:36 No, no, no.
07:23:48 Okay, Well, we've got a long list of committers here
07:23:56 Is it up to date? Well, I Don't know because that would be the responsibility of the Ptl?
07:24:07 There are, of course, still more Morgan in in the in their worn, and others from Orange, which at the moment not active.
07:24:16 Okay, Wukash has changed. Actually I think that we have is he's now a dodger telecom congratulations.
07:24:28 Thank you. So we have to change the Iv email address here.
07:24:34 Yeah, this Samsung guys we are not sure I I'm not sure, actually, especially.
07:24:42 And of course, via is is as active definitely but the with the Samsung guys.
07:24:48 I don't know. I think we have an not not have anything heard from she stuff, and so on, so.
07:24:56 But maybe that has them to be reviewed again by the let's say you know, resigning Ptl. So let me go when he's back
07:25:10 So one of the things that we have talked about in the past is the scope of the integration project being too large.
07:25:33 Is that where we should maybe start start looking here. I know I Yeah.
07:25:48 The one thing here that we know is is is mikhail is going on on vacation.
07:25:51 We know that he's not walking away from own app so that's good.
07:25:58 It's it's not like we're in a situation where we're the the a ptl abandonment, if you will it's it's simply a resignation so that that's you know to
07:26:13 our favor here in terms of being able to follow. follow the process.
07:26:19 Marshall, go ahead. It was I was just 1 one just to say that maybe the whole should be.
07:26:25 Assume collective bye
07:26:35 Your desk integration in order to
07:26:45 I I think 1 one issue is, of course, which I mean what we have just done.
07:26:52 Here is to get the dating pipelines up and running to get the daily runs.
07:26:59 This is, of course, I mean we are still doing and we continue doing that.
07:27:04 That's not an issue of course, then the migration of the Github project.
07:27:08 This is the what is now at the moment, then pending. it takes, of course, Big F.
07:27:14 And time for doing that. this far we are still relying, at least for the gating on the orange implementation and the orange part.
07:27:24 But this is also let's say time critical for the in the near future.
07:27:30 We have some for example, some some things which Server did on his own premises.
07:27:40 I think in 6 weeks we don't have any dns entry anymore, because 7 had done that, and it's paying for that, and we have to move that we have, as we know that this migration of the of the of the
07:27:54 of the of the Ci chain pipelines into this Yeah.
07:28:04 Lfn. Project part. and this is a one big issue.
07:28:10 The other things is, and which should be more. The responsibility also of the Integration Project would be to create more and to end tests and and more health tests.
07:28:23 Yeah. And this is something where, of course, the project should also help here. Yeah.
07:28:28 So if if we want to make the the let's say own up more stable and reliable of course it would be nice to have also additional test cases also testing other components, besides the ones which we have we didn't
07:28:45 have time really to create new or the integration team didn't have really time to create new test sets and test cases.
07:28:57 And I think that's something I think which we were also the project.
07:29:02 Could the project could could, would help with them
07:29:13 Why is this picking it up
07:29:24 Okay, Well, I don't know for some reason it's it can't find you.
07:29:30 I'll worry about that later. So thank you andres? I do want to circle back to this the the comment about the dns part of that.
07:29:42 What, What are this? Can you share the specifics with us?
07:29:49 As I see so so one hat in some mino I o
07:29:57 I, I an account created to make Dns resolutions for owner.
07:30:03 For the own up test chains. This was done on his own premises on his own costs, and so on.
07:30:12 And this will let's say the will this appear I think in a couple of weeks.
07:30:17 This is what let me help told me he updated now, recently yesterday for us, although he me a a surveillance on vacation somewhere in the forest, he updated something for us, But of course, this is something We'll have to take
07:30:33 care also that that we get or create a new account and a new some some new dns entries.
07:30:42 I don't have the details so we have to wait for me how I when he's back. but that's I know that it.
07:30:48 This is something we'll have to take care I don't know if there are other resources or other things which surrounded at this time. on his own name.
07:31:06 Or whatever costs, and which has to be replaced, that has to be checked, checked in the next.
07:31:13 In the near future. What we can do to replace is otherwise.
07:31:17 We are risking, of course, to to get the at least gating pipelines.
07:31:26 Not running, but as I said so we need to check this with Michelle so is that like own app gating or something.
07:31:39 I mean it's it seems like this is the resource that should be from the sounds of it centralized, and and we should be maintained.
07:31:48 It's part of our yeah, it should be yeah, I have to check that.
07:31:56 So I think he had done some. yeah, some. What is it, Meno?
07:31:59 I o account where the configured some Dns resolutions for us, that I think it should be easy to replace.
07:32:08 But we have to do that. that's something we have to do Okay, and it should be then in the hands of whatever Lfn
07:32:43 Okay, so we will find out more when Michael gets back
07:32:51 On that one
07:32:59 At the moment. Is there risk to con rural release in the current situation that we find ourselves that this time I would say, no, not at this time.
07:33:22 Okay.
07:33:45 Okay, anything else on integration. Yeah, i'm i'm I have a comment there.
07:33:53 I was looking at the Om. team, I mean. there is no detail in, you know.
07:34:00 But seems like that team has done a great work and and sort of collectively.
07:34:09 Yeah, solve the problem same and coming over hurdles so that's not ideal, of course, at the news there's no ptl, but that's a also way to to handle this.
07:34:20 However, when it when it comes to integration I would say that i'm a bit disappointed that sort of companies that that are saying that they are interested in the the full sort of own up platform isn't able to to come
07:34:36 up with the with the ptl candidate when it comes to to Ericson. we we are mostly taking sort of code directly from the projects we are.
07:34:50 We're not using the the owner platform as say we we're using the the best sort of breathe code from from the various projects and and integrated that integrate that in our own products, and in demos and so on so
07:35:04 I I think it's maybe it's it's a some kind of sign of weakness that there is sort of interest in the own platform.
07:35:16 Is still no one to sort of raise their hand and take a lead.
07:35:22 The ship row. I think that's the 1 one way would be one conclusion would be that the interest is not the greatest, as we think.
07:35:32 And that we might sort of with the ambition for for integration.
07:35:37 That's of course. not ideal because you We apart from from this sort of getting a full pro platform.
07:35:46 You also get an alignment between the project threed.
07:35:47 The integration, of course. So if you're using different components you you you you get an alignment, and you don't sort of yeah, you can benefit from that, even if you're not using the platform.
07:36:04 But I think that's I have to to recognize that if there is no sort of pt coming up, maybe maybe the interest is not super great
07:36:21 One thing about headless projects, if you will.
07:36:26 That i've done is that it's true that they can often, you know, function you know, maintain the function, even though they don't have a ptl where we often run into problems, though is in you know
07:36:43 status, understanding status, and you know, transparency of the the release process.
07:36:50 Because what often happens is that, because typically like the the release management, milestone tasks get assigned to the Ptl.
07:37:02 Now the Ptl can reassign those to someone else on the project. But there's someone to take responsibility for the tasks.
07:37:11 If there is no one, then I then I often find that those tasks don't get completed, or they're very slow and getting completed, and it makes it difficult to understand what what what the status is when we
07:37:26 assess milestones so that's one problem i've noticed with that situation
07:37:37 Yes, what they say. The The buck stops here. you need some someone to to conclude on the street.
07:37:47 True, Man: Yeah, that's right yeah they said he had that on the back of his and on in this overall.
07:37:54 Yeah.
07:38:02 Okay. Anything else on that one
07:38:13 Okay, and then shifting good So and the nfsdk
07:38:20 I got a mail from dan shu saying that she wouldn't be able to attend this meeting due to business travel and center apology.
07:38:31 She will, trying to 10 next week. Folks probably saw the email that I sent out last week, but in case did not
07:38:54 Kind of garage is stepping down and and and had essentially said that was nominating Dan Shoe for the position.
07:39:07 Now he's the only one that was a committer on the Sel project, so there were no other committers on that project.
07:39:19 At all, which leaves us in the state where the Tsc.
07:39:24 Is going to have to take some action to either. promote somebody on a Mortuban project. clause or something like that for the for vnfsdk.
07:39:47 The committer lists are lengthy all those I look through the list.
07:39:51 I know that there's a quite a few people that are not necessarily active.
07:39:58 What I will do today is send an email out to the individuals.
07:40:08 Saying, Hey, kind of garage is stepping down.
07:40:16 We need a committer for Vnf. Sdk:
07:40:21 You all first need to figure this out for us so that's the steps that I will take in that regard.
07:40:31 The Tsc. is going to need to figure out what to do with the Cli
07:40:38 Probably something to wait, and next week to discuss any questions on that
07:40:56 Okay, don't moving on i've been doing a lot of talking.
07:41:07 Randy, Would it be possible for you to give a quick summary of the attack?
07:41:13 Yeah. sure. so. there is 2 kind of positions that were discussed.
07:41:20 One is the committer rep to the board which is less relevant to all of because, we sent the last rep, and we're not that eligible.
07:41:31 So. there's at least one kind of day another community, and the other thing is the approval of the what is called the appointed seats in the attack meeting.
07:41:44 We we felt in the tack that there is a need sometimes you time, to have expertise that does not necessarily exist.
07:41:52 The one of the members. So we created this mechanism for attack to a point. Experts in certain domains to be tack members for a year or 2 that could be things like security or any other things.
07:42:09 So that has been finally formalized after some proposals, and work at that.
07:42:15 So there is now a mechanism for the tag to a point.
07:42:18 Experts to sit on the tack and put the necessary expertise in which anything that will determine necessary.
07:42:28 So you might be called the point by the tag to participate.
07:42:31 So when the time comes. please consider that as a way to help our entire Lfn.
07:42:39 Community. I don't remember what else was discussed I think and we talked about the programming committee.
07:42:47 Oh, yeah, So I think in again in our case. both table.
07:42:56 And I kind of volunteered to continue doing the job of serving on the program committee for the upcoming Dtf.
07:43:04 On November. if anyone else would like to get into this sausage factory, please let team and I know, and will get you involved as well.
07:43:18 If not we will do perform the same tasks as before, and organize the agenda and
07:43:27 All the logist logistics around the Dtf
07:43:34 Thank you so much for doing that. Let me i'll just link this back here
07:43:49 So just wanna take a look at it
07:44:00 Kenny, while I have the stage, and because I have to drop in a few minutes, if you can scroll down quickly.
07:44:06 Yeah, this upcoming. event so i'd like to bring to the attention of our community That first of all there's if you don't No, there's a hyper ledger pro umbrella project
07:44:18 under the Lf. which deals with development of blockchain technologies, and they have several special interests groups.
07:44:28 One of them is a telecom special interest Group
07:44:33 And this special interest group meets from time to time, and sometimes experts or people with that especially interest present their related work.
07:44:44 So first of all, I I recommend that our community members. They can look at that.
07:44:50 And can you just share the link here Specifically, on next week we meeting?
07:44:58 They have a presentation about for 2 researchers about the use of blockchain for network slicing, federation and brokerage.
07:45:08 So if you're interested in networks slicing and Federation it might be a good opportunity to attend.
07:45:19 And learn about this research proposal. The way this special interest group works is, people come and and propose topics.
07:45:27 And the way they work my defer by on the case to K.
07:45:33 By case it's sometimes more long-term research proposal.
07:45:38 Sometimes it's the more short term proposal for developing specific things under the hyper ledger.
07:45:46 So once again, take a look at the upcoming presentation on the 28. but also take a look at some of the other work that might be relevant to things we're doing in the own up community
07:46:01 Questions.
07:46:06 Okay.
07:46:11 Okay, life cycle. I don't think there was any more work done.
07:46:22 On the proposed edits. and David keep me honest here.
07:46:32 Just can, and I made some cleanup It was just about indexing anything set up.
07:46:38 So
07:46:47 Let's see here, we do this there was some yeah There was some issue on the on the numbering 45,
07:47:10 Yes, there's many numbering features yep
07:47:17 Great. Thank you so much
07:47:25 So I guess the question is, how close are we to actually putting this forward to a vote?
07:47:38 I think that we should probably go through one more un maintain projects.
07:47:44 Review of it. we've already got and kind of tested approval from the Tsc.
07:47:54 On those from last week's meeting so maybe bring it forward for a vote next week, or at least get it distributed for for formal work you next week.
07:48:12 Other thoughts around that
07:48:21 Okay. Cool again, Marshall. Thanks for you know, Catherine going through and doing that.
07:48:29 Really appreciate it. in that regard, once we do that, then setting up the project reviews is something that we we need to do.
07:48:39 There was a suggestion that we probably should start with Cli and the nfsdk.
07:48:46 On that. but we will kind of table that for now the election cycle will start September first.
07:48:57 Andreas. You said that you were leaving on holiday Yes, that's right.
07:49:09 Yeah, I I would stop my vacation next week, Friday until the tenth.
07:49:18 Oh, for the eleventh of September. Okay,
07:49:24 Are you considering running for a seat? again? yes, I will.
07:49:32 Okay, would anyone on the Tsc. have an objection?
07:49:40 If Andreas was to submit his candidacy before he goes on holiday
07:49:57 Yeah, I take that as a No. so I will get things set up so that you can go ahead and and fill that in before you leave.
07:50:05 Alright. Okay.
07:50:36 Team t a
07:50:38 Team T. A. D. E. D. I still spell it wrong will be accommodated.
07:50:48 For folks on holiday as of September first.
07:51:02 Kenny will be possible to just start the nomination period early, just to be fair to everyone creating impression that we're creating special considerations for our own
07:51:23 You know what that is the more correct thing to do. Thank you, Randy.
07:51:30 Yeah, this is this is the forest and trees issue for me you're absolutely correct.
07:51:39 I will just go ahead and and and kick off the the cycle and just make it a longer cycle.
07:51:45 So I will kick off the nomination period early.
07:51:54 There's there's nothing that prevents that It says the elections will take place in September is the language in the in the community, Doc.
07:52:06 It doesn't say that the the cycle needs to start in September, since the elections will take place in September.
07:52:13 So yeah, no, you are, I I That suggestion, I believe, is is the proper one.
07:52:23 Agreement from the Tsc. on that
07:52:31 Okay.
07:52:35 Let me reword that because yeah you're you're absolutely correct.
07:52:41 I just. Andrea had said something about his vacation earlier, and and that like clicked in my head that the elections were coming up.
07:53:00 Okay.
07:53:01 Okay, So i've got some marching orders There
07:53:17 Give myself an action. Item: What?
07:53:40 Okay, and then the Jakarta awards have been extended through the ninth of Stephen.
07:53:50 I have not looked at this in a couple of days, and we still have a relatively blank slate of nominations
07:54:08 We have
07:54:15 No nominations for the dows. So, please, I will drop that link into the slack window, earned that in the eye into the chat window.
07:54:34 Guess I can drop it in slack window. 2
07:54:53 My mouse has been giving me so many problems I know i've been sniveling about that for a while.
07:55:00 Now probably should just get a new mouse. Okay, any questions here.
07:55:15 Oh, the other piece of it is that there will be extended
07:55:34 Randy already talked about the hyper ledger thing.
07:55:39 One summit. North America registration is open. Please register for the event.
07:55:44 And immediately following that is our next developer and testing for them.
07:55:50 This will be one of our 2 day events rather than the 4 day event.
07:55:53 But you know, soup to nuts one side plus developer summit is a 4 day event.
07:56:01 So please do that. The the proposal page is already up and available for you to start filling out