 Hey Sandeep, hey Zuru. Hey, hi. Can you see the screen share? Yeah. Cool. Hey Rama, hey Rama. All right, we can get started. Hello and welcome everyone to the Hyperledger CACSI Maintainers Meeting. Please abide by the antitrust policy notice that I'm showing on the screen and also the Hyperledger Code of Conducts, which you can find linked to in the agenda document. And one thing I had is pool requests. I wanted to talk about a few of them. Just as an FYI, I submitted two of them that you can see here. If you go to pool requests, you see 2519 and 2521. They are both very, very simple sort of administrative change kind of pool requests. But please do look over, let them over because maybe I did something that you don't think is a good idea. For example, here I just mass upgraded all the container images, which I know is fixing a bug that's been causing issues for all of the tests. And then the other one is also a bug fix, which is causing issues for tests that we are running locally. But also it's just a dependency bump. So it's pretty simple. And then the other thing I just wanted to explain further this comment I made on round was pool requests. I already approved it, but I just wanted to talk through the specific thing I said about the change log generation. So if you go to the changelog.md file that I'm showing, then you see there are bug fixes and then there are features and there are reverts as well. The point is that there are these sections and what actually makes it to this release notes is determined by what you wrote in the commit message. And so that's why sometimes if I see a bug, something marked as fix that is not actually fixing a code bug or fixing a vulnerability that I tried to ask the people who submitted the pool request to rewrite the commit message just because if it's a documentation fix or if it's a fix in a test case, then the people reading the release notes won't really care about them because they're trying to decide, oh, do I want to upgrade my production deployment to this release that you're seeing right here? And then they maybe read the bug fixes and then try to determine based on then, but if he introduced too much noise to that list of bug fixes, then they'll just get bored and not actually read it. So it's the reason I wanted to explain all this because I always feel like I'm annoying people with these nitpicky requests about how to format the commit messages. So I just wanted to explain that there is a specific reason behind it that is related to the commit messages being machine parsable and then they actually being parsed. No, no, no, no, I'll, sorry about that. I'll change the fixture docs then. Thank you very much. And it's already been approved. So anytime you can, you can merge it. Well, actually someone else has to approve it. It can be anyone but Jackpreet because then we would still just have one company approving it. Yeah. Yeah. Maybe Sunday can take it. Yeah. Yeah, if he can take a look that would be great. Okay, so that's about these pull requests. And then the last thing on pull requests that I have is that I started going through them in order from the beginning from the oldest ones. So I'm going to start looking at these and close them down a little more aggressively if I think they are not going anywhere in the near future as in we should either try to push them over the line and merge them or if they've been abandoned for too long and we don't see ourselves being able to finish them then just close them down for now and leave a message to whoever submitted originally. Something that says, oh, we're closing this now just to tie the things up to the clutter, but you're always welcome to reopen it and continue working on it. And yeah, and there will be a few of them where I'll just ask for reviews and I'll ping those to the chats specifically. So no actual items from you from anyone here yet, but I'm just letting you know that I started doing this and the end goal is that we should never have more than 10 maybe 20 pull requests open at a time in my opinion if if we have 55. It's usually the sign of a lot of them just being stale. And that actually is the case because we have dozens here that were submitted more than six months ago and and so with those the question always poses itself how much more effort is it going to be to rebase these with all the marriage conflicts that were introduced in the meantime because as they grow older it becomes more costly to to resolve the marriage conflicts again. So yeah, it's just bottom line. It's a tidying up kind of operation that I want to do, and also at the same time I'm working in parallel or on making the CI a little more stable. And then hopefully the two combined together will put us in a position where we can accept contributions quickly and easily so that we can we can always keep the pull requests smaller if you don't have to do this thing we're the submit large pull request just because we know that it's going to take a lot of time to actually merge it in because it's CI takes days to pass or even longer. Yeah, that's it. So that's that's that was my thing for today just keeping everyone up to date about these things that I'm going to do slash already do. Thanks. And then I don't have any other agenda items so if anyone else would like to say or show something to go ahead. Yeah, I wanted to get some feedback on the documentation. Anything machine. Can we also check this out online or is it just for local house for now. No, it's just local for now I'm, I haven't published it to publish it anywhere I just wanted to get feedback on the layout of this page. So, Tracy had, I mean, this is an adaptation of what Tracy had, and she had a bunch of candidate sections up on top. I changed those a bit. So, I retain some of them. These don't have anything right now, just placeholders like FAQs glossaries. I think contributing we can probably retain whatever she had looked pretty good. Just take a review this again. The introduction page. I'll fill something here from based on the content that we already have, which introduces the project, the history is something same for vision, what did I do here. Oh, the vision I think I just for now I just copied over the read me from the from the cacti repository but I'll change this a bit before submitting for approval. Key concepts I just eat in this page. Sorry, I just eat in this page. Maybe I'll take something out from the existing pages and listen here. Also want to feedback on that use cases. I created a page I thought it'd be good to have a list of use cases here up front, and then one for characters and one for We were one on the integration roadmap. Again right now this is just a copy of road map and D but I'll Change this to make it Read better Guides, I think you have to figure out what to write here. References I just Yeah, there's something I'm going to fill so for now in the technical specifications I just linked to the character white paper. RSEs in the reader folder, but I plan to add the publication list and list of the events and the videos you've done together. I need to put them there. Things like that. Under we will see I just imported the The pages we have in the weaver dogs. The sign The thing at the top is preventing me from looking at the tabs. We just see one second. One second. Okay. So this is the documentation we have the publisher we were And this basically looks very similar. I just sort of fix some formatting issues some of the image links for For characters. I wanted to ask you like what how exactly should I structure this because you have the docs in here and there are some empty files here. And There is source. What should I look at in order to create the The chart for this page. There's a few different ways to approach it. One is That we could just Abandon this. I don't know. Yeah. Honestly, I think we just abandoned this one and just go with the new one. And so the question is then how to migrate it and The important information here is that Most of these rst files are just doing an import of the markdown files. So if you look at contributing md, I think that's just going to be a reference to the contributing md. And The root folder. So most of this. Yeah, I'm not sure what I'm looking at right now either. Give me one second. Maybe it's the or maybe there's a matching rst file. Or maybe it's in the index rst There Or maybe read routes. Okay, that is a table of funds here. I think should I should use this. Yes. Yes. So those are the markdown files that actually get referenced from the project route. And Yeah, that's that's how I would start. I would just figure out if The new documentation template also works with these markdown files and some smart easy way like the way this does where you can just import the markdown. Yeah, so I It kind of does the only catches it has a I'll show you something like it imports, for example, the notes and the The code and everything the problem is Some it doesn't It needs more white space. So if you see here, I think there's something some issue with the with the line break, which is why it's not interpreting this as a note. So some places I have to insert An extra line. So that I have to do and also have to update the image references because it can't figure those out. So there's something I have to do manually but I'm willing to spend some time to do that. Okay, thank you very much for that. Then Then I think that's the way to go. We just take what's in here the references to markdown files. And we just pull in as many as we can, meaning we won't be able to pull all of them in because Some of it will be conflicting information like the navigation bar or whatever definitions But we can definitely use governance and the build dot md contributing md Letter support matrix as a support RST Maybe packages as well The regulatory and industry initiatives reading list Oh, we have definitely the maintainers md Because you want you want to show who the maintainers are So people can figure it out. Yeah, so I had a Proposal maybe what we can do is if you're okay with the high level Categorization here then Maybe we do this in a sequence of peers like not all in one PR but In the first PR we just create the This outline fill in as many pages as we can leave the other pages as Work in progress and in the cactus and we were taps. We just moved the dogs from the Cactus cacti dogs and from cacti weaver dogs folders Respectively so that They are in the in the right place now And in the in subsequent PR we we try and remove some redundancy because that's I think There are actually some placeholder files here for stuff like governance and policy I think There are actually some placeholder files here for stuff like governance and policy But we never wrote anything. So if you have something that can get rid of this from From weaver and put it in the most interlocation so Can do that in like two or three different PR then you also have to fill in Things for FAQs and glossaries and and references and things like that. So Our guides reference so I can fill in the first group So Is that does it sound okay first PR we just Move everything into a Into one central Dog folder And Then we refactor it in Subsequent PR Yes, anything that's the easiest for you. I'm totally fine with and also It sounds good that In the first PR we just do The minimum viable change that pushes us forward and then we can Interessively improve it later on For governance and policies we do have in the repo route a governance MD Which talks about Maintainers and how we do reviews and stuff like that So if you if you don't have anything in the other one, then we can copy paste this If you want to Sure, I'll just do that. I there are a number of different files here I'll just yeah, I'll probably just copy them over for the first iteration. Maybe we can Refactor them Okay Yeah, I'm gonna copy them for the first iteration Okay Yeah, I will copy them first because Some of these have to be In the roots Just so that the scripts that Rai run sometimes picks them up For example security dot MD has to be maybe it does not have to be but It's preferred that it's in the roots so that people can always find it easily and quickly Then maybe yeah, maybe I can just add a link here to that page If you have nothing new to say here, it's just best to say go look at governance what I mean that I call to you Yeah, I'm full finder to you. Absolutely Is it not possible to like import the data from common 25? And show it here Yeah, we can do that but the questions do you want to reflect To say the same thing in two different pages If it's the same content might as well just provide a link here Or would we can discuss this No, I mean I was saying not creating a copy but directly somehow showing the same file contents of the same file here Okay, so whenever we push a change to governance.md in the repository to show up here and to show up here Yeah, we can write an action for that Okay Yeah, I think this is the documents are mainly a way for somebody to just go and get started with the code, right? Rather than having to navigate through the repository Yeah Yeah, agreed Okay, otherwise this I haven't changed anything in the look and feel of the page this is I just changed the name and the logo Replaced it with whatever Tracy had this default. This all looks okay So just one thing in the logo Yeah, in the logo can we have just the logo and should I put in the category also because if you look into the tab It's not very readable the icon That is true I just changed whatever Tracy had. Let me see if I can make this bigger. Yeah I guess one more little thing I noticed is that on the top right corner Those numbers don't look real because I think we have 200 something stars Yeah, yeah I'll try to fix that. Yeah, I wasn't focusing on it Yeah, it's a minor thing. It doesn't really matter Yeah, I haven't tried to see that. Let me see how this works It works nice Yeah, I think it looks great the the menu structure to lay out the color theme I think it's good. I like it Yeah Okay, so I will keep working on this one to complete this before we have to submit the quarterly update Oh, yeah, which is gonna be due soon probably in a few weeks. I think I think we have about two to three weeks left to go in July Yeah, okay. That's great. Thank you for working on this. This looks really good You're welcome All right. Anyone else with any other discussion topics? Cool. And thanks everyone for joining and I'll talk to you next time Thanks Bye Bye