Hyperledger Indy Contributors Meeting - 2026/08/11

Greetings. >> Good morning. >> All right, give me a sec here to get the doc prepped. >> All righty, you see my screen? >> Yep. >> Awesome. Uh Welcome everyone to the August 11th, 2026 Indy contributors call. Uh we're managed by the Linux Foundation antitrust policy. And we follow the Linux Foundation decentralized trust code of conduct. Um I'll post the link in the chat here for anyone that uh needs to link to the Oh, what's the edit link? Once up here. Publish. All right, there's the link if anyone needs it. And you can find the Linux code of conduct in here as well. All right, uh >> [sighs] >> I don't see anyone new or anyone that needs to introduce themselves this time. Um I'm going to give an update on the Ubuntu 22.04 status. Uh I'm making uh significant progress and moving in the right direction. Uh let me show you where we're at right now. Um I've got the Indy uh plan on project here. Um uh simplified the build processes, so it's easier to onboard new people. Although, I will need to add some features back into it. Uh the basic idea though is uh we have a base Docker image that gets built. Uh we build the production image, uh and this will be the same pattern on Indy node. Um we're moving towards a uh Docker configuration. Now, we uh trigger the tests on a pull request, for example. Um, if you go look at the Docker images um, themselves, we need to look at our branch here. branch And we come and we find our Docker file. Um, this is a uh pretty basic uh Docker file for Indy Plenum. Indy Node will be a little bit more intense. Um, but the basic idea is we install the Docker file. Um, this is the build Docker file. It goes and gathers all the dependencies, does the builds, and uh creates base file, a base Docker file. Uh both of these can be used in the Indy Node later. Um, the main advantage here that we're getting away from is um I've experienced a lot of difficulties getting the Python uh dependencies to install correctly and be managed in the Debian deployment. Um, so the idea is to move away from Debian packages, move towards a fully Docker based install. Um, with that in mind, there are a couple of changes that I'm looking at adding for the upgrade and synchronization commands. Um, and those details will be fleshed out a bit further uh as I get through this. Um, so the first priority here is to get the built working. Uh that's where I'm at right now is uh once I get through uh uh get through all the builds working and compiling so that um, we make it through the build and we make it through the tests, and we make it through publishing. Um, uh both Indy Plenum and in you know that I'll move into the test phase and then I'll work with you, Lynn, to uh ensure uh that there's an upgrade path from the Debian-based images so that we can finally get off the Ubuntu 20.04 installs. Uh you have any questions, Lynn? >> Um >> [clears throat] >> I just a concern I'd like to raise really quick. I It looks like 22.04 is going out of um standard support in April of 2027. And so, as soon as we finish this, we're going to have to move right into the next one, I guess. >> Oh, absolutely. Um there's a number of steps that we need to take. Uh we need to apply a bunch of security fixes and other things uh and uh upgrade to Ubuntu 24.04 uh pretty rapidly here. In fact, maybe even bump it up to Ubuntu 26, but I think we'll stick with 24. Um so that that is a valid concern that you have. >> Yeah, I'm going to vote for 26 um because that'll be in LTS early next year, I believe, if I'm not mistaken. And so, by the time we get that done, it'll be the right one to be working on. It It's Um that'd be my vote, I think, but unless there's some weird difficulty in going that many versions, I guess. >> Yeah, that's something I'll I'll have to look at. Um uh but overall, I'm excited for this direction. Um it simplifies uh the We We had a lot of weird dependency issues on the build process where you had to have a build to do a build. It It followed very circular reference-oriented. Um where you had to have the Debian packages already to do uh step through the entire build process. Um, and so the goal here by moving to those Docker images is that we simplify the build pipeline, make it easier for anyone to contribute to the project. Um, and that's the main focus right now. Um, so I just wanted to show that yes, I am actually making some progress. Um, now that my uh, big push on the other project I was working on wrapped up. Um, so I'm hoping by next week this will all be wrapped up and we'll be moving into the other phases. Um, we really need to get the project all cleaned up so that uh, uh, we're passing those additional priorities that we made at the beginning of the year uh, for the project. We have uh, some signing to do, uh, dependency scanning, and a bunch of things that we need to add. So, I'm trying to move quickly on this now. Um, >> Excellent. Thanks for your efforts there and for the progress report. >> Yep. Uh, I think that's all I got for today. Um, Lynn, I'm going to update this report and then uh, I'm having a hard time finding those recording links, so maybe you can add the recording link for me later today. Or you can send me uh, some instructions on how I find those recordings. >> Uh, yeah, I got the information from Ryan. Or sorry, Rye, I guess it was. Um, I can I can send you that link. It would probably be Or I can do it. Either way, either way works. I'll go look at the link and see what it see how hard that is and >> Cool. >> [snorts] >> figure figure it out. >> Um, any other topics to go over today? >> Um, nope. >> All right. Uh, catch you guys all later. >> Thanks. Bye.