Russia could attack NATO as early as 2026, Polish president. Russia may have the military capability to attack NATO as early as 2026 to 2027. Polish President Andrzej Duda said this in an interview with CNBC. The Polish president defended his recent proposal to increase the required threshold for NATO defense spending from 2% to 3% of GDP. From my point of view, it's a question of common sense. New reports are coming in and I recently saw one by German experts which said that soon, perhaps as early as 2026 or 2027, Putin, by putting his economy on a war footing, will have such military might that he will be able to attack NATO. Duda said, the alarm bells are ringing. We have two or three years in which we can increase our efforts, stockpile ammunition and produce weapons to maximize European security. Get ready and make sure the invasion does not happen, he urged. He also urged the US to continue to support Ukraine, warning that if Russia is not stopped in Ukraine, the cost will rise sharply later. The Russian aggression has to be stopped at all costs. If it's not stopped, it will spill over and then I fear US money won't be enough to stop Russia. US soldiers will have to step in and no one wants that, Duda said. The same time he said that every dollar donated to support Ukraine, every Bradley transferred to Ukraine, every weapon transferred to Ukraine, every box of artillery ammunition transferred to Ukraine staves off the Russian victory. Earlier, German intelligence services had prepared an analysis for the German government examining the military threat posed by Russia, which predicted that it could attack the territory of NATO member states starting in 2026. In recent weeks, a number of European NATO countries have warned of the risk of Russian aggression in the near future. For example, German Defense Minister Boris Pistorius said in January that the alliance should prepare for a Russian attack on a NATO country within five to eight years. NATO troops are already in Ukraine for arms control. NATO troops are already in Ukraine for arms control, intelligence operations and training, according to El País. The agency has interviewed many military sources from Ukraine and the EU over more than two years of war and they all agree that no NATO army has taken part in ground combat. But they also agree that they have informants on the ground who provide information about the situation on the front line, determine the effectiveness of the weapons being supplied and possible problems in their use and identify possible cases of corruption in the delivery of aid. Some of these official informants are retired foreign military personnel who volunteer to fight in the Ukrainian armed forces. At least two sources, one American and one Ukrainian, claim that Washington is particularly active in monitoring their assistance, organizing missions between its embassy and the Ukrainian authorities, as well as visiting them outside official channels. The alliance's military is not directly involved in combat operations in Ukraine, the paper asserted. It also mentioned Polish Foreign Minister Radislaw Sikorski who told a conference in Warsaw that NATO soldiers are already present in Ukraine, but as compared to other politicians, he would not specify the countries that they had come from. The Polish Foreign Minister statement, as the paper said, could be seen as criticism of German Chancellor Olaf Scholz, who said in late February that British and French forces were present in Ukraine. Retired foreign servicemen fighting on Ukraine's side allegedly on a voluntary basis are among unofficial informants. Besides, two sources told the paper that Washington was controlling its aid especially actively. French President Emmanuel Macron said after a French meeting on February 26 that representatives of about 20 Western states had discussed further support to Kiev in the conflict with Moscow and raised the issue of potentially sending troops to Ukraine. He said that participants in the discussion had reached no consensus on this issue, but this scenario could not be ruled out in the future. Later Macron explained that not ruling something out does not mean doing it. As Russian President Vladimir Putin stressed, Russia is aware of the presence of NATO forces in Ukraine where they are perishing in large numbers. China threatens to boycott Ukraine peace talks without Russia. China may boycott peace talks on resolving the war in Ukraine if Europe does not allow Russia to participate in them according to Politico. The news agency spoke with officials who reported that China is trying to persuade Europe to allow Russia to participate in future peace talks possibly to be held in Switzerland. Otherwise, China will boycott such meetings. That message was amplified, they say, during Chinese Special Envoy Li Wei's European tour earlier this month to discuss the future of Ukraine, the material states. And officially, the Chinese Ministry of Foreign Affairs announced that Li Wei promised support for the timely convening of a peace conference with equal participation of all parties. Earlier, Chinese President Xi Jinping presented his vision of a diplomatic resolution to Russia's war against Ukraine and appointed a special representative to address the issue. This representative is China's former ambassador to Russia, Li Wei. After his appointment, Li Wei visited Russia, Ukraine and the EU to discuss the Chinese initiative. Kiev does not appreciate Beijing's diplomatic efforts as Ukraine already has its own peace formula. After that, China forgot about the issue of Russia's war against Ukraine for a long time. It was previously reported that China's Special Envoy Li Wei would visit Ukraine, Poland, Germany, France and Russia. His tour began on March the 2nd. The Chinese diplomat has already visited Ukraine as well as Brussels and Poland. Li Wei discussed Russia's war against Ukraine calling it the Ukrainian crisis. Against the backdrop of the Special Envoy's tour, China's Foreign Minister announced that Beijing supports holding a peace conference on Ukraine. The EU expects China as a permanent member of the UN Security Council to play a constructive role and use any opportunity to defend and promote the UN Charter and International Law. The EU emphasized that it expects China to call on Russia to immediately and unconditionally respect the principles of sovereignty, independence and territorial integrity by withdrawing all forces and military equipment from the entire territory of Ukraine within its internationally recognized borders.


Hi. My name is Mike, and I'd like to tell you about the future of machine learning. So a Deloitte study shows that the number of machine learning projects piloted in the world is going to quadruple within the next two years. I'm sure that's not news for you guys in the crowd, but the fact of the matter is that human brains need to build all these algorithms, at least for the time being. And there's a giant skill gap between the number of machine learning engineers that exist in the world and the number of projects that are going to be demanded. So the number one source of machine learning developers in the world is actually software developers that are re-skilling on the job. The problem is that for these software developers, machine learning is still a black box, totally different animal compared to software development. We did a large survey before going to market with over 100 AI companies, and we found that over 80% of them, for example, use Slack to make important decisions about machine learning. And yet, those decisions, when they're made on Slack, are really tough to carry out. What does that mean? We got a billion dollar problem. Why? Because when you make the decision to turn a server off on Slack, when you make the decision to redistribute compute power on Slack or kill off a model, there is no actionable way to take that decision into your testing environment, let alone in production. Our survey estimates that this leads to 10 hours of waste per engineer in a company in machine learning stack and development process. So at Mishkin, we decided to fix this problem with the world's first interactive machine learning bot. It is IML software for the tweak, test, and learn generation. Before I tell you about how it works, the entire team would like to thank our clients and our partners for helping us iterate this tool in beta before we release it to the world. We worked backwards from client need in machine learning to come up with an amazing, uncharted list of engineering problems to solve, and solving them through our product has been a wonderful adventure. So let me tell you about what it does. First, with our interactive machine learning product, out of the box and for free, you get monitoring of all your machine learning jobs on Slack. On top of that, you're able to schedule as many jobs as you want right from Slack, pause longstanding jobs that are executing, tweak parameters while the job is executing, fork a job just like you'd fork a repo on GitHub, and under the hood, it will automatically spin up, provision a server, and send the job off running. Looking at our competitor matrix, we are the only company currently that has a duly UX centric and a deep tech approach. We have a patent pending for the optimizations, scheduling, and memory IO options that happen in the back end, which are purely a result of the requests that we get from our front end application in Slack of what machine learning developers want. On this subject of what machine learning developers want, our business model derives entirely from that. We have the privilege of partnering with Slack, Microsoft, and Amazon for their machine learning workshops, which are conducted on Slack through the Meshkan tool. That means that we're there at the workshop feeling the pain point of hundreds of machine learning engineers as they're discovering these tools for the first time, interacting with them on Slack, and turbocharging our sales process directly in front of the clients that matter most to us. Of course, Slack is an ambiguous tool that allows us to give high-level support. And furthermore, most of the advanced features that you saw us talking about are part of a freemium model that you have to pay for. But in order to measure what value we're capturing, we use analytics tools directly through our partnerships with these providers in order to see the value we're capturing, charge for it, and continue to delight our customers. So our market is barely out of the gate, and already it's a huge business opportunity. We seek to capture 20% of the total addressable market by the year 2021. And as I told you guys, that doesn't just stop with machine learning. Because remember, these are reskilled developers who also need to test their code, push their code to production, and mostly be advocates for a data-driven approach in the future. We hope to be their trusted source of software tools now so that we can scale with them as they grow. The Meshkan team is myself and three intrepid entrepreneurs that combined have experience of 16 years providing deep learning and high-tech products. We build our solution with an immense amount of love and empathy for our clients, all of whom are colleagues, research partners, friends, or future friends. They are serving all of you in this audience with new generation machine learning tools. And we are proud to serve them. Lastly, I would like to thank our investors, including Risto Silasma, chairman of Nokia, who are supporting us in our journey to be the world's leading provider of machine learning and development services for a new generation. Thank you. Yes. Thank you, Mike. Jury. So very cool, great presentation. My question is, the machine learning number of engineers, they were small, right? And we heard that from Amazon just one presentation ago. How big of a business can you build here? So this question leads me to an exciting announcement that we just launched a second product based on our machine learning stack called Unmock.io. Don't take out your phones and type in Unmock.io that uses the same exact stack for continuous integration. So let me rewind a little bit and talk about what I mean by tweak, test, and learn. When you're running a machine learning model, it's a very data-driven process. So you're tweaking it based on external data, but not based on lines of code you're writing. The same exact logic works for third-party integrations, where you're tweaking code and testing it based on mocks of third-party APIs. So we found that machine learning is the first vertical that we're scaling up with, because we know it well. I myself am a data scientist. And by validating this tweak, test, and learn model, we hope to catch a much larger total addressable market, including continuous integration, monitoring a production environment, and database management. So are you providing data then for that tweaking? Yeah, so actually, the second service I talked about does the first service with machine learning, the developers bring in their own data to the servers. And then the tweaking, testing, and learning is actually about the configuration of the models and the parameters that go into those models. I have one comment and two questions. First, you have a very special company name and logo. That's very special. Two questions. So how does onboarding, if a customer looks like, is there a customization? Or it's like an automatic or straightforward process? Yeah, so that's another question that could be answered with a website, so app.meshkan.com. And we could see how many of you are onboarded pretty soon. So it's through Slack. So you go there, and immediately you go on the Slack page, where you can integrate it into your favorite workspace. You'll get a ping from the Meshkan bot, and you could take it from there. The other question is whether you're optimized for certain workloads, certain machine learning specific workloads, or it's like totally generic. So we're most optimized for deep learning workflows. And to tell you the truth, it doesn't make a lot of sense to use a tool like this for short running workflows that don't need a lot of monitoring and constant re-tweaking. But for deep learning workflows written in PyTorch, Keras, SCI Learn as well, and TensorFlow were optimized. And we are big users of Meshkan as well. And you can see that in our open source repositories in GitHub, where we'll show you how to use the thing. And how are you setting up your sales team? So our sales team is currently the entire team. I was just at Reinvent last week, where I was there both to pilot these workshops and to sell. But I read a great book earlier this year called Negotiating with Giants. I don't know how many of you guys read it. And one of the great pieces advice that I learned from it is sometimes putting on the other team's jersey helps a lot to be able to sell stuff. So I'm proud to say that our partners are part of our sales strategy, and really actively helping us with that. So Microsoft for startups, AWS for startups, it's not just free credits, but it's a whole lot of advice about how to sell. So it's a win-win both for the providers of the GPUs and the people like us that are helping you use it. Continuing on the sales, you're targeting the companies and teams in the companies that you're not selling to individuals. So currently, we have a dual strategy. We started by selling to companies. And those we meet at conferences. And I've met several of your conferences, including this one. But after beta testing the tool, we've moved to selling to individuals. And then upselling through the Slack bot. So we have instant onboarding. And then the upselling is all behind buttons that people click on, which then allows us to measure price and adjust price on the fly so that we can make sure that we're always providing value to our clients. So I gather you're raising financing? Our financing. So currently, are you raising capital? So now, now we're not raising capital. We are going to hit the road in San Francisco in a month to start doing that. And if any of you are investors out there interested in financing Michigan, we're especially looking for people that could help us scale with this model. So we'll be talking to the Slack fund and a couple other funds, too, that you can imagine that the Slack fund knows something about Slack. Yeah, I would gather. I've also, we've seen platform dependency be a killer of businesses in a sense. What kind of a dialogue do you have with Slack right now, right? With several sources. There's CTO who might even be in the audience is there, is here. So I had a chat with him last night. I had brief chats with the sales team as well. And I'll be there in San Francisco to meet them next month. And I'll also be at Amazon headquarters in Seattle. So the dialogue is pretty fluid. I think everybody realizes that it's a win, win, win for all businesses involved. And I'm really excited that they're willing to help us out. And I'm also kind of excited to help them out, even though we're still small fish. OK, I can ask more. Yeah, one more. Where do you aim to be in 18 months time? In 18 months time, we would like it to be deployed on a thousand different teams platforms, running machine learning on Slack, have data-driven metrics to figure out the pricing model, and have launched two other products based on this tweak, test, and learn model, going with this chat ops idea. So you already saw the Unmocked product. And currently, we have one in the works for database automation as well. That's where we would like to be in 18 months. Those are some pretty good milestones. What does that mean in terms of are you going for a freemium model that you're going to deploy? So everything currently runs on a freemium model. And we also meet with larger teams to come up with custom solutions for those teams. For example, I'm flying out to Stockholm to meet up with Raysearch Labs next week on this exact topic. So if you're a larger data science team, don't hesitate to reach out, have a chat. We'd love to come up with a custom solution for you as well. But in order to be able to scale, the nice thing about Slack is it's already in millions of pockets, thousands of which are vibrating around this room. And we hope to sell through that too. Can I just give you a compliment? I think you're an amazing marketer. Can we just give him a round of applause for that? Because you can. Thank you, Mike. Thank you. Thank you very much. Take care.


The Minister of Labour and Employment, Senator Chris Ngige, has warned that the federal government will no longer tolerate strike that does not follow due process by any union. During his transition period of the administration of President Muhammad Wairi, Senator Ngige issued a warning shortly after receiving an award of excellence conferred on him by the Nigerian Association of Resident Doctors and ARD at a 42nd annual General Meeting Scientific Conference of the Association. At the award event, the new leadership of ARD rates some concerns of the doctors, including the review of the Consolidated Medical Salary Scale Comments, the structure of the correction of some minor errors in the secular on the upward review of the medical residency training fund MRTF, non-taxation of the call duty allowance and non-payment of the new hazard allowances to house officers. Speaking on the review of comments, Ngige noted that the committee had already been put in place at the federal Ministry of Health, which was working internally for the time being but would swing into action next week to dialogue with the resident doctors and members of the joint health sector union, Johesu. notified about fresh news updates.


Hello and welcome. This is the Jenkins platform SIG meeting for February the 28th of 2023. Today we have Mark Wait and Kevin Martins and of course myself. We still have a few open-action items. I think we won't get rid of them shortly. And it's of course about Docker images for the Blue Ocean container which are deprecated. We haven't announced yet the deprecation of the image or have we Mark? I don't think we have. No, no, we have not. It's been discussed here. I think the deprecation of this image would be best done by adding the administrative monitor that's mentioned in a later action item or in a later topic. And then we announced the deprecation, blog it and people see it in their Jenkins Weekly. Oh, hey, this thing is deprecated. Yeah, because we still see from time to time people coming out of the blue. What? Wait, deprecated? Really? Yes. Right. And we need a way to at least point them to, hey, your user interface was trying to tell you this. You suppressed it because they may, but at least we attempted to tell you that this thing is deprecated. Okay. And speaking of things that we want to get rid of, we used to love the Blue Ocean and things that we don't love that much. Like CentOS 7. We like to get rid of the CentOS 7 Jenkins Contra Docker image. As you may already know, we've thought that in the previous meetings. Officially, CentOS 7 is still in maintenance update from 2020 until June from next year, so 2024. And we want to deprecate the CentOS images for Jenkins. And we definitely want to get rid of that. I know Mark, it's one of your motto, get rid of CentOS 7 for various reasons. One of the reasons I have it that it's really difficult to keep it up to date with a recent version of Git. For example, I know how much you love and use Git. And that's a pity that for CentOS 7 it's really, really hard to get a recent version. Unless you compile it by yourself and help. So in previous meetings we talked about maybe needing a JEP about using an administrative monitor. So if I'm not mistaken that the kind of thing you see when you have a deprecated plugin and when you have a new version of Jenkins and all of that appears in your Jenkins controller. Am I right, Mark? Yeah, and I think we may actually be able to do this with just one JEP and a pull request to Jenkins core now that I, I look at this a little more think thank you for writing thank you for the notes. I think that Jenkins enhancement proposal that we need is to change our usual behavior our usual behavior would be CentOS 7 end of life is June of 2024 when the CentOS project ends its life. We want to end support of CentOS 7 sooner say September of 2023 October some arbitrary date we choose. That is a change for the Jenkins project and so the JEP is to propose an acceleration of the end of life for CentOS 7. With an administrative monitor I think we can just do it as a pull request proposing now the pull request will certainly get lots of feedback, lots of comments from people about hey, either this is not general purpose enough or it's to general purpose. What are you thinking about doing it this way why not do it this other way, and, and those those conversations will be valuable and useful and important and will give us a better solution. Because it's, this is sort of an administrative monitor for deprecation of a thing that deprecation of a thing there could be multiple deprecated things and we need a way to represent multiple deprecated things, portably cleanly extensively, etc. And so that's that it'll actually be a fun thing to add to Jenkins core. And certainly there will be lots of conversation I expect lots of conversation and some really good insights from the high skills people around the organization, not me, who know how to do Jenkins core development really well. They'll suggest, we should do this instead of that and we'll get a much better solution as a result, because we know we need to deprecate blue ocean Docker container right the blue ocean container image. We know we, we, we should tell people that Ubuntu 18 is end of life as of April of 2023. And likewise our Alpine container images. I think in May of 2023, the oldest of those container images will be deprecated three dot 14 if I remember right is one that's deprecated so. All sorts of places where this technique may help users and where we need the technique as a way to make things very visible that hey you're running on so as a as a very specific example. I saw posting today on community dot Jenkins.io from a user who said, I have a Jenkins that's running on Ubuntu 16 04. And my answer to that is, that is absolutely crazy because the Jenkins project does not support Ubuntu 16 04. And we don't support it because the vendor does not support it right canonical does not support 16 04. 1804 is the oldest they support and that will end support in May of 2023 I believe or April of 2023 so. So, we could do them a service by saying, you are running on a platform we don't support. Oh yes indeed yes you're right and they may, they may be unsettled by that they may find that very aggravating what you're telling me, but but it's the truth right the Jenkins project does not test or support or in any way do any work on Ubuntu 16 04 and and we won't. Yes, and as you said that could lead to good conversations between people in the community. And I guess people from the security will chime in say, what you're going, you're going to deprecate all pine line looks whatever what about getting totally rid of all the pine images and so on. Why not. But yes, I hope that people will discuss and find the consensus afterwards. It's very interesting and you're right that would be very helpful for the end users seeing that they are running their Jenkins on an underwater system by Jenkins and by the vendor itself. It's super cool. I would love that. And by the way thanks a lot for the link you gave us few meetings ago, maybe it wasn't docs office or whatever. I'm going to deprecation the end of life the open source website. And yeah, today I saw a tweet from a French guy saying, oh I found a nice website to manage my end of life and say, I know of a better website which is open source, because the website he used to use didn't list Jenkins for example. So yours is better, whatever. Kevin Mark any other informational question whatever regarding that subject. No, we just I think for right now we're in the talk phase, rather than the implementation phase and I suspect will will be stuck in the talk phase for several more meetings just because I don't have capacity to do and I don't know of anybody else who has capacity to do it. But the concept feels like the right concept and let's let's keep working on it. Yeah, to me at least looks pretty cool. So without further ado, let's go to the next subject, which is the latest updates on the agent images, nothing disruptive. This time, just a few things about get once again, because I think there was a CV you recently about get so the latest images now have the right get version until the next CV, I mean, I suppose, and the inbound agent got an update of the parent image to update in fact, the three and then the four. That's all that they and for the update cli we don't care because it's something that happens behind the curtains, and that doesn't change anything when you are using the input agent so something totally optional but we still have a few minutes. So I discovered by accident yesterday that the Android build tools are now natively compatible with art 64. And guess what it has been a long time I never know I was stuck for whatever reason with the version 30. Something and so it never worked for our 64 unless you know for example lots of people have now arm and one with an R64 controller and building Android application with Jenkins all these machines. You had to use the Rosetta, which transform the xx t64 instructions into our 64. And this is not perfect. You just have to switch to Android build tools 31.0.0 and bound. It just works. That's typical for me because I build Android apps with Jenkins on a regular basis but on xx t6 machine. Yesterday night I tried something on those small R64 machine and it worked. It was amazing. Previously you had to do some hacks with some binaries taken from a Chromebook for example to get it to work so now as a developer. I'm super happy that it does work. And yeah, another subject about Jenkins. I know every meeting I talked about race five, which is a very promising CPU architecture. And I was pretty proud of myself because I had made some tests with some very agey open JDK bills and so on. I thought I was really a pioneer, you know, and unfortunately I tried a chat GPT today for the very first time. I didn't want to experiment with that but I asked chat GPT, do you know about Jenkins, of course. Do you know about risk five, of course, do you know about risk five and Jenkins and then he gave me some pointers of blog post and ready thread and GitHub issue. And I thought end of 2022 was the beginning of Jenkins on the risk five, but I was wrong. So wrong. Some people experimented in 2020. So yeah, I'm not a pioneer anymore. So I'm happy and sad at the same time. So with any of you have any other things to add before we close the meeting. I do not. Thanks very much for your time. Thanks. Thanks a lot for coming. The video should be up on YouTube in 24 to 48 hours and we'll see each other 15 days from now. Have a good rest of the day. Bye bye.


One of our favourite phrases is stay curious, not furious. In a lot of schools that I've been in, a child will present with behaviour and the teacher will immediately be, whoop, I'm angry with you, you've done this that and the other. But what we say is, be curious, why is that child presenting like that? Why is that child coming angry, upset, frustrated? Why is he throwing a chair? He's not just doing it for the good of his health, he's doing it for a reason. He doesn't want to make you feel angry. So we stay curious, we wonder why. Why is the child coming in like that? Why is the child there? Why is the child dirty? What is happening in the background? And I think if we remain curious about people, then we practice really.