 All right. Good morning. Good evening. Good afternoon. Wherever you are, there's your weekly reminder of the antitrust policy. Don't do antitrust. Okay, so on tap for the agenda today we have we have our usual reminders for the test on the call for papers and the TSC election. We will have quarterly updates for fabric. And then we are waiting for quilt and sawtooth. I don't know if Adrian or anybody is on for quilts. It doesn't sound like he'll make it. It sounds like he's in a conference. Okay, right now. All right. And then we have no weekly updates for working groups. Mark has asked to to bump his I'm sorry, not Mark Hart has asked to bump his disease traveling this morning. And then we have a proposal for a hyperledger labs, I believe. No, I've been, I've been, no, I'm sorry. That's a different one. Anyway, so we do have a proposal that we can review and hopefully somebody's on for that. Yeah, we can do that. Okay. All right. Any other items for the agenda? If not, then Todd, you want to kick it off. Yep. Sounds good. Just three quick reminders. Hyperledger global forum. The, our major public event in December in Basel, the CFP will close tomorrow. Please get your submissions in for that. We'd like to see a lot of topics from the groups here. A lot of great stuff has already come in. Thank you for those that have submitted, but that does close tomorrow. Next, the last test of the year will be October 34th in Montreal. Please get registered for that. We'll start talking kind of draft agenda in the coming week and take into consideration a lot of the things we've done for them. But I think that was definitely a step in the right direction with the pre-planning we had done for that. And then the third piece, the timing and process has been approved as of last week for the CFP election nominations will begin August 9th. It'll run for a week and then we'll move into the voting phase in the link for the timing and process. This is now a link to the everyone that's eligible for that. And so that's based on the criteria and the charter as well as what the CFP had approved the last week, which was the workgroup lead. The workgroup contributors as defined by the workgroup lead or chairs rather, as well as the labs. So please look at that as you get closer to August 9th. We'll be asking if your name seems to be missing from that. Please reach out to trace your eye so we can investigate. A couple of days before August 9th, we will freeze that and call for any objections there. Otherwise, that will be the list that we do for nomination eligibility and voting. Do you have any free updates? Any questions there? All right, then let's move over to project updates. Chris, I think that's you unless it's someone else in fabric. Yeah, no, it's me. I need to figure out how I can get somebody else to do these. Where is my TSC chat? There's the, I just pasted the link to the update in the chat. So for, pardon me, for project, for the fabric project, we, I think we're still going strong. We're continuing to grow and mature. We pushed out a release almost on time in our quarterly cadence. We ran into a snafu literally on the day that we were, we were cutting the release where Debian had pulled support for some images that we were using. Anyway, long story short, we pushed it last week on the 3rd of July. And the, the, the announcement, if you will, the more formal push will be next week coincident with Oskon. And I'll be giving one of the keynotes talking about what we're doing at Hyperledger. We have a growing mix of contributors. We actually bumped up a little bit in terms of the, the ratio of IBMers to non IBMers. It inched over 40%. And however, the, the sort of the ratio of commits from outside IBM and on IBM actually grew. So, so that's good, right? So we're actually getting more content from non IBM, which is, which is the positive. And, and we actually increased our number of developers considerably. We're up to 16. And we have about 1450 commits there. We are really doing well, I think over in Stack Overflow, we've got over 2100 questions. And that's actually sort of almost a doubling quarter over quarter of the number of new questions added. So this is, this is, this is good news. It's a good sign that people are using it. They have increasingly sophisticated questions. We actually have spent this past week almost wrap it up with the JIRA consultant this afternoon, but we've been, I think, having a really good engagement there. She's been able to sort of help us with our workflows and recommending some plugins and so forth, including we had a demo of Confluence as a potential replacement for the Wiki, if we wanted to consider that. And I know that that had come up in previous discussion, where Rohad asked for Confluence and seeing the integration between JIRA and Confluence. From a Wiki perspective, it seems to me like it might be a really good improvement over Wiki media. Anyway, so, but that I think is moving in a positive direction. And then next week we'll spend actually updating JIRA with the consultant and getting all the issues transitioned over. As I mentioned, we published our 1.2 release on the third. And we also published a 1.1.1 a couple of days before that to backport some bug fixes. The rate of downloads, so again, it continues to be I think a steady stream of about an average of 100 or so downloads a day. That's not all of them, but those are the ones that are tracked through a short URL. I think actually a lot of people in China can't use that because it's Google or it had been Google. And so that number may actually increase. I change it to Bitly as the end of the release and see what happens there. In terms of our overall activity, the email traffic dipped a little bit after the spike in March when we had the 1.1 and then moved back up towards June. But again, we're still going better than the year before, so year over year I think we're doing well. And then certainly there's a ton of traffic in rocket chat and as I mentioned, on stack overflow with a 55% increase. Our current plans are to continue our quarterly cadence of releases. So we're expecting a release at the end of 3Q and we are in the process of working with the maintainers to agree on the release roadmap and which epics are going to get in. That planning is underway and we hope to be able to mail it down I think by the end or by next week. Maintainer diversity with static, but we do see some possibility to add some maintainers on the horizon. Contributor diversity, as I mentioned, basically it bumped up a little bit from an IBM perspective. I think that was a result of some increased activity from IBMers on testing and so forth. And because things are in production now, we're starting to get bug fixes and stuff coming from support teams. So obviously we want to work on some of that, but as I mentioned, the stickiness, if you will, of contributions from others is growing. And the type of contribution we're getting from non-IBMers is also much more substantial. So this is all good news. And then finally just a note on sort of collaboration between Cello, I'm sorry, Calliper, there's increasing interest in leveraging Calliper for doing performance benchmarking and so forth. Burrow obviously with the integration of the EVM and Fabric in 1.2 and the continued work on building out a proxy. And we had some really good, and then of course with Indy, I know there's people looking at exploring how we can leverage Indy identities in Fabric for our MSP. And then we had some really good discussions with Sean. I had some good discussions and so did Gary, I think, with Sean from the Sawtooth team. And we're exploring various areas of mutual interest and then also had some really great conversations with Kelly on what we might do from an SGX perspective. So again, I think it's good news. I think we had some discussion in our, we had this sort of an impromptu because I happen to be here in Raleigh with Gary and others. And so we had an impromptu sort of retrospective, if you will, on the release. And we're pulling that information together. We have a sort of a community retrospective. But thinking about how we could maybe do planning a little bit better. We overshot on the number of epics we thought we could squeeze in and so forth. And so we started thinking again, and it was a hallway discussion and can't help those sometimes, but of how we can potentially do that. So I think that the maintainers meeting will start having ideas, sort of thinking about how we can better do planning and tracking that we have. So anyway, that's basically the update. Any comments, questions? Hey, Chris, this is Tracy. Yep. I wanted to talk maybe a little bit about the confluence statement that you had in your update. Yep. So we've done some research on confluence for Aroha because they were interested in using confluence. So the cost of using confluence of our existing Wiki is actually twice as much. Why is that? I have no idea. That's what we've been told by our IT folks. Maybe it requires bigger machines or something I don't really know. But anyway. Confluence itself is free because we're open source. Sure. But there's also the cost of migration of existing Wiki content as well as the cost of people learning a new tool. So people have been using it. I think it's something that we should talk about further as a TSC and decided that's the direction that we want ahead. Yeah, like I said, what I saw, I was really impressed with and it gives us a better ability to build out, for instance, something that is much more easily consumable to people from outside the project in terms of understanding what's going on. We can build like epic pages and we can have a release roadmap page that is a little bit easier than trying to self navigate JIRA if you're not a JIRA person. Chris and Tracy, this is Dave. Just to remind you, remember the consultant said yesterday that if we're coming from one of the well-known Wiki packages that there are conversion tools or migration tools available. And I said Wiki media and he said, oh yeah, yeah, there's there's probably a good migration path there. Yeah. Go ahead. Yeah. Just a question for Tracy. When you said twice the cost is the cost initial cost like $50 or $200,000, you know, what is the range because twice the cost implies, you know, double what is present. But if it's insignificant, then not insignificant, if it's low, then, you know, then it's really possible to do that, right? Can I break in really quick? I'm sorry to interrupt you. That's Nikolai from Hyperledger Roja. So we were applying previously for at lessing program for open source projects. And I think Hyperledger at all is eligible for free cloud versions. So there are no expenses for the infrastructure and for the platform and all the plugins. Well, as for the plugins related to Confluence, there will be paid if we are going to buy a server version, all the plugins, even the commercial ones will be for free. And a question for Fabrik, for Christopher, I mean, do you use Caliper as the part of your continuous integration? I'm sorry to interrupt you. I'm sorry, is that it again, Nikolai? Yeah, my question is, so you use Huawei Caliper tool, right? Well, I mean Hyperledger Caliper. It used to be Huawei. So do you use it like a part of your continuous integration pipeline or what's the process of your use of this tool? Yeah, we're looking at, we have something called PTE here, Performance Test Environment or something like that. And we're looking at leveraging Caliper. And so we have an engineer that's starting to work. Great, thanks. So it may end up being part of the CI or maybe not. We aren't sure yet, but we're taking a look. And certainly just doing performance benchmarking and performance testing and so forth is something that's of increasing importance. And I don't want to spend money developing two things. Yep. So the cost of Confluence was $400 to set up and then $450 a month continuous cost, the current cost of our Wiki is $200 a month. And those are the prices that I got from LFIT for running it in our infrastructure. So that's the order of magnitude of cost. Well, if we need to, we should, I think we should be able to go to the Budget Committee and make that request. I think what we have decided here is that it's a serious alternative and I think we should maybe move it off the TSC call and get all the people. Yeah, Dave, you were on the call and you saw how powerful it was. Yeah, it was pretty cool actually. Yes, it really was. Yeah, so I'll talk to Tracy. I think we'll, and Rai, I think we should have another meeting about it. I hate to add to more meetings, but maybe we'll come back to the TSC with a proposal. Yeah, okay. And of course we don't have to, you know, do the migration, but I think that would be ideal. Anyway, I think anything we would do would require migration. So because we have such great content on the Wiki already. Okay, so that's it. Any other questions? I guess from my end, hello, I'm Sasha. I've been working a little bit with the High-Pledge of Fabric and Composer and also contributing back a little bit to the community through creating Helmcharts and such. I'm very happy with the ecosystem, but my main concern is the scalability of the fabric component. It's particularly the CouchDB. I wonder if it's possible to somehow prioritize the improvement of the aspects of the CouchDB which relate to scalability. So with the pagination and things like this, this would go a long way to making High-Pledge of Fabric more scalable and more production ready, which in turn would I think increase adoption and also grow the community much faster. This is my only kind of gripe currently with High-Pledge of Fabric. Well, we could take that offline and be happy to explore some of that with you from a scalability perspective. I haven't reached a point where I've run out of a number of gears that I can connect, but maybe there is, I don't know. I didn't understand the question about scalability. Maybe I can repeat, basically in our own tests we found that it's sometimes, especially when you're combining High-Pledge of Composer and Fabric, it works very well for proof of concepts, but the amount of data that can be handled by the CouchDB components for the world state means that the actual requests become very, very slow. And I think it's possible to somehow improve the pagination for CouchDB, which I know it's a work in progress. It was planned initially for 1.2, but now it's been moved to 1.3. And it's quite important thing for production to make sure that it's one of the key priorities. And of course there's limited hands on deck, I realize, but I wanted to do the same thing and also ourselves to help. Okay, cool. I could take that offline as you suggested, Christopher. All right. Yeah, on Chad, the Fabric Chad, and then we can start following with the JIRA task. Yeah, sure. Okay, Todd, I guess next up would be the IBAN-P proposal. The link. Yeah, one moment. It sounded like someone was on from there, so that's Federica or, I don't remember her colleague's name. Or Lorenzo, either of you on. It sounded like one of you was on earlier. You know, I'll adopt the link in one moment. Federica, are you on? You know, they confirmed. Yep, as of yesterday. Right. Well, I guess we'll have to defer that. Yeah. Sorry about that. Yeah, I know we had confirmed that. So, and then the discussion on the copyright, is that still, I know you guys have been traveling a lot. So, I don't know, Tracy, where does that stand? We never nailed down with. Yeah, so we haven't yet, we were traveling, our legal folks are traveling as well. So, I think now that we're all back, at least until we leave next week for Oskac, I'll send out an email and see if we can get something set up for that. Okay, good. I think I know I've seen in fabric, I don't know if others are following the same suit of using at least for new content or content where there's, you know, it was clear it was developed, you know, sort of within the community were using the proposal, but I still think it's important to get the answer on what happens with the original contributions. Okay. Um, all right, well, I guess everybody gets 35 minutes back then, so sorry about that. And we'll talk to you all next week. Maybe see some of you at Oskac. All right, thanks everyone. Thanks everyone. Okay, thanks. All right. Thanks, bye. Thank you.