 All right. So good morning, good evening, good afternoon to all. Welcome. So this morning we have a couple of project reports to hear about after the usual hackfest planning discussion. And then we have, I think we can discuss the update that Tracy provided to us on the workgroup reporting proposal. Pardon me. And Tracy's not on but we can, you know, we can discuss and she can listen to the recording after the fact and update accordingly. So is there anything else for the agenda? If not, Todd, do you want to kick it off? Yeah, sure thing. So before we go into the hackfest, I just want to make everyone aware earlier this week we announced the flagship event for Hyperledger. We're calling it Hyperledger Global Forum. This will be December 12th and 12th through 15th in Basel, Switzerland. So I'm dropping all the information into rocket chat now. But this is a large conference to pull together the entire Hyperledger ecosystem. So this will be a mix of both business focused as well as technical focused tracks. We expect over a thousand attendees at this. So please have a look at that. Mark that off on your calendars and we hope to see many of you at that event. I imagine there'll be an expo for vendors. Yep. A large exposition hall, a ton of sponsorship opportunities for any companies looking to sponsor there. If you have any questions on that, I'll drop a few of the details in here into the minutes that go out after this call. Super. Thank you. All right. And then next Los Angeles. So here's the registration link again for that February 20th to 22nd. The two things we want to cover in this call. Tracy's not on. So I'll just walk through this. Here's the draft agenda that we pulled together. So one from the feedback last week, we restructured the day zero training day. Really the idea is that'll kick off the first half of the day up till lunch will be kind of a welcome overview. What not from Brian and Tracy at a top level than brother strategy. And then quick lightning talks from each one of the nine projects. And then everyone will break for lunch after that. Folks will come back and sort of self select on how they want to get their dev environment set up, whether they want to focus on contributing to the various projects, writing applications or whatnot. And so we'll have various breakouts for that. So the, the two things we need are one, does this format look okay, any last weeks to it. So if you are one of the project maintainers or heavily involved in those and going to be there on the 20th, please drop your name in where it says need volunteer. So any, so number one, any concerns to this format. I think Todd the only thing that I see that sort of missing is discussion of any of the work groups. I wonder if we might want to have sort of a lunch and learn and maybe the work group chairs that are there if any can talk about their respective work groups. That's a great suggestion. I'll add that in the comments and just chat with Tracy on that as well. Again, I don't know who's planning to attend but I think I recall a heart saying he was going to come. I guess it didn't happen either if they're not there but certainly, I think it would be good to cover the work groups as well. Yep. That's great suggestion. Any other questions or concerns on format. All right, for those on the projects please get your names dropped in there otherwise Tracy is going to come track you down and work on sign ups for that. That's a great representation for one of the projects. We just want to be able to cover it, but we'll do so to future hack fest. Otherwise, beyond that everything remains the same hope to have Dubai confirmed soon. And then Amsterdam is confirmed June 27 to 29 registration will be live by Wednesday of next week. So you'll be able to sign up for that starting in the DSC call next week. Yes, and then front. Thanks. Okay, project reporting. So first up is start to stand are you there and yes, I am. We'll copy this. I definitely managed to get this report put together last night before bed. I remember this morning that we've got four more repos that I'd forgotten about so. Okay, I think I pulled in stats from everything but so the, I think the short version of this is that saw tooth is very active it's very healthy, we're continuing to move forward and we're all driving towards our one dot oh release which is pretty big deal for for all the saw tooth maintainers and contributors so we're pretty both tired and excited approaching this. There's always a surprising number of loose ends to tie up as you approach a release but pretty happy with how things are shaping up. The process has been over the last several months that we've been expanding what we do in CI so that things that are going into the one oh branch go through an extended period of testing. And we keep the network. We keep a test network up for a number of days under load so that we can shake loose problems that wouldn't pop up during unit testing or brief or integration testing from from kind of a project organizational perspective. We did some structural stuff with the code where we broke things out into a couple more repos, but largely those have been long applications to make the applications independent of the core code. Kind of in favor of splitting out some of the SDKs into separate repos but the prevailing viewpoint from from the the rest of the maintainers was preference to keep that in lockstep with core so we don't have version mismatch stuff with the SDKs so those continue to be in there. But among these applications that we split out I highlighted a few in the report here, which are a role based access control system that that is sort of an extension of the permissioning rules that we've included in the sawtooth design. Most of that is the application level. So there's there's hooks within within the core code itself but the way to interface with with sawtooth to configure that for whatever your consortium enterprise needs are out at application level apis supply chain. We showed off in a previous TSC meeting, but that shows telemetry of things as they go through transit, for example. And then we also had block explorer application donated by by pocket talk who needed UI for some of the things that they're doing and we're glad to have them contribute that back, just like how T mobile contributed back the the hyper directory application. As we approach 1.0 for our current plans there's there's going to be all the the marketing drive that that Linux foundation supports us with which is fantastic. And so I've left off most of the details of what the 1.0 features are knowing that we're going to have a nice campaign about that. And then also noted that that some of us have already started to move on to 1.1 thinking and quite get into details and not in in next quarter's report. As far as community health, the not really any change in the maintainer population we did see some of, or maybe we've adopted some of the IBM strategy here of letting companies poach off a couple of the folks from Intel. And so that's going to give us a little bit more diversity, but the actual people involved are basically the same over this last quarter. I don't think that's an actual strategy, but. No. Now I feel like I should follow that. Nice try though. Yeah. Contributed diversity on the other hand we have seen some uptick in that in general that has been I think from. The edx course is has driven a lot more interest and a lot more questions out to chat and then subsequently commits for. Bugs and stock fixes and stuff so that's been great and then we also see interest in. Seth the the sawtooth ethereum collaboration with with hyper ledger borough. And then of course as we approach the release that's also been driving more interest and sawtooth so those of all helped I think increase the the commit or traction here. And so I mentioned the the edx course and and seen some increased interest and I think I may have mentioned that in our last update the downside that I saved for the end is that. I think the the maintainers in general do not feel connected to that edx material. And we often get questions out on chat that are based on that material but most of us aren't familiar with it. So I think there's a couple problems there that might be worth discussing one is just you know simply the the maintainers taking time to go out and go through that material is is one thing but. From from several of their perspectives that that material kind of. Was put together without a whole lot of their involvement and so there's at least a feeling of disconnect there. So I don't know if any of the other projects have similar. Experience or similar. Opinions of that but that that does feel like a bit of an issue within within the sawtooth maintainers. Well not not hearing any reaction to that I don't know if that's a. The absence of that means that that's a sawtooth only experience or if. Other project maintainers simply aren't on. Look look at the chat please. There's a whole bunch chat. Okay. So who developed the edx material I wish Tracy was on because I think she's closest to this. Correct. Yeah. Tracy's not on but. Again I mean this this is sort of why I brought up the the whole point that I thought that we wanted to have maintainers from the various projects participating in the education training working group. To ensure that the material is correct. And current and so forth. My understanding was that that was checked you know that people on the various products were checked with. So far from a fabric perspective it's been mostly accurate so I can't. I can't speak to that there's been questions and I think most of those are just people. Who are trying to do more than what was in the course and getting stuck. Yeah I think. Go ahead. Of course that. Chris was talking about is that the IBM blockchain course on. No it's the edx the MOOC. Okay there's another MOOC with. Something called IBM blockchain in Coursera. Yes. But I'm talking specifically about the hyper ledger edx material which is combination of. Material covering both fabric and sawtooth. Yeah so we've had a couple training initiatives one has been this this online course. And. Material for that was was gathered I think mostly over the summer early fall. And that was put together. Not sure is the name of the company edx. I think so. Yeah edx. Okay. And then subsequent to that. Tracy initiated the that the training working group. And so I think that the. The takeaway from my perspective is that we didn't have as much involvement from. Maintainers as would have been desirable in the edx material for the edx material. And so as we're starting this training working group. It would be good if. It'd be good if we don't repeat that. And part of that's definitely going to be on the maintainers if they don't. Make time and don't. Engage then. You know that. On the one hand they don't really have a reason to complain. And then on the other hand it's just. Going to be the pragmatics of. People who are already working. More than full time on code and docs and stuff to then add another thing to their plate voluntarily is difficult. Yeah. No, I tend to agree with that. But I do think that. You know that we. And this again this was why I was pretty adamant about my point of view on. Getting maintainers to actively participate in all of this. Because I think it's. A responsibility of all of us collectively hyper ledger. Right. That. If we are going to put out training material that it is correct and we do our best to make sure that it is. And we can't just use an excuse of well no maintainers got back to us. Then it maybe it shouldn't be published. Right. So, you know, again, I just think we need to be careful about, about some of this because it can. It can create problems and everybody is very busy. I get that. This is all volunteer. I get that. But by the same token. We have to make sure that we're doing the right thing. Yeah. So if, if there's something that could be done within the existing edX material. And. Maintenance of that that makes it easy for a project maintainer to go in and. Sort of see an outline at a glance, you know, not have to like sit there for a 60 hour course to see what's there. Right. I've been asking for the same thing. So. Yeah. So that would decrease. Yes. Yeah. Then it's the same to the same extent with the, the upcoming. Yeah. Yeah. Yeah. Yeah. And then it's the same to the same extent with the, the upcoming training working group. If there's like a digest version of the material that. The maintainers can review that that lowers the bar and increases their engagement. I'll make a note to have Tracy reach out and kind of get to the bottom of this and figure out that there's a good plan. For moving forward. Okay. Great. And if, if possible to reach out to the sawtooth maintainers. At large and not me specifically. Sounds good. Yeah. I mean, I see. In the code. Currently I see the code for the training, but not the course material. Maybe I'm wrong about that, but. I think we need both. Right. Need to be able to. See the actual, and we should be able to drill down if somebody posts, like for instance, I was asking previously of Tracy. So, okay. So I have some stack overflow questions that are coming in on one of the, you know, one of the apps, but I don't know what the course material says. I haven't taken it. Haven't had time. And so I don't know what it's saying to people and I can't tell whether or not they're being misled or I think in most cases I've sussed out that basically they're trying to take the example further than the, the, the course. You know, so coloring outside the lines and then they get stuck or they, they run into trouble. But it would be good if we could actually look at the course material to see if, you know, if they're being misled or not, but, you know, not having the ability to sort of drill down and say, Oh, there's that, that sentence is incorrect. It should say X and being able to submit a poll request. I think, you know, Dan to your point creates a bit of a problem. Yep. Okay. Well, thanks for, thanks for that. And then that's, I think that's it for the sawtooth update. Unless anybody has any questions that I'm happy to answer. So when we are being listed for sawtooth 1.0, is there any plan date? The, the official release date for 1.0, I guess the, to keep the, the marketing announcements impactful, we're not supposed to disclose that exact date, but you can consider it imminent. As they say real soon now. Yeah. Yeah. So it will be very soon. They, they send out press releases that go under embargo, so that they all get released on the same date and that there aren't like leaks. Okay. So it would be in the first to quote her, right? Yes. Okay. Great. Okay. Thanks, Dan. Any other questions? All right. Thanks. Unless anybody else has questions, but. If not, then I think we can move on. Oh nuts. I lost my agenda. Here we go. Roja. So somebody on from a Roja to. Yes. I hear a voice, but it's very faint. Okay. Let me try to improve it. So is it better now? A little bit. Can others hear? Well, I'm not sure if I can improve it at the moment. So. Well, I'll try to do the best. Okay. Yeah, just speak up. You're coming in better now. Okay. So, um, so your project is quite active. So we are working towards a preliminary release 1.0, which is expected to be in April. So right now we have an internal feature freeze. So, and we're working. Well, to improve the reliability to improve the performance and usability so that, for example, the error messages are more clear for the users. Um, as for community, there are some issues. Well, for the, like answering the questions and so on, but we have some internal changes to improve that. So we're also working towards improvement of community management. As for project issues. So we have a sonar cube working to analyze our project. We're improving the metrics. So the main issue was the best coverage. So, well, there are some issues with the setup of the coverage. So it's, it may, it may not show the exact numbers. So we're also working on that. So, and we also will improve the coverage metrics by introducing the integration test framework, which will allow easy testing of both transaction and query pipelines. So, as for in general, as for expected, expected features, which we're working on now are multi-signature transactions. The model library, which is usable in Java and Python. Then push-based notifications for clients. So this, so a good elaboration on this was made on Lisbon Hackfest, where I have met people from a caliper project. So we have gathered better requirements for that. And so I think that's basically it. So it's, it covers the most of the project update, which is available on Hyperledger Wiki. So if there are any questions, please ask. Hi, Andrea, this is Chris, just clarification. You have maintainer diversity here. You said four new maintainers were added. Are they all from Sir Amitsu or? Yes. So the four new maintainers are from Sir Amitsu. Anything about current projects, external projects like similar to what Dan was talking about, like for provenance, if it's sort of similar to that, is it all involved in any, I mean, I didn't go read details of the, of what's there in the Wiki page, but is that presented? Sorry, I don't think I got the question clear. Could you maybe? There was some background noise cutting you off. Concrete projects in involving Iroha in any, in a commercial setting. Oh yeah. So I guess my colleague can elaborate on that. So I'll give a word to him. Hello. I know about one new project. It's a company, CAC, from Japan. They worked on insurance program and use Iroha like storage for, for their purposes. Thank you. Any other questions for Andre? Just follow up on the earlier maintainer question. Are all of the maintainers from Sir Amitsu? Yes. So all the maintainers are in the Russian team of Sir Amitsu. And then as far as your contributor diversity, are you seeing contributions from outside Sir Amitsu or all the contributions also from there? No, there were contributions from outside and we have seen people working on a snap package. So this snap craft package, which is used in Ubuntu. Great. Any other questions for Andre? Okay. Thank you. So I think Andre, you know, the, the sort of the, the feedback that I think you're hearing is that it would be good. If the team can work to try to grow that diversity. You know, again, it's, it's one of the more challenging aspects. But I think, you know, certainly reaching out to either maintainers on some of the other projects or, you know, maybe Tracy to get some ideas about how to go about doing that would be, would be good. Yes, sure. Like we are like looking towards some more external interaction. Yeah. Yep. Thank you. So I think that's one of the three strategies for, for going about, you know, doing that. And it does take time. Right. Just like I said, I think, you know, probably if you chat on, you know, rocket chat with others. Yeah. Or if you have people coming in and starting to use the platform, that's a good source of. You know, potential new contributors. So. Okay. Thank you. So the next up is discussion of the working group reporting. Process draft. So. Tracy's provided us with three links here. One is the overall process, which is very similar to the project reporting process page that describes how you create a template and so forth. Then she's got the actual template itself, which I think is the part that we should probably discuss. And then she's got the schedule for the. For the updates is in there. So I suggest that maybe we. We all take a look at the template itself. Joe. Payton chat. Oh, Todd already beat me to it. Thanks, Todd. Um, so. I'll play Tracy here and just sort of walk through all the different pieces is very similar to the project reporting. Some differences in terms of. You know, maintainers and committers and so forth, but other parts of it are fairly similar. So the first part is. Obviously specify which working group this is. Um, a description of sort of the. The chair's perception of the health of the working group, how things are going. People showing up for calls. The having calls, right? Um, what are any issues outstanding? Um, yeah, you know, can't get people to come. Can't keep people away. Can't beat them off with a stick, whatever. Um, you know, so identify any concerns or issues that the. Working group has that the TC should know about. Um, a discussion of the progress on the various work products. Um, and then just sort of generally discuss and, you know, the, the activity that's gone on for the past quarter. Uh, anything's that were released, anything's that are amended and so forth. Um, current plans for the next quarter. Uh, and then, um, you know, you know, you know, I mean, just like with the projects, you know, do we have a healthy diversity of participants in the working group? Um, the working group scope. I thought as, you know, Um, this, this, you know, this point here has the scope of the working group change since the original charter. And if so, how. That would be a red flag to me because the, uh, before hands, uh, as the change in charter and scope should probably be, uh, directly brought up and not just made as part of a work with the port. But that said, and then, you know, again, as before any additional information. So thoughts on the, the, uh, the template. Yeah. I agree in particular on the scope. Uh, I think we should probably just strike that. So it's not suggested that. The, the work group would just sort of willingly change its scope. Uh, I think for me, one of the important aspects of this regular reporting is to drive progress along scope. I think that, that some of the frustrations with, with working group participants has been that it can be hard to make forward progress and something like this helps drive that, that forward progress, which I think you can only get if you're, you're actually focused on what the work products or, uh, mission of that. Yeah. That working group is. Any others? I know. So. This really comes down to, and the, the templates really basically three things. Um, one is, um, kind of the working group health and issues, you know, what's the current status. Um, two is, um, uh, moving towards kind of plan deliverables and then three is community. Um, can we just simplify this down into those three? Do we need to have it broken out into all these different sections? I'm looking at something, you know, it'd be nice to be able to have three or four paragraphs rather than a, uh, document that's going to take a couple of hours to put together. I think, you know, if you're a point, I think you're wrong. You know, we could likely consolidate this. I mean, coming back and saying, okay, what's the help, for example, cover and overview any issues that you have. Okay. How are you making progress towards the deliverables? You, um, uh, claimed in your, in your, um, charter. Um, and then how's your community doing? Yeah. I could see that. Maybe we also want to add like a brief spidgen about what your plans are for the future quarter. But yeah, I think that's about right. Yeah. I agree with hearts edition there. What have you accomplished? And then what do you have in progress or plan to accomplish? No, I totally agree with the idea. And, uh, actually for the, um, technical working group, we are already keep the monthly reports for the passing past a year. So Chris, if we start a new quarterly working group reporting, would you like to ask to convert the monthly report to also to the quarterly one? Uh, Oh, absolutely. I think the China working group should be a part of all of this. Yes. Okay. And you're, you know, the China technical working group is in, um, you know, in the schedule. So, um, yeah, I think, you know, just sort of, uh, uh, summarizing and then maybe looking to the past three, uh, monthly reports will be. Okay. I suppose the idea. Any other thoughts? Okay. So I think there's sort of general agreement then to simplify this a little bit into the, the four categories that making heart suggested. And, uh, I guess we can ask Tracy to, to go back and after listening to the feedback to simplify. Other than that, I think. Any other comments, concerns. Uh, also our thanks to Tracy for putting it together initially. Absolutely. Okay. Then I think we're at end of job. Thanks everybody. And, um, we'll talk at you all next week. Cheers. Thanks. Thanks for the line. Have a good day. Thank you.