Hello, hello. Today is May 19th and we have a regular governance meeting. We announced in the developer melon piece, we have a quite packed agenda for today. We have some news, we have roadmap updates review, though no all topics have been submitted and I'm looking for I'm not submitting my request. Jenkins JEP process updates, knowledge updates, with many sub topics to be in Ruby runtime to determine what are the next steps. I think half issues of opening governance. Front of Jenkins Revamp, plugin end of life policy. As you may guess, we are going to like reach these topics. But yeah, let's start and see what we did. So, yeah, news. So the first and most important news, we had Google summer of code announcements. This year, we will have five projects. I mean, I think it's project that is also one project focus on spinnaker. So projects we have cloud events, plugin for Jenkins get financials binding. It's more different from materials. Most likely, maybe open telemetry will still discuss that security with the data for Jinx. And semantic version, which is also subject for remain from what I heard in the chat. But yeah, so what it means we have five quite important projects. So three are rather focused on Jenkins in the cloud. One semantic version is required for this DLC stories. I'm using Jenkins delivery pipelines with this concept of the previous contributor summit and get credentials. Yeah, well, it's a must have. Because it is much on every Jenkins instance. And it's quite important, especially again, it will be security trends. So, improving credentials binding, I think would be important addition to the plugin. So these are topics. Today we had a kickoff meeting for community bonding. We had something like 10 participants there for them, your students. And yeah, we still will publish recording, but so far so good. We will start at the prospect of a similar sleep because yeah, there are some topics discussed, as always, there are some struggles, etc. But overall, it seems to be good. Yeah, you start coming to bonding. So we encourage everyone to help students if they reach out in the community is welcome the students and if any of them is watching welcome to the Jenkins community. So, it's a great update that we will put applications which was unable to accept. So right now, I'm looking into alternatives. And if I find something, I might come up with a budget request for this summer. So that we could run a program on our hex mentorship. Because here we had several project ideas, which are quite important, but we should be unable to accept you to various reasons. So just to show you what we have from the automatic specification. Again, not this year. Custom Jenkins distributions again not this year, or at least not the same JSOC, but it would be awesome to actually get it to the operational point. The installation manager improvements. My parents, this is Jenkins all of these topics are quite important. So, if you could have a program, it would be nice. Right now it's just heads up because I have nothing concrete to ask for. I still have an action item to actually send an update about our budget. Maybe one important topic. So we will have to move out of the SPI. Yeah, we discussed the SPI. The original plan that was that we can use the SPI treasury as long as we need. When we were discussing this into some dating, but as long as we need to and basically three years of transition, etc. So three years of transition. And I asked them and they said that the migrate. So there is no strict need to be created tomorrow. There are some action items on the Jenkins governance board, but I think that you need to go to LFX crowdfunding. I still have an action item to get to other board members to LFX crowdfunding management so so that it's not a bottleneck. And after that, yeah, we can initiate the transition. And my another action item is to actually send a budget report. But yeah, right now, on our accounts, you have something like $14,000 from them, almost 8000 GSOC money we receive this GSOC students organizations. So, yeah, it's not like we have the same amount of money. But yeah, we have never fundraised. And if needed, we could try fundraising. Okay. Any questions, concerns, or you move on. Okay, then I see you have talk to me nation updates. So last meeting, I will be the nominee from the Jenkins community. After that, there was a need to submit an admission to statement. I shared this statement with the governance board and with the developer mailing list. I got some feedback address to that and submitted before the deadline. So, yeah, now it's submitted. You can send statement somewhere in the developer mailing list. Yeah, we are waiting for the process to be announced. And on the related news, a CDF has just announced general member seats. I mean, this year, two seats in the talk will be left from among the general members. And if you know a contributor from a general member, you can eliminate them. So you can find it's taking the other side committee. And there is a description for eligibility, but basically any member of general member of CDF, any employer can be eliminated. So, you won't consider doing that. So basically what is the lowest increasing volume of Jenkins users and contributors and the CDF talk. But yeah, let's see how it goes. So, Raihan has released the release candidate for the next look CS baseline. It's announced in the developer mailing list and again everyone is welcome to test it and provide feedback. Again, we have open questions about how we promote release candidates better to facilitate feedback. But yeah, the release is there, so hopefully somebody tests that and provides feedback. Any comments about this release? 334, is there any things you're concerned about in general? In this release, so there was a patch which we had to regard because yeah, there was a teaching my deal of Firefox, which they implemented that then regarded so Daniel has more details about that I believe. I mean, the original patch has been in weekly releases for a few months now, but only fairly recently was discovered that it caused a regression, mostly in HTML unit. And I think in the testing for that it was also revealed that either the new patch or already my patch mark you will know that also cause cause problems with form submissions being blocked. It may already have been in my patch. It was already in your patch and the delta the revert has healed it. And the, the change from Thomas, Thomas, Grenier de la Tour also seems to have healed it so we've got a potential fix. We've one we've got the revert, and that's in the 2.2 89.1 release candidate I've confirmed it. And we've got a proposed address the problem that Firefox brings also that's pushed up as a candidate needs more review still. Or at least I think that was what you would ask for Daniel was please could we get more more eyes to review this particular change. Right. Yeah, that was when I thought it would go into the weekly. I don't know what the current status is. But yesterday it was, you know, fairly late changes in the pull request, I think we'll just take care of it. It would be nice to have the new patch already in point one. It doesn't sit right with me to revert something that's been in the weekly for quite a long time, but it is what it is. Yeah, for me it was important to revert it from the weekly because of how embarrassed I am that I didn't detect, didn't detect sooner the problem and chase it down. So I was aware I had a problem I thought it was forms conforms modernization, I was wrong it wasn't forms modernization for once that blocked a submit so yeah. And you tried to ask that and thanks a lot for that. And thanks a lot for everyone was delighted. So, and anyway, the scope isn't that big in terms of web ports, the scope in terms of features we bring from weekly is also not terribly big, because we didn't have major breaking changes. We have table studies, etc. in the previous LCS baseline and things like Ruby runtime, etc. we haven't merged it in time so yeah this release is relatively safe. Yes, I haven't created the change log yet and I hope to do that over the course of the next multiple days. I'm not the best one to talk about this impact but I know that we are we have been seeing some failures on the PR 5206, which is Jenkins 69 oh two about SSHD bump. From what the 72.6, and it seems to break a few things and so I just like two seconds ago marked this as a regression I think correct me if I'm wrong. But yeah, I'm not absolutely sure I didn't have the time to dig into it. But yeah, I'm not sure why it was not mentioned more by people as a regression. But it seems to be one. If you look at the PR itself, one person said that he had to he or he had to go back to the to the 283 before the work to get back back to normal. So, we are still assessing the impact and what is possible on the side but yeah, I'm not sure what is the last radius on this one seems to be. So what's this and that's why we have these candidates because we still have two weeks to make adjustments. Exactly. I mean my point is that I'm not fully fully sure yet but I was about pointing that I didn't tell you today. I'm not on the PR team, you know, typically team and Rehan to see what they think about back pouring this one. No, but pouring actually there's no fix. Thinking about, well, making for potential. Okay, talking about the SSHD bump. Yeah, that seems to be, I had an evaluation in Jira. Yeah, I just looked at this yesterday. Yeah, I think it's, it does seem to be a regression I think just affecting people using RSA kits only. It looks like it's best fixed by just updating SSHD again. They've published the tag that has the fix that doesn't seem to be on central so maybe it's still being held up and release candidate status somewhere I'm not sure. Yes. The SSHD they have a process is voting so similar to Apache. Yeah. So it may be something like one week before the release and before the station actually release. And if something is needed you can drop a message to the developer mailing list. SSHD has another mailing list and you can ask to facilitate or we can stage it on our local infrastructure is really needed. I mean it might make sense to revert this in the LTS branch. I don't have a strong risk to get it guys. Yeah. Yeah, thanks all. So anything else about the release candidate. Okay, let's move on then. So that means we still haven't finished news. So a quick update. So we have been in contact with Amazon to renew our sponsorship for AWS. We've been quite successful about that. The Jenkins port, Olivier, Mark are in CC. I don't know if as well, maybe not. But yeah, so what currently happens, we have agreement from AWS to consider to continue sponsorship. But there is still open concerns about how our infrastructure is organized because our Amazon account is still owned by cloudies. And we had issues with that because we're brilliant on AWS, not the piece, but so we discussed our options and we're good. We would rather proceed with the touching the Jenkins entirely to the new account and initiate the transition to CDF so that we could do basically what we did with Microsoft infrastructure before and we could close this topic altogether. So right now. I think the big win there is that the cloud because cloudies owns it only cloudies employees were able to access it and if we get it migrated, then the entire infrastructure team can manage it if they want. Yes, that's right. But on the other side, I want to add something quite important. This means that we know this means once we move that account to the CDF will have to pay attention to the sponsoring because in the past when I mean clubbies was paying for that account. When we needed, which was quite useful. And so once we move that account to the CDF. I'm not I don't see I mean I don't know yet how it will work because we have a limit of 10,000 per month that you can spend on infrastructure. So we'll have to pay attention about the costs of that as that account as well and we may have to reduce our infrastructure. Because we already when we moved Azure account to the CDF we had to reduce from 20 K per month to 10 K. And part of the workload was moved to the Amazon account. Last year that that account was sponsored by Amazon. The sponsoring is renewed this year, but yeah this this account run critical services for the project. So you need to monitor that we also need to have someone connected as a credit card. Hopefully it will be the continuous delivery foundation. I raised the ticket to the CDF I have meeting this Tracy tomorrow, and then this CDF talk on Tuesday, and we'll see what we can do, but yeah right now is we just started that. Yeah, with the monthly given is right until we move in the detached completely from called this. It will be difficult to have community contributions there in terms of management. I do know that Damian has reached out to to Gerocian, I think I'm going to add the board and Olivier to that thread. So that, but that might help keep your costs down to if we can spread out sponsorship for more clouds. That would be nice because then we reduce the risk on the one I mean once once one one cloud provider removed sponsoring that just reduce the risk. Keep in mind, maintenance costs because maintaining multi clouds setup is not exactly cheap. And you also have limited bandwidth infrastructure team. I mean if it's just like the spinning up the CIA Jenkins machines that would use cost because you won't need as many of them on one cloud and that less maintenance than critical infrastructure and communities clouds and stuff. That's that's a difficult balance to find, because monitoring the cost also take time and sending and communicate with all the people to find ways to reduce the cost also take time so. But yeah otherwise that that's a really great news. Sorry. What if we had infinite money. Like what we had to what we used to have with Azure for four years. That's like, yeah, you go somewhere and pick it up and show me the money submit. It would be nice. But yeah otherwise with Amazon account that's really nice because that's quite a mean. Okay. Anyway, it was quick heads up, but we are working on that. The next topic is from Daniel about trouble with three note IRC. What do you like to speak about that. Yeah, so this kind of exploded today. Our IRC channels are on the free note IRC network, which is sort of hosting quite a bunch of open source projects I think Linux some Linux distributions PHP all of their IRC channels on this network. And it looks like there's been kind of a I mean it's described as a hostile takeover of the network where previous where the previous admins are being forced to hand over access to the infrastructure. And I mean, I provided some links in the notes and it basically has this page that all it has up with links to basically the two points of view about a dozen or so volunteer staff have resigned today. And it's difficult to say what's going on really. It's just something we probably should be aware of those staff who have resigned are starting a new IRC network. And of course, if we need to migrate elsewhere, we may be able to consider other options as well. In additional alternatives to IRC, just you know something to keep in mind, I hope that there will be a clearer picture over the next few days and weeks. Perhaps we can look at what other projects with perhaps a larger stuff that can deal with drama like this, decide to do or not to do and do something similar. So that is the list here. And here are projects that are still going to get what number projects announced and that they would be moving or whether they really would get to be seen. I mean, to that note, I think it's the same as when Microsoft over get up everyone was quick to jump ship and then some people did and some people didn't. I think the only real concerns are private issues or private channels, which as Daniel pointed out, are not heavily used anyways. So I think the rest can. Jenkins security is located in private RC channel. Yeah. And if you go on security, we also have RC bot running, which has access to our need hub. What was that. Well, I didn't hear you said the what has access to Jenkins at sea boat. Yes. So if you want to disaster snuggle with somebody exploiting access to this boat through free note access and wipe out our repository. Doesn't have destructive commands. I already renamed Jenkins. Jenkins repository once. Yes, renaming a repo is not destructive or like the only destructive action that exists is deleting a g-rock component and moving the issues elsewhere. Everything else is non destructive. So I think what I was trying to say is I think this is a high priority issue, but as Daniel pointed out until a little bit of the dust settles a bit. I think it's a little premature to say hey we're definitely shipped to this of that or whatever thing. And the only ones that were critical were cert. I think certain shouldn't. I don't know. Just delete or move to another channel because the honest outside my link is that there is not that much activity. Right. Most of the activity takes place in JIRA. The search general hasn't been really active recently. Something for us to be mindful that from now on. We probably should move private direct chats. I think the queries I think they are called an IRC elsewhere. I don't think you should have those. Okay, so on the high level, my vote is still Gitter. It's our matrix is centralized on that, but I think we need to spend time to investigate and make a decision, but I would like to, you know, as a recurring topic for me is to standardize our things. We're a little bit everywhere we're spread out very thin all over the places. Yeah, maybe it's something we really needed to discuss. So regardless of free note, but you know, is another cool function. And since we have progress with this course, maybe it's something we could actually try moving forward. This course is English replacement, not the chart replacement. Yeah. Yeah, but for many, our queries in Jenkins, it's basically when I bought for the majority of users. It's the best again, even if we, you know, I agree though, I don't think this course replaces chat. Yeah, but we have IRC, we have Gitter, we have Slack now in many subprojects and CDF. So maybe getting rid of one of them is possible. Yeah, but yeah, but there is a difference because in the case of IRC. I mean, except I mean, we already use Gitter by default in most of the projects and we only have IRC for Jenkins infrastructure. Jenkins hosting as well, I think. Yeah. And it's only, I mean, that's only concern a small group of people. So if you tomorrow we decide to move to a different RC channel or use something else. It's not like busy. It's not like if we have to move the committee from the Jenkins Gitter channel to somewhere else. The Jenkins channel IRC is still pretty big. Yeah, definitely. Yeah, but you always have people staying on our see whatever you do and and I mean I don't see it as an issue with people want to stay in the Jenkins channel just to discuss and ask questions, as long as other people answer questions. It's not officially the main communication channel anyway. But it is listed and that's my point is we should be very clear on saying this is where people will be there available to help out if people do other places that's fine, but we should be clear on this is the official. I thought that we officially moved to Gitter for the. The end. So we basically said that whatever works. And the current is that the community sector so many channels. So considering them doesn't seem like the worst idea because for example this course could replace some million pieces and I believe some chat chats, because many chats actually operating the coin a mode and discourse is quite good for me. Yeah, let's see. It's just on the topic we need to result now and somebody wants to drive at it. Yeah, can we can we please move on. We are already passed off. Yeah, I agree. So, any closing words on that. Okay, so. We have several open pool request. Actually, we have on the pool request which is related to roadmap content, we can take a look at them quickly. Because again, I haven't submitted my pool request I was trying to planning to do. So, one update is from current behalf on my cloud native seek. And basically what they are cloud made cloud events support. It's a G so project this year. I believe that we have a consensus that's reasonable to have. Then the rest of the client flagging. So this one is a bit more complicated because we already have two interests on the roadmap about tip tone. To be honest, I'm not exactly sure what is the difference and your car is not here today. So, for the phone we already have. We have pipeline build steps, which was basically a client plug in alpha. And the repair and they can move it to them, and we have tick on the client's execution engine, which was making a jinx pipeline pluggable in terms of pipeline execution engine and making a tick on the first class citizen. Well, it's technically possible not to see it to be decided, but the idea was like that. And the question is whether we want to add another topic for tip tone because he basically duplicates this one, but this another description opinions. I'm not sure what your ask is, like it sounds reasonable to me. So, yeah, if you had that we will have basically three tip on items. Each of them will interlock with each other. So it might be a bit complicated. So, I think all like what you said is that the tecton tecton pipelines build step is, in fact, the tecton client plugin. Yeah, there we go so. So isn't that really saying that the thing that she added for tecton client plugin is already there maybe we need to rephrase it to be tecton client plugin. I don't know if the tecton pipelines build steps I don't know if that would have helped her realize it was not it was it was a duplicate because it seems to be a duplicate I don't I don't see us adding duplicate entries into the roadmap as a benefit right now. Yeah, and so there is some data roadmap. So we discussed at the last meeting. And right now these features do not seem to be important enough to be put a separate roadmap interest. So maybe I'll just take action item to remove this part play and replace right. Right so because for me tecton client plugin is, is more explicit than the tecton pipeline pipeline build step, just for my benefit, but I'm okay either way. We're creating this roadmap I think there was no tecton client plugin. Oh, got it. Thank you. So it was a bit well ago but yeah, it's basically what we have started. Okay, and the next is docs and platform roadmap of this maybe you would like to speak about that. Yeah, so in the February 2021 contributor summit we had ad site search was one of the items listed. I believe it's done and released for both the plug in site and for Jenkins that I for www.jankins.io and Jenkins on Kubernetes. We started it, and we've got another person who's working on it now during our docs office hours, Asia and Australia time so I think those are reasonable updates. Yes, speaking of that, will we need to create LFX mentorship for this right now the person is doing it without LFX mentorship but we would like to like to consider that for some time in the future. Our idea was September ish that we would consider doing a sponsored program. Yeah. You'll right and sorry the embarrassment for Sheikot Africa is it's already done, but we had agreed in February as as part of the presentation that it should be on the roadmap this is me doing it much belated. We don't have much problems with it. So any objections. Okay, so all of it is straightforward so we can just say that. Okay. And we need to spend more time on repanning the roadmap because it's a bit dated. We still have some items from February contributor summit we didn't put there we have another one. And together with Mark, we also have a talk about how we did the public drinks roadmap that's in the corner. So I guess we are in the hook to update this roadmap before we record. Um, for calling feature is there a reason that those roadmap items are not tagged for the board. The PRS. I don't think I've seen. Yeah, I'm just like, we have auto reviewer on drinks IO that says, this is a board and this gets assigned to board right. Yeah, I guess it has broken at some point because I believe that could also be a contributor to review that, but you're right that now it doesn't happen. Yeah, so I think that I mean, I don't think this needs to be discussed like the roadmap is necessarily need to be in each meeting. Yeah. Again, you can assign it to me or anyone can submit one line for request. Yeah. So, yeah, I think that we have agreement I will follow up with this apparently I'm not locked in from Firefox. Yeah, I was testing this candidate from Firefox. So, yeah, let's move on. So Jenkins job process updates. So there is a long discussion. Basically, we agreed on the most of the things, I believe. So there is a pull request submitted, which addresses the agreements, we had a few iterations with Liam about how things should be working that etc. But I think that basically it's ready to go. There are a few important changes. So we agreed on terminology updates. So instead of sponsored reviews champion. So basically, somebody who drives the initiative, without the practical changes in how it relates. We also replace the review process. So we introduce Jenkins community as an entity presented by our open governance process. So, yeah, basically what we have discussion on the million keys consensus building and voting to the governance. If needed, or if there's no consensus, not even spending time on the meetings. So, yeah, basically the idea that this approach replace the day failure be the effect delegate, which was the biggest bottleneck in all our current jobs. We also introduce advisor role. So the role for advisors basically provide consulting this role is optional. It's basically how sponsor works in Java Japs. So it's an experienced contributor who just helps the job to happen. If somebody less experienced is willing to submit a job and go through the process, but it's optional. So basically we reduce, we remove BDFL delegate we remove BDFL as this unique entity and be an optional advisor, but optional. For example, if Jesse is the most popular author of Japs. If he decides it's another job, then I believe that you wouldn't need an advisor. Jesse has that. And also, yeah, there is open question about what we do with BDFL in general, because you're basically BDFL was only used as a karma in Japs one. What's the other games introduced and BDFL from the very beginning, even when it was a thing in the Python community, etc. Now I'm even more against what happened with this role. But right now we haven't received the response from Tiki whether he would like to step down as BDFL so that we move for this role for good. Yeah, Tiki would still remain Jenkins creator, Tiki will be managing this government board member, etc. And BDFL is just getting rid of one of the roles which does nothing. So question to both members and to contributors who work with the job process. Does it look same to you? At the moment it was mostly collaboration between me, Jesse and Lima. Yeah, any feedback is welcome. I need to do more detailed review like I would like to review it to think about it because I need to submit the JAP to proposing Java 11 as default. Yeah. It's a very important item that since we have a synchronous process, so we can build a consensus and even the strong consensus that we are fine. We agreed that we would have seven days to view period of the call for final feedback, so that if nobody shows up, we just merged. We have seven days in the process for any JAP acceptance, even a very strong consensus, but while taking our current situation when JAPs stay around for months and years without actually being assigned to BDFL delegate, I think that would be net improvement. So if you have any other ideas how to ensure that everyone had an opportunity to voice the opinion, please comment in the discussion. But yeah, right now, I just try to do it in this way. On the call. Yeah, there's been a lot of updates. So there is spending thread. There is one open questions. What are we doing with historical change? And there was written opinions because some people think that we should clean them up. Some people think that we should keep them. So, from people on the call, are there any strong opinions? Yes, but I don't think it makes sense to go into detail. So everyone, please go to the mailing list and comment. Yeah, I already commented on the list. Yeah, let's do so. Yeah, proving the remaining terms, we still have a number of open terms. Basically, we didn't do much progress about the past two weeks. It's still something on my letters, but yeah, there is nothing to approve right now. We still have terms like Jenkins controller for etc, where we need more feedback before we accept that. So, again, just moving on, but this topic is where we definitely back in the original ideas, because none of these terms seem to be good at the moment. So, yeah, maybe documentation seek health mark. Oh, yeah, Daniel says that everyone needs to review his PRs. You mean the Jenkins core ones, right? I mean, all of my PRs, but in this context, yes. Yeah, so just request the reviews from everyone on this call. I think that it would be fair. And yeah, let's try to get it over the line because, yeah, terminology now is definitely something you would like to progress until the next push event on May 29 in the developer man increased again is focused on terminology now. But taking the activity at the moment it seems that we won't participate in this and officially. So maybe it's a question to bodies. And for now, but yeah, right now it doesn't seem that we have organizers to run this event. This is how commit push thread somewhere here. This is the 29th so it's a Saturday. And yeah, I guess everyone has other things to do on Saturday. Okay, but yeah. Okay. So let's try to get this over the line. So yeah request from inclusive naming initiative about health is naming inclusive naming marketing promotion. The contributors have joined the included me includes the name initiative including this lock meetings, because you may have seen that there is a lot of requests happening right now. So just to share some insights, they're called this and this is sometime in cleaning up and also the rather contributors so I created terminology cleanup project, just that there is input request and you can see that we have almost 70 recent requests. So, yeah, and people participate. So I think that taking our history and decisions we made in August. It would be nice if you could participate in health vision. The name initiative. The moment we are looking for some more repose promotion and maybe having an interview with Jenkins project representative. So, I think that all is reasonable.  I just don't have the balance to take on anything more right now. And I think we should identify someone outside this group. So I was thinking about just inviting Alex, so since he was leading the effort this summer. And he is an author of the blog post. So, if Alex would be able I think it would be great. But again, I'm not sure with this case of legalities days and Alex. Yeah, also have a lot of things on my plate. And I think for Mark, I believe, for the university season, etc. The villain is also busy from what I know. She's a typologist she can join with this meeting. So, yeah, maybe we might actually must actually send a public call. But I think that it would be important for us to participate in some extent. And separate related topic is actually about officially joining the inclusive naming initiative as a project community. So just so there is inclusive naming. Just to provide some feedback it was basically started by CNCF and a few other companies. So, yes, it's a main facilitator now so Priyanka Sharma is GM and CNCF and also one of the leaders of this project also you know many of you know Stephen Augustus is also one of co-founders and many other contributors, then get Cisco, IBM, both of them like Jenkins contributors and Red Heart. And what do they have they have related projects like conscious language and technology by Kubernetes, etc. So we can easily just that Jenkins there by Jenkins community or whatever. There's a lot of knowledge in Jenkins. So this looks straightforward. And I think that we could do that. You also need to give me the landing endpoints we have some in advocacy and outreach stick. But I think that we actually aggregate and that is content would be still beneficial for Jenkins community. Participating in the initiative officially. And would it make sense for us to join this these etc. I am always I'm always worried about taking on more responsibility without finishing the stuff we already started. I'm same with Kevin. If we can find someone else we can drive that that thing that would be really great. But we, I mean, we already I'm driving the naming. So after Marky and Alex stepped down. Yeah, I inherited it so basically about the implementation it would be rather me being called this like work. It's a lot of questions about feasibility whether we want to happen. It's not a big deal in terms of time. At the moment I would personally like to pass. I mean, I think it's a good thing to do. But I am so concerned about how many projects we have half started. I don't want to advertise the fact that it's like get people say hey look Jenkins is starting this progress I rather say hey we're done this progress and then add it to the list. Yeah, but but isn't this one. See I'm the other direction with this one because this is a project we've already started and all it's doing is providing another link to our terminology update. So I don't this particular when I don't think adds any significant burden to us that we don't already have. My, my, I'm just wondering if we could maybe reach out to one of the people who have with the with the naming renaming so maybe one of those people can step up and help on that initiative. So and currently we work with several contributors and so we can cruise your name initiative angelic job at current target. So they joined already the slugs that we've been active because for example three here created some tools for discovering terminology on screenshots. Then we have some stories to share about governance how we approached the vision making in a big project. So, just by sharing the experience we already contribute to this initiative and I don't think that there will be be covered. I understand the given spawn as well and if you could find someone who would take leadership, maybe. So do you noted. Let's see. So I guess for that we again public call. And the same for CDF so for CDF there is also a list of members, I will be bringing up CDF joining because CDF over the course of naming, et cetera. Interoperability seek and terminology cleanup and that project. So for Steve it makes sense to join this list. And for CDF it's actually free. Because, yes, they have created an inimity, because of the initiative and they are still defining what will be the membership piece, et cetera. The membership piece seem to be a bit high at the moment, but for the CDF as a nonprofit it's free. So maybe CDF will join and maybe we will get some help from the marketing team in terms of promotion and related communications. I don't want to have Jenkins as a showcase of inclusive naming cleanup, because firstly, we are quite better than inclusive naming cleanup my humble opinion. But at the same time we are working on that so I think that being presented there would make sense. Okay. Anything else about that. Okay, closing time. Should we just vote on adopting the subproject because it seems quite straightforward. I thought I was already done so I'm on board with adopting it. Plus one for me. Plus one to vote on it and plus one for me that vote to approve. Does that mean that you would move the stapler git repository to the Jenkins organization or we keep the stapler under the stapler organization. I didn't provide it but the Jenkins governance would apply there officially. And your current it's Daniel and JC is stepped out means. So JC is already on board. I believe that Daniel hasn't voted. I mean it makes sense to integrate stapler into the Jenkins project. If KK is okay with that I don't have a strong opinion on keeping the org separate. We could do it fairly cleanly by by just keeping the org separate and you know adding a few more contributors as admins and then we're done. Yes, but if we keep the org we need to throw out a bunch of folks who haven't contributed in the last decade. Because it seems weird to have these, you know, all the cons around that's. So what we will be definitely doing is moving idea stapler plugin, because I believe we have a consensus about renaming Jenkins plugin, because nobody else uses stapler enough to really need integration with intelligence idea. So that ability if you have a consensus on the mailing list, or if somebody is a post the same happen to this means plug in that means plug in is already within the Jenkins, I give up organization. So basically, they will be under the Jenkins rule, whatever happens. But you're for stapler, I think that you're moving repositories rather implementation detail. So the step that anyway goes to kind of our tick part of our sub projects. I mean, as discussed in the minute, he's a new efficient recommended for using outside Jenkins. So, well, basically it will be just our heritage. And as I said, there is no practical way we would ever step from Jenkins. I guess it's a small coding exercise for anyone, if you want to try. But yeah, so I think it would be natural if we just take it all life each year. So, just, then you'll listen, you think that key case approval is a must right, because key key belongs to these contributors who haven't contributed for a while. And it's kind of his project in a sense, if if I were, if I were the men of a repo in Koska's namespace, I wouldn't move it out there without his approval either. And this is not that dissimilar to me. Okay, I agree. So I'll try to get explicit approval from Kiki. Yeah, we're losing people. So do you want to press it with other topics or do you want to shut down for now? I think we can shut down for now. Yes, so what do we have the placating program runtime just let's try to get the progress in the mailing list, because it feels like the job is almost done. The process is almost done. So we should probably push it forward. We have issues. Yeah, we can keep discussing it in the coming, but I don't think that there are blockers for experimenting. And the friends of Jenkins, there is no hurry at all for that. And again, we can discuss in the mailing list. Again, I don't know if policies. I don't know if it's been time meeting. So, thanks everyone. And yeah, thanks again for your time. Maybe we need to switch to weekly meeting so whatever, but hopefully you won't be have so many topics in the next two weeks. Yeah. Last but not least, don't forget about configurator summit. And if you have ideas about agenda topics tracks, please comment there. Thank you.


To you guys know where I'm coming from, let me catch you up on the very brief story. 2002, I was 20 years old, I got my real estate license. Made a mill before I'm 23. By the time I'm 25, I'm bankrupt, sleeping on friends' couches. Went back to roofing houses, working on an oil rig. I read 100 books over a two-year period. In 2008, I was laid off from the oil rig and got back in real estate. That's when I started building my business on people, not deals. 2010 was the BP oil spill, which was a mini recession in my market. That's when I tested this theory out and I made 50% more money. I went from 100,000 in 2009 to 150,000 in 2010. That was my aha moment. That was when I thought to myself, I've got something really big, really special. From then, it took me till 2014 to build up my business to sell in 100 properties a year as a single agent with just one assistant. I was the number one remax agent in Alabama three times and I've sold over 100 properties a year every year since. Now, why did I get into coaching? How did that transition happen? In 2014, when I sold 100 properties, I thought to myself, is this real? You know, I made it all before and then I lost it. Is it gonna happen again? So I was scared. So I just kept grinding, I kept pushing, I kept fighting. I sold 100 properties the next year. Then I sold 100 properties the year after that. That was 2016 and after three years of selling 100 properties a year, that's when I decided, okay, I think I have something I wanna share with the world and I decided to write a book. And if you'll notice, I got in the business, I made a meal, I lost it all, I came back, took me six more years to get to 100 deals a year. Then when I got there, I waited three years before I decided to try to share anything with the world. And a lot of these coaches are out there that have been selling for two years, sold 19 properties and they're selling courses. It's coaches like that and it's coaches that charge that really don't have any business charging for coaching is the reason why I got in to coaching and the reason why I'm a free coach now in the beginning of my coaching career, let's say in 2017, I started out coaching. It was really cheap. What I wanted to do was create an alternative, a much, much cheaper alternative. Okay, that was my thoughts going into it but after about six months, I realized that that was not the best business model. I was losing so many agents. I would have 300 agents sign up for a webinar, a hundred would show up and only one would sign up for just 20 bucks a month. And I thought, well, there was 300 people there that really wanted some help. A hundred really wanted some help and only one took action. So I know my webinar skills probably weren't the best at the time and that could have something to do with it but at the same time, I wanted all 300 to succeed and that's when I decided I woke up one day and I thought, wait a minute, I'm not running my coaching business like I'm coaching my real estate agents to run their real estate business. I'm telling them it's all about the relationship, not the deal, but here I am trying to charge them a hundred, 220 and there was a disconnect. So I went to my 200 paying students, 10,000 a month coming in automatically.  I'm about to release that to the world. I'm gonna start teaching it for free and guess what? I'm gonna make it even better. And I gave them so much value that there wasn't even one of those 200 students that asked for any money back. They all cheered me on, which was amazing to me. I was expecting people to get mad and to start cussing me out and leaving bad reviews but they didn't. They cheered me on and they said, Ricky, you're right. If you go free, you can really make a difference in the industry. And that's what I'm trying to do. My overall goal with Zero to Diamond is to create a free coaching program that brings more value than any coaching program on the face of the planet with the objective of reducing the failure rate in the industry. And it's happening. I get messages every week from agents who were about to quit a year ago, six months ago, last month, and they ran across my content, started using my free coaching program and now they're getting listings. Now they're selling properties and these agents were about to quit the business. That's what they say in their messages. I also have a huge passion for when the market crashes because it's gonna inevitably happen. And I want you to know that closings continue to happen every single day. Please don't be scared of a market crash. Know that there'll be a temporary downturn. Your business will suffer very temporarily, maybe a three month period. And we're gonna be back to business as usual. We're gonna keep making our calls. We're gonna keep helping people through the crash. And closings are gonna continue to happen. All the other agents are gonna get out of the business but Zero to Diamond members are here to stay. I've also been doing events all over the country. I went to Brazil and was the keynote speaker at R4 in Brazil for 800 Brazilian remax agents. It was an incredible journey, incredible trip. But I've been all over the country and I'm setting up events all over the place. So you can go to zero to diamond.com backslash events. If you wanna see where my next events are and to purchase tickets, I would love to see you guys out there. Please come up and shake my hand and take a picture because I just love meeting you guys and hearing all the stories. You guys are motivating me. I just want you to know that if it wasn't for you, I would not be still making videos. I would not be coaching if it wasn't for you guys. I'm posting all your results in the Facebook group, all the comments, all the messages.  Thank you guys so much.


Meanwhile, supporters of the presidential candidates of the All-Progressive Congress, A.P.C. Bala Ahmed Tinibu and the ex-presidential Ed Reno Mocray Monday clashed at the Chatham House in London. Recall Tinibu was billed to speak at the House on Monday as regards his presidential ambition. Now, prior to his arrival, supporters of the party converged current placards in support of their candidates while awaiting his presence. In a viral video, Mocray could be seen joining the crowd shouting Tinibu while supporters of the party chanted for precedence.


So I'm Alexis, and this is Living Energy Farm. The purpose of Living Energy Farm is to create a small village scale model that runs without fossil fuel and to try to do it as cheaply and simply as possible. So instead of asking the question, how do I make renewable energy suit all of my needs, we ask how do we adjust our lifestyle to live within a modest renewable energy budget. And we want to create a model that can, as much as possible, spread all over the world, including to a lot of people that aren't very wealthy. We tried to build a better solar energy system using off-grid batteries, standalone solar electricity, and we've developed what we call a DC microgrid. It's worked out really well. We run motors straight off the solar panels. We call that daylight drive that allows us to shrink our battery bank way down so we can use a small battery bank. We use nickel-iron batteries, those last forever. We have a lot of other projects. We've been using biogas and expanding that biogas for cooking, and now we're using biogas to power small tractors. We're also developing better grain harvesting equipment. Basically anything that a small, low-income farmer would need anywhere in the world, we're trying to develop it, and that's what big corporations don't do. And a lot of people who try these things over-engineer it. They try to do things that are big and complicated. We're trying to keep it as simple as possible but still be effective. Regarding solar cooking, we have several kinds of cookers. We use a regular solar oven, and you can make those, or you can buy one. Sunoven is a popular brand in the U.S. They work, but they need very good weather. Only in bright, sunny, warm weather do those work. We have a parabolic dish. It looks like a little satellite dish. That works a little better. It's a little better for slightly cloudy weather. They do work, but we found that we could only do a small fraction of our cooking with those. The weather needs to be pretty good. It needs to be warm. You need to go out to the cooker, which when you're trying to cook for a dozen people, having to run around between different solar cookers is a bit stressful and tiresome. And then we, about nine months ago, we discovered insulated solar electric cookers. Isak's first developed by Pete Schwartz at Cal Poly, and now it's an international effort to improve them, uses DC electricity off of solar panels into insulated cookers. And the insulated is an important part of that. And they are much, much more effective. They've allowed us to cook now. 80, 90% of our food now is solar electric in the summertime. And even in the wintertime, it's still quite a lot. So if you have a toaster, like in an ordinary house, and you look in there and you see those little glowing wires in there, it's called nickel chromium. That's what it looks like. It's very, very cheap. This is our simplest burner here. And we take the nickel chromium and we just wiggle it back and forth. We lay down some concrete. So that is connected directly to the solar panel. There's no fancy electronics at all. And then you put it inside of an insulated box. And then that sits under your pot and makes heat. We wanted to start with the simplest, cheapest, easiest cooker to build. So we came up with the bucket cookers. We call this pearl because it has made with pearlite. If you look down in there, you can see the circle, the nichrome wire and the little circular burner. This is a metal tube.  That's a white material. You often see it in potting soil. Pearlite insulates moderately well and it has very high temperature resistance. Now for this kind of cooker, we have to get a pot that actually fits in there. This is called a bain-marie, but it slides right in there. You plug this, again, straight into the solar panel. There's no fancy electronics at all. Then we make a lid. So this cloth right here and this cloth right here are flame-resistant cloth. This is not wool or cotton. This is what's called a welder's blanket. This is called aramid. We use a little bit of rock wool around the top to give that. We want to make kind of a gasket, something that seals a little bit. We put that on there, boom.  It cooks somewhat slowly. Now, this particular one was made to work at 100 watts, 12 volts, but you could put 200 watts, 300 watts. You can put different wattages, different voltages. The smallest cooker like this with a 100 watt panel is going to take all day basically to cook a couple of liters. So you would cook dinner with this. And we found that it's often better to bake rather than boil just because you get rid of the thermal mass of the water if you have a very small cooker. But now we have developed these in many different sizes and many different configurations. We make the box cookers, the Roxy's. So the burner would sit on this one. Now this is a sheet metal cover. This is made with metal fabrication tools and that sits on top of that and there. Roxy box cookers that run up to 1400 watts. When you're at that level, it will cook as quickly as an ordinary oven. We can cook three meals a day on these. You can cook at 9 o'clock in the morning because the big advantage of these cookers, it could be very cold outside. It can be partly cloudy and you're bringing that energy in and putting it inside of an insulated box. They work far better than any other solar cooker. The big challenge is with any kind of traditional cooking meaning electric gas or even firewood, you cook really quickly.  So the biggest challenge is just getting people to plan ahead. So instead of coming in at 5 o'clock to cook dinner at 6 o'clock and have dinner ready by 6, you start dinner at 2 o'clock. You get it all packed in the ovens. You let it cook and by 3 o'clock it's cooked.  That's our biggest challenge. Here's the interesting thing.  Our biggest cooker is tied into our high voltage system. Now our high voltage system at Living Energy Farm runs dozens of motors as well as our cookers, heats the houses, does a lot of different things and that runs at 180 volts. At 180 volts DC, we can cook when it's cloudy. Not heavy overcast, but mild overcast, partly cloudy, we can still cook and that's pretty amazing. But it's because of the integration of the DC microgrid, we call it, that integration of systems. Well, we have been doing this project for 11 years now and we have relied on solar cooking, firewood and biogas. Firewood's easy, it's cheap.  People of course use charcoal in a lot of places but charcoal throws away 70% of the energy content of the wood. So you can't imagine the cities of the world cooking on wood, it's not going to happen. We do use biogas and we like biogas. For us, the biogas and the solar cooking are very well, they're complementary. So instead of having a big biogas digester that can do everything, we can have a moderately scaled biogas digester. We do a lot of our solar cooking, cooking with the solar and then the biogas because the solar, you have to use it when there's sunshine. There has to be some sunshine, but the biogas, they can store it and then use it tomorrow. So we hit a long cloudy period and we can adjust the feed rate going into our biogas digester. And when we need more biogas, we can push more food into the digester or back off on it when we know we've got good weather and can mostly rely on the solar cookers. So insulated solar electric cookers and biogas, I think that's what happens after industrialism is done. After the fossil fuel and the natural gas are all gone, this is how we could live gracefully and still have something resembling a civilization, which is a mixed bag at best, granted. But it's a lot better than firewood. Insulated solar electric cookers will spread. I'm quite sure of that. It's so cheap, so simple, so effective. It's the best solar cooker on the market. You can buy these expensive vacuum tube cookers. They're fine, the big dishes, they're hard to make. They only work in good weather. They work in bad weather or moderately bad weather. Pretty cheap to build, pretty easy. They will be mass manufactured within five years. That will happen. But even then, if you want to make it yourself, you can make them. I mean, that's pretty easy to make right there.


Welcome back to Winner Home on Afternoon Express, the show where we follow three young designers as they transform three empty apartments at Val de Villes State into dream homes, using finishes provided by Plascon and Caesar Stone. And at the end of it all, we'll be giving away one of the completed apartments worth over three million rand to one lucky viewer. So for the next two weeks, it's all about the bathroom and today we're joined by one of our Winner Home judges for some colour inspiration. Denita's on the couch. Decorating a bathroom can easily go terribly wrong and choosing the wrong colour to paint the walls can ruin the common effect of the whole room. Here to help guide us away from disaster is the lovely Ann Rosal, Plascon's global colour manager. It's good to have you. Thank you. So let's talk a bit about this bathroom experience because I mean bathrooms are quite a difficult one to get put together. What are some of the no-nos and things that people are generally doing quite wrong when it comes to decorating bathrooms? Okay well if you think about it you start and you end each day in the bathroom. So when you walk into the bathroom in the morning you want it to be uplifting because it'll sort of set your mood for the whole day and at the end of the day you want something that's quite relaxing and calming so you can you know wind down. So beware of very bright bold colours. I mean you don't want to wake up in the morning and you know go to through the bathroom and you hit by this bright passionate red. You know you do want a bit of energy. If you want energy add some red accessories or whatever but beware of painting the walls all red in a bathroom or all yellow. It's just too bright and bold and it can go. That's sometimes when it goes horribly wrong. Yeah also when you're trying to focus there's like distracting to have on the entire room being so many different colours you don't even know where to where to be. What are some of the things that we can do in terms of choosing the right type of paint? What kind of colour should we go for? Okay well you want to create like maybe a spa like bathroom or relaxing all colours that really reflect well on your skin that's also something to bear in mind so you don't be careful. Yeah exactly so you look in the mirror and you look kind of greenish but you're kind of green wool so oh yellowy and you think gosh I might ill. I'm ill. So you want colours that have sort of a peachy undertone or pinky undertone that look good on your skin. In fact in our latest issue of Plascon Spaces magazine that we have out now we show you one bathroom and how you can totally transform it just by changing the colours of the walls. Oh really. So in our first one we show you just a plain old neutral bathroom which is great it's fine you know neutrals never go out of fashion it gives you that minimal look and very calming and relaxing and then our second look is when it really gets interesting when you add colour so there we have a grown-up pink called Savannah and pink is a very trendy colour at the moment as I said it's Pantone's colour of the year is rose quartz so it's linked to that so it's very trendy but it does look beautiful on the skin. Our third bathroom is also Pantone's colour of the year it's a sky blue they call it serenity we call it marmelo and you get a wonderful cool refreshing look when you paint the walls blue and it's like sky and water it just fits with a bathroom. Especially if you maybe have like more than one bathroom in the house it might be a nice one to have as a guest bathroom because if it is towards the beachy side of the world or if you've got a coastline a house that's a beautiful colour. It does it just it just fits the whole theme of the space and you know you really feel that water connection which is really good for you you know your soul really. And then our fourth bathroom that we showcase is one that's going a little bit different and we've we've used a military green called Starlight Express and it's really quite different but when you add plants and stuff it's almost like a no-acess so you know it's very relaxing calming green is very stress relieving so it's a great colour also for a bathroom and then it's up to you to choose which colour you would like to have in your bathroom. Sure nice ideas I think people are always stressing because bathrooms are one of those spaces where a lot of damage is potentially coming in there with water damage and coming down dampness is also a big one that that happens. What kind of paints can we use to protect our walls what are the hardy hardy paints that we can use? Good paint okay well enamels have been traditionally been used in bathrooms because they're hard wearing they are heat and steam resistant they're chip resistant they're anti-mold but we've all got to be eco-friendly. It used to be enamels you'd have to wash your brushes with turps and turps and all of those things are not great. Now it's fantastic we have a water based enamel called Valve Glow it's much more eco-friendly everything is water and it is just as hard wearing it's mold resistant it's heat and steam resistant it doesn't yellow you know the old enamels you painted white and it would go yellow after a while these stay white so it's great when new products are eco-friendly but they also as good as all the products so definitely go for a water based enamel in the bathroom. I like to take a lot of inspiration from the hotels because they really like to decorate their bathrooms and make them interesting and unique and a lot of them are using things like wallpapers and really getting wild with those sort of bathrooms what are some of the techniques we can use to to just really uplift our bathroom? Well wallpapers are beautiful but I must admit I'm one of those people who just cannot take wallpaper in the bathroom but a lot of wallpapers actually are paint finishes if you have a look at them they're like painted strokes and all of that and they're doing wallpaper we'll do it with paint okay there's an amazing amount of techniques you can do with paint so rather use paint you know you can do easy stripes or you could do a stencil in your bathroom with a metallic or you can do something really exciting and do a mural in your bathroom so that really there are endless possibilities of what you can do with paint to fix in the bathroom and what I love most about having you in the loft is that you make people so excited about just experimenting with the houses so I'm pretty sure everyone that's coming weekend is definitely going to be playing around a little bit either in the bathroom or in any other room of their house just to use color and different types of paint so thank you for joining us it's such a difference thank you remember you stand a chance to win a golden ticket into the winner home final draw when you buy a Plaskon product an sms the word Plaskon the last six digits of your barcode and your full name to 32979 visit Plaskon.co.za for more details on how it all works as well as much more inspiration, color forecasts and how to go about choosing the perfect colors for your bathroom. Well some really valuable advice there we saw on Monday that our design contestants didn't score particularly high for their use of color will that all change for their bathrooms let's see what they're up to. Minent Len Tully's bathroom is coming along nicely and he's choosing a soft neutral shade to complement the dark tones in his design. I'm picking my paints for my bathrooms I'm definitely going for an off-white I'm still stuck in between choosing whether I'm going for the worn wood or the silver bird I'm going for the off-white because it's going to help make my room bigger than it seems I'm also bringing the garden city that I have in my guest bedroom which is part of the concept I have to keep the consistency without throughout the apartment. Also busy at the paint stage is fellow contestant Joanne Fenter who is continuing her spa-like theme into the serene bathroom. So I'm using a white flask on valve aglow because my floor is going to be very dark and I'm going to have hint of light oak and concrete so I think white will work perfect with the space. I'm using valve aglow from Paskon because this is a wet area and my bathroom is looking great already. The contestants know the importance of choosing the right product to protect their bathroom surfaces and Rudolf Joanne has made a bold color choice. So almost done with the first coat here I think it works well with the tiles I've selected and remember that with my white tangerine fittings my 50% neutral 50% black stain on the floors everything will pop against this color and I think Paskon will like that. This is not the only color I'm going to use in this bathroom so you'll have to wait to see what the surprise element is. Well from today you can head over to privateproperty.co.z and vote for your favorite bathroom and by casting your vote you stand a chance of winning paint from Paskon to the value of 5,000 rand. You will also automatically be placed into the grand prize draw where you could win one of those completed apartments at Val de Vie with more than 3 million rand. Winner Home is proudly brought to you by Private Property in association with NED Bank. We'll be right back.


So, if your F1 visa interview is in the next 10-15 days, then we have something for you. This is a self-preparation course and F1 visa video course, which is about 3 hours of high-value content which covers all aspects of interview preparation. So we have modules covering all the interview questions, templates, sample answers so that you can structure your answers, plus we cover all aspects of interview preparation like the document checklist, what to wear for the interview and we have included lots of real visa interview experiences and student experiences as well. So this is a self-preparation course, you can prepare at your own time and pace and it's going to be a great value add to your F1 visa journey.


What is good yo welcome good morning we're here we're out here and it's still spinning yo my energy's maxed out what's up this is your first podcast actually and those that are listening to the podcast for a little bit now the daily ones we're on video today and I'm not just any video brawl I'm in that 4k I was gonna put my phone up there and even though I think the phone actually does iPhone X is 4k but I couldn't even find the little phone clip so I got my camera rocking don't get used to this I'm trying it out on a Monday because I had that extra energy but I was like you know what I'll throw the camera on do a little bit extra editing and we're good so we'll see so those of it that those that have been asking for the video podcast it's up today go check that out and if you do like it I need you to comment and let me know because it's a lot of extra work than just recording my sound volume hitting post and that's it because of a video I got post production you get it anyway what is good my energy is maxed out like I said everything feels amazing I'm the people I've been talking to the clients that I'm working with it's just I think that's what's happening is that I'm helping them and it's I'm I'm feeling like I'm getting better at coaching and like when I hear their goals and people that are trying to max out their life it's just that shared inspiration that gets me super hype and also I know I get super hype when I'm jumping I'm not jumping because my hamstring I'm healing that up so when I'm not jumping it's not really exerting my energy my body's used to going a hundred and so I haven't had one of those like a hundred percent exhaustive days so it's just like ready to move it's like say you're in the primal stages of earth when you're chasing after lions or running away from them whatever that fight or flight when you're in that fight mode to the max then you go into that flight mode or whatever like recovery versus action I guess I'm gonna say and I haven't really been that going that hard in the gym but what I have been doing is something little every day so I've been working on my friggin toes to get the arches of my foot strong because jumping you need strong ass feet our toes should be like all spread out if you're listening to the video podcast which is a new update you like your my fingers are spreading and so like if you watch actually I really like those guys I'll move you on the Instagram they have a YouTube as well they talk a lot about all these little detail things so I'm working on that working on my hips working on my back and probably going to invest in a massage therapist I've talked to a few different trainers now and my hips are so tight that it's almost impossible for me to stretch myself so investing in myself investing in my health which is very important I'm going to do find a massage therapist I have a few recommendations get those hips worked on broken up so I can get flexible enough or move enough more enough mobility that I can keep maintaining it by myself where is this podcast going I don't know but you can feel it you can feel the energy it's how Monday we're gonna plan it out I haven't been planning that well but I have been super productive lately the only thing I'm behind on is these YouTube videos which is hence why the video's up I don't know if anybody's gonna watch this because my algorithms only dunking but I have a lot of videos to do I we took so much footage at Dunkamp I didn't vlog very much I had other people filming I wanted to be in the moment and last year was way too much footage footage it was stressful so I have the low-rim video with t-dub that I'm super pumped about the first time I ever met him if you haven't seen my Instagram by now I met the legendary t-dub himself and it was surreal to say the least I have some crazy footage of the very first time I spoke with him it was it was awesome and then I increased my vert so I'm gonna post a video but analyzing it a lot that I learned about my takeoff because even though I increased my vert from last year last year the actual attempts my footwork was terrible not terrible but I learned a lot compared to when I go for a ball simply put I stay way taller and I was trying to do that but I didn't realize how much I was collapsing on my takeoff so I think I can even jump even better next time I do a vert tech but my jumps are getting really well I also think that that same technique will help my dribble dunks and other than that I want to do a video about analyzing the windmill dunk and why I think it's the easiest dunk to do mainly because your center of mass goes higher when you pump your arms down if you're watching the video podcast once again I'm doing a windmill motion so yeah I got a lot of videos on the works I feel like those are gonna be super valuable if you're a dunk fan you're living at Dunk life to keep your technique going and also see the legend himself okay and other than that back on the grind haven't been dunking soon but as soon as I'm back in the gym I don't know if you should follow my Instagram if you want to know what I do daily because I post something there every single day of what I do and the last thing I want to talk about is what it feels like how the my body feels like the metaphor for all this energy and all the progress you make is that I'm trying to get the most lean I can be just because it's a goal of mine but also I think it's the best way I can to be healthy the best way I can jump the best and it feels like the more I do every day like a little bit of bird dogs like for your back those little muscles a little bit of hips a little bit of isometrics get that blood flow in there and when I do the isometrics for my hamstring and just that you hold that position where it's like flexing your hamstring I could I'm starting to feel exactly what muscle it's hitting and isometrics are like suck mentally like I hate just holding a position like a plank for 45 seconds to a minute so I'm pushing my mental side so tough and making it as tough as I can because I know that's a weakness and basically working in all my weaknesses and in the gym all I do is these things that burn like crazy and it feels like it's keeping my body always in that burning state so if you think of your metabolism and your skin and your blood is like a little bit of like burning instead of just like extremes of like highs and lows I have I do that still when I go dunk and then I'll recover but it's like I burn it at least a little bit every day like keep that fire burning keep it really churning and we're keeping that burning motivated which is morning and so that burning feeling also keeps my blood flow and I it pushes my heart rate a little bit and then at night I'm also sleeping better I slept really good last night I had a dream that I was in New York that I met all my friends in New York and everyone there was actually they were all going super hard of their goals that it was like insane like there was like bosses I had to catch at this minute and they left with like the exact minute so they get there I don't even know I almost miss the bus and then everybody was like it talking like this extremely fast and extremely motivated and I think that's just what's been on my mind but if I got to say anything before we get the frigging seven minutes ready start your Monday strong do the little things it gets the only thing that happens to me is I get overwhelmed with all the different things I want to do write them down do whatever you got to do or just have your priorities start just get a little bit going whatever but it feels so good to just make a tiny bit of progress keep it all going you're making progress we're in this we got a 4k frigging podcast now maybe I'll do this daily that's tough but let's all right have a good one to the loo stay tuned for YouTube videos please let me know if you like the video podcast so you're just cool with the audio because I don't want to do a ton of work for nothing all right have a good Monday stay frigging active to the loo


Hello there everyone and welcome. This is Melissa Armand. I'm looking here at CVS stock has just tanked tanked on news and the pharmacy stocks The drug companies are our tanking. I'm looking here just at the CVS right now though Amazon has retained a pharmacy license just breaking news huge news huge huge huge and here it is 310 Amazon reports tonight So not only does the stock report tonight? This is big news out for the stock coming out as well today Drug companies are tanking. Look at the move. The stock has just made. I Mean, obviously you wouldn't have known this just to be in this here unless you would have shorted this in a gap down today Which it did get down. Excuse me. Sorry stop to get down today This isn't exactly an ideal short But if you if you happen to catch a move in this to the downside, you could have done it here You could have done it here. I mean from the from the moment this broke look at it 7544 the move down Wow, look at that four bucks plus Again, you would have had to you would have had to have the news on or be watching television or you know get get breaking stock Up news updates, which I do so this look at this thing. I mean Yeah, yeah. Yeah. Yeah. Yeah. In fact, let's look at a couple others In fact, let's just look at Walmart and this is big news Amazon is taking over the world Be really interesting to see what the earnings are out tonight Definitely will be watching. All right Walmart here Not as aggressive as a move as CVS, which obviously CVS is more of a pharmacy. Walmart has other things they do Walmart sells drugs, but Walmart stock has been performing better than CVS.  Definitely you'll be watching this really big news Really really big news actually as far as stocks go So we'll see we'll be watching CVS tomorrow and Amazon tonight Talk to you soon everybody


I'm going to speak for both John Chambers and myself. Both of us firmly believe that we do not want to compete with our partners. And an important set of partners are going to be served by the partners. So we stand up, big clouds, to say, no. That being said, we have to learn. This is now I'm talking for you as the owner. What we have to do is learn. As you probably all know, we own Mosey, which does PC vacuum. And we want to take a guess how many petabytes we have we manage in Mosey. We just went over 75 petabytes. 75 petabytes. So we are managing. That's a much bigger scale than Amazon's management, for instance, just a story. So the reason we did that, by the way, we make no money there, the reason we did that is to learn how to manage petabytes at scale in a cloud department. The lessons that we're passing to are served by the partners, the blueprints. We'll have cloud. We will also provide an application developers cloud to make them for free, developer in our sense of technology. But as terms of getting into what you're talking about, cloud business to make a profit and compete with our service writers will not do that. That is not a heartland. And I know, speaking of John, that is on his plane. But we do need to learn a lot by doing. And that's why we do Mosey. That's why we're going to do the application cloud. When you get petabytes and petabytes, we have well over 1,000 customers that have a petabyte. That's just those that take you to the first 1,000 customers. We have well over 5,000 customers that have a petabyte. Do you know how much your patient think humans can manage that? Or you better, you know, you've got to trust the automation. And that's really where we're going. So these two worlds, so part of what he's saying is true, but it's going to be a different world in the future. And we have to react to that world, not the current world.


taught that when the colonists came here and I just heard a version of this today that really knocked my socks off, that the word Indian, my brother, comes from indios which is in God. Is that a proper translation? All right. So that Christopher Columbus was not talking about Indians from India because if you'll just give us that short story. In 1492, there was no country on planet Earth called India. It was Hindustan. And because they don't teach history the way it should be taught, people believe and don't check to see what they're being taught is accurate. So when Manfair said his response to the crowd that there was no country on planet Earth called India, then his next question was then how did we get to be called Indians? And he referred that to me and I said, the response was I said you're right, 1492 that land was called Hindustan. I said don't confuse that with me being smart. I said that was the only year I paid attention to this. I said I barely got out of my school. But he asked me again, he said then how did we get to me? And I said I don't have a clue. Well he went and asked permission to go to Spain to look in Columbus's law. And he asked two translators, one in town and one in Spanish. He said I need to know the reference that Columbus made in his law to the people he met. And in the Spanish the word deals means God. And in the context of the phrase indios, he was referring to the people as being in with God. So it really changes the perspective of the image of the people not being heathens, pagans and savages but actually being a higher functioning group of people that was seen. There's much more but that's tying into exactly your premise and your approach to the history and the things that we need to set straight for the future generation. Well I think you gave it to me today because there's a part of me that has always felt somehow or other less than the people that Columbus was actually seeking. And to find out that what you're saying supports the belief that I've always been taught that this was better than the Garden of Eden. That this was the place where there was no warfare. I get to that point because we get to, what was wrong with the darn Erocoi? Why were they fighting so much? And I don't have an answer to that question.


Hello everyone, wherever you are, good morning everybody, I am going back to Barcelona, I am the name of the city, and I am the vice president of a lot of people. I am working with the city partners, and I am going to work with the city of the landscape. The idea of the other landscape was conceived at the Hyperledger Global Forum last year. It was actually the last in-person event I attended in 2020, and so we were talking about the fact that the whole DLP space was growing in complexity in the last few years. We have seen an increasing activity and interest in areas that were outside of that core distributed ledger layer that now I guess we all know. It sort of created a confusion over where specific projects and company offerings as well as specific networking implementations fit into the overall system, the ecosystem. We thought that creating a sort of business stack that had a technology foundation would be really useful to mitigate that confusion in the market, but also to again provide a better understanding of the different participants of the ecosystem. There are specific offerings, but also just to create a common language in the DLP community and provide even a strategic tool that you could use for better positioning for your specific offering. Also look for partnerships as well as sort of tweak your go-to-market strategy. In terms of what we came up with, this is sort of the framework for the DLP landscape and this is the initial version of it. As you'll see, we go from that basic compute infrastructure up to the distributed ledgers, which we sort of differentiate between permission and hybrid ledgers. Also we thought that distributed ledger technology doesn't really stand on its own, so we thought that many of the use cases sort of required a combo of different technologies coming together and then provide that desired outcome. We sort of created another layer that we would call technology intersections. The keynotes, I think, David Tree from Accenture mentioned this combinatorial technology and I think that's what this layer reflects, actually how the core blockchain technology sort of works together with other existing emerging technologies. Could be AI, IoT, cybersecurity and so on. And then again, when we think about that we are living in a multi-ledger world, it started with the Bitcoin blockchain over a decade ago but then all sorts of new protocols came to existence because while trying to sort of address the flaws of the original, we could call it the original blockchain, but also catering to enterprise requirements and solving some of the problems that arise or just simply new requirements. So interoperability will be key and I think that obviously that's reflected in the landscape. Right now it's still composed by very fragmented initiatives, but we'll see how that evolves. I guess it's still a little bit early, early days, but again it's a very important area. And then obviously smart contracts and digital tokens, they play a key role in this space. Smart contracts, they have become known to the world as self-enforcing business logic that is on sort of top on that core distributed ledger that can sort of automate the rules of engagement and different business processes where different parties coming together. And again digital tokens as well, especially lately with NFTs and everything, there has been a lot of noise around that, but it is definitely a key part of this market together with Digital Wilds and so on. And then we cannot forget about business tooling and integrations. At the end of the day, this technology is very complex. It's not straightforward to use, obviously not for the end user, but perhaps not even for the developer. So then we need those tools that make that easy. So you can build on that sort of blockchain infrastructure and focus on your application and build those multi-spart systems and so on. So that's where this business tooling and integrations layer comes into the picture. And there are again different categories around different tools that help the developer itself, also some early monitoring tools as well as very specific platforms that have been already existing, but now they have this sort of distributed or decentralized capability underneath. And then obviously the applications on top, there have been many industry specific implementations, trade lands and in different industries, creating specific business networks, sort of addressing a very specific industry problem, as well as the centralized marketplaces could be to trade all sorts of assets. It could be data or even any in-game collectibles or so on. So those would be on that level. And then you will see on the framework that on the two sides, the platform category or layer as well as the services one, obviously IT skills gaps as well as the lack of resources that organizations may have, you would need some help with that. And there are specific companies that are vendors or service providers that focus on making your life easier. So providing all that knowledge that you don't have or just basically providing some quicker time to market for you. So taking away all that pain that comes with operations and management, setting up blockchain networks or even building applications. So just providing all that infrastructure and knowledge and so on. So they can help you with that. So this is the framework. This is where all started. And now I guess we should be talking about the outcome, right? So what we wanted to do based on this framework is to create a sort of a living segmentation of this market that it's still evolving. It's again, we see it as a business stack with the Technology Foundation. And so we found this application, this landscape app that was created by the CNCF project under the umbrella of the Linux Foundation. So basically we used that open source code and we did build an open source initiative that it's based on that same open source code. And it's sort of interactive. At the end of the day, we created it as a company, BTP, and we are going to curate it or continue to create it and we'll be hosting it. But it is independent of the company, right? So obviously, our competitors are on the landscape. It's just we created it for the community to benefit from, contribute to and so on. So before showing the actual landscape, we launched it in April on the 22nd of April. It had a press release. It has a blog post as well. It explains the whole background of what I already explained to you, the background of the landscape, what the different layers mean and what the purpose of it is.  It's the artist landscape org. It has its own QR code. It's sort of created a person around it. It has its own Twitter account. She tweets in first person and so on. But, okay, well, yeah, just, okay, sorry, I want to show you. And then we can talk a little bit about the dynamics, right? So this is how it looks like right now. I think to be honest, I think this is pretty awesome. The application has its limitations, but we did create, as you can see, we did create the same, you know, structure as shown on the framework, going from the infrastructure, you know, goes up to different levels and then end with the applications, with the platforms and services on the site. You can see those little squares. Those are, you can call them by project or company cards. So if you click on them and then, obviously, as we are at High Collegiate Global Forum, let's check a High Collegiate Project. All right, so Distributed Ledger at High Pledge of Bezoo, we love High Pledge of Bezoo, is in that Distributed Ledger layer among the hybrid initiatives. And as you can see, so if you click on that specific card, you will see some basic dates around, you know, the project or if it's a commercial offering around that offering and the company and so on. So one thing to highlight is that to be able to be part of the landscape, you need to have an account on CrunchBase because, you know, that this base information is pulled from CrunchBase and all that information that is displayed there, as well as, obviously, if you are an open source project, then also your GitHub repo. So we are, you know, all that information is in the landscape and then all the data is pulled right there.   But obviously we are using the CrunchBase account is just for an organization, but that we are trying to pull in some data from your specific project. So, okay, that's it. You can also see that, you know, you might see some of the logos are not the actual logos, but there are some placeholder logos, which are, you know, those cars that are displaying the DLT landscape logo. That's, there is an explanation for that. It's because, so this application requires that we have a logo of the specific organization or offering in SVG format. So if we don't get the SVG format, we cannot display it. We are so sorry, but that's how it is. So for example, if, for example, we look at cybersecurity, let's click on this one, oh, Altar. So Altar is, yeah, it's a impious security startup. They are using distributed ledger technology. And, but yeah, again, you can see all the data about the company, their tweets, we had all that information, but we didn't get their logo. So again, we, if you want to, if you want to make any correction, basically, if you see yourself on the landscape and, you know, you see any mistakes or, you know, you want to, you think that you might be in another category or you need to be in more categories. All you need to do is pull, is submit a pull request, right? So you can do that. Again, with the same thing with the logos. If you see your car there, but you don't have a logo, if you submit your SVG, the genuine SVG format, a logo, you know, we can approve that and it will be displayed. So this is what you need to do. So essentially what we created, it was, you know, the whole framework, you know, with a, with a good list of projects and companies with their offerings on that. It's not an exhaustive list. So there are so many initiatives in the DLT space, as you can see, as you can see the market right now is pretty fragmented, it's very complex. So, you know, if you don't, if you don't see yourself here, please let us know. Well, just submit a pull request or you can reach out to us as well directly, we can make that happen. And again, if you see, you want to make a correction or suggestion, yeah, again. So we want this to be, you know, something really useful for the community, created by the community. So it's now, let's say it's, it is in the wild, right? So please, I invite all of you to contribute to it and we are really excited about this and we really hope that this is useful. Again, as mentioned before, you can use it as a strategic tool.   So I guess that's it for me. So I, yeah, I'm going to take a look at if there are, you know, any questions. I'm very happy to, you know, answer all those. All right, no questions. There's a chat. Okay. Thank you. Thank you, Troin. Again, you know, if you have any questions about the DLT landscape, you know, let us know. We are silver sponsors of this event and we have a virtual booth and just, you know, stop by and let's have a chat and, you know, let us know what you think and again, you can just, yeah, reach out to us. We are more than happy to help. And again, if you don't see, if you are active in the DLT landscape, well, sorry, in the DLT space and you don't see yourself on the landscape, please let us know or just, you know, submit a pull request. Let us know or let us know and we can do that for you. And, you know, again, hopefully this is a useful tool for the community. There are actually a couple of questions in the Q&A tab. Sorry, because now I can see it because, yeah, I was clicking it. Where do we do pull requests? Yes. So, as if you give me a sec. Git, so you can see, yeah, yeah, it's, is that my, you can please open a pull request, right? So you can click there or just go to GitHub, right? It's GitHub DLT landscape. So you can, you can create your pull request there. Can you tell us about your work with the DLT? Well, thank you for that question. That's something new. So we have just launched that sort of technical working group. We had our first meeting this week and actually it's, you know, it's a really good questions because we have, you know, we have started to talk about if, you know, this is something that, you know, we could collaborate on if, you know, we could find a way to, you know, bring these two sort of initiatives together and how we could extend this landscape and reflect the work of the GSMI. So that's something that we are working on. Excellent question. Any, yeah, any other questions? Can you tell us? Yes. Yeah, so I guess, so for now the landscape, it's sort of, it's, as you can see, it's very vendor focused and it's not only commercial companies but also those projects that are either underpinning or have an open source offering. But then, yeah, so what we could add and I think we will start to think about is those, adding those or somehow those organizations, you know, we don't want to overwhelm the landscape but I think we will need to perhaps add those organizations that are a little bit on the sidelines but very influential, right? They might not be a technical offering but, you know, they are influencing the market. So I think that's something where, yeah, we could improve the landscape and again, you know, if, yeah, please suggest any ideas, just take a look, take your time, take a look at the landscape and just let us know what, you know, what you think, any suggestions and the idea is to, you know, make it grow. This is sort of our first version and we want to make this really useful for the community. So thanks so much. Could you add tech capital funds and investors? Yes, okay. So there's a question around capital funds and investors and then again, I guess, yeah, you're right. So those are, those would be including that category. There are not like specifically offering a technical offering but then we should be, yeah, those should be reflected on the landscape. I do agree. So we will work on that. Yeah, definitely. So thanks for that suggestion. Any more questions? How did we? So how did we come up with permissionless blockchains? I mean, you know, so I, I don't know if this is an ironic question or not.  And they were not that comfortable with public clouds and then, you know, we have seen the emergence of private offerings. I think, and then obviously the market has evolved and now it's hybrid and, you know, pointing to more usage of public cloud and so on. I guess something, perhaps something similar is happening in the blockchain space. The initial idea was like fully public and then, you know, obviously enterprises saw the opportunity and the potential of the technology and, you know, there are specific enterprise requirements that those, you know, public blockchains couldn't comply with or at first instance and then, you know, all those offerings have emerged and then we'll see where the market goes. But we, I guess I just see a very, very similar trend to the cloud market, like going to hybrid and then who knows. But yeah. Any other questions? Thank you, Troin, and thanks everyone for the questions so far. And again, I'm happy if you, you know, if you're shy or you don't ask your question here, I'll be here today, well, tomorrow and after tomorrow. So I'm happy to answer any additional questions, not offline, online, but, you know, outside of the session. Okay, I'll wait just a few seconds if there are any more questions. Okay. All right. Well, I think we are, yeah, we are about to finish the session anyway. So thank you so much for those who attended and I hope this was useful and we are really excited about this initiative and, you know, just, yeah, again, let us know what you think. And again, I really hope that this is useful for the community and I'm available for questions outside of the session. So thank you so much. Have a great afternoon, evening, wherever you are. And hope to talk soon. Thank you so much.


Today, I will present to you our case studies, Digitalist, Test-Fed, Autobahn, and Durabast. These case studies are part of the project cluster smartbridge. In this project cluster, an adaptive system of information and holistic evaluation in real time is developed. The main benefit of these project clusters are economic and safety improvements. Here you can see which aspects are important for the project cluster. On the left side, we have the smart sensor technology. This aspect includes the support of intelligent network, sensors for intelligent network, and the development of innovative sensors. On the right side, you can see smart assessment methods. Here are the aspects, bridge modeling, deterioration modeling, and reliability-based assessment are important. Above, you can see the smart maintenance management. Here are the conjunction of the visual inspections of the bridge, the bridge database information, and the results of measured and evaluated data are perceived. The first case study I will present is the Digitalist, Test-Fed, Autobahn. This is the new built concrete bridge at the interhighway change Nuremberg. The bridge is equipped with different sensors for the detection of impacts of traffic load, climatic influence, and the reaction of the components with regard to the functionality of the individual bridge components. The aim is by using an analytic bridge model and evaluation methods, the condition and reliability of the bridge construction and its components will be determined. Here you can see on the left side a build of the bridge. On the right side, you can see an instrumented expansion joint with strain gauges and force sensors. Downright, you can see instrument bearings with pressure and displacement sensors. This is the second case study. It's called Durabast. Durabast is in demonstration, investigation, and reference area of the Federal Highway Research Institute in Germany. Within this area, we've gotten a completely overhauled bridge. Located is the Durabast area at the intercharge Cologne East. And the bridge is equipped with different sensors for the detection of durability and structural safe monitors. The aim of these studies is the integration and partial implementation of the aspects, data collection with sensor, data processing, and model development of condition assessment of the bridge. On the above, you can see the Durabast area. In the middle, you can see the bridge. On the left side down, there are corrosion monitors. And on the right side, strain gauges, which are now in the bridge. And we can take the first data of it. Now, the approach of the implementation for value of information. What I must say that, until now, we are not dealing with this aspect value of information. In the future, we'll be in research projects so that we can use the value of information for us. What I can say for the digital test fat is the aim is to optimize the maintenance planning of the bridge. What we are doing periodically, the reliability index of the bridge components is determined in two different ways. First, the reliability index of the bridge and its components is calculated with an FE model and the impact data. And second, the reliability index is determined through the reaction of the bridge and its components. For the Durabast, until now, there's no idea how to deal with these aspects. What are the current states of these projects? In a digital test fat, the sensors are installed. The first data are collected. And what we are now doing is an automatically merge and evaluation of the data. At the Durabast, the sensors are also installed. The data are collected and analyzed. And the next step there is the determination of the weakness of the bridge and an experimental determination of the load bearing capacity of the bridge. For some questions, thank you for your presentation. I think the basic elements for making a decision analysis is the very important. Yes, thank you.